[FOLIO-3698] UI GitHub workflow actions fail, folio-org/checkout@v2 missing Created: 05/Feb/23 Updated: 11/Jan/24 Resolved: 05/Feb/23 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P1 |
| Reporter: | Zak Burke | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | DevOps Sprint 158 |
| Development Team: | FOLIO DevOps |
| RCA Group: | TBD |
| Description |
|
Overview: CI builds fail immediately in all UI repositories with the following error: Error: Unable to resolve action `***-org/checkout@v2`, repository not found Steps to Reproduce:
Additional information: The relevant lines from .github/workflows/build-nmp.yml appear to be:
runs-on: ubuntu-latest
steps:
- uses: folio-org/checkout@v2
with:
fetch-depth: 0
Did ubuntu-latest recently change? |
| Comments |
| Comment by David Crossley [ 05/Feb/23 ] |
|
I re-created the Fork. It was deleted by mistake. See Slack discussion. But not sure if more is needed. Cc Ankita Sen |
| Comment by David Crossley [ 05/Feb/23 ] |
|
Julian copied its releases/tag/v2 |
| Comment by Julian Ladisch [ 05/Feb/23 ] |
|
Rerunning the .github/workflow actions succeed now: https://github.com/folio-org/stripes-core/actions Sorry for the disruption. GitHub search doesn't find the usage:
Need to use
|
| Comment by Zak Burke [ 05/Feb/23 ] |
|
This glitch was inadvertently caused when the folio-org/checkout repository, a fork of actions/checkout, was intentionally removed because it was not known to be in use at the time. Whether we should maintain a fork, given we have made no changes to it, is another issue, but the immediate problem was resolved by restoring the repository. Special thanks to David Crossley for quick action during a weekend! |
| Comment by David Crossley [ 05/Feb/23 ] |
|
And thanks to Julian and Zak for similar weekend action. Julian also noted in the Slack thread that our fork was about 2 years out-of-date. |
| Comment by Zak Burke [ 06/Feb/23 ] |
It is unfortunate, but GitHub search is seriously unimpressive. Like you, I have resorted to grep -r, and I maintain a directory with many folio-org repos cloned in order to be able to search them more precisely with CLI tools. The good news is they know and have a new "code search" public beta. The bad news is it's been beta for as long as I can remember and their beta-list appears to be full ("we'll email you when it's enabled on your account" and ... crickets). |
| Comment by Mike Taylor [ 11/Jan/24 ] |
|
So, now the dust has settled a bit, do we have any idea why `folio-org/checkout` exists in the first place? |
| Comment by David Crossley [ 11/Jan/24 ] |
|
I have no idea, but i presume that it was when Ankita was initially learning about GitHub Workflows. We must get rid of it after all of the UI workflows are updated. Our fork at https://github.com/folio-org/checkout is a massively out-of-date fork, and not been updated in over two years. The official version is now "v4". |