Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: Switch cache job to use a specific version of ubuntu instead of ubuntu-latest #2820

Closed
terriko opened this issue Mar 14, 2023 · 0 comments · Fixed by #2823
Closed

CI: Switch cache job to use a specific version of ubuntu instead of ubuntu-latest #2820

terriko opened this issue Mar 14, 2023 · 0 comments · Fixed by #2823
Labels
CI Related to our continuous integration service (GitHub Actions)

Comments

@terriko
Copy link
Contributor

terriko commented Mar 14, 2023

In debugging #2799 (our cache jobs are getting queued for many many hours) my admin suggested that we try using a specific version of ubuntu for running our cache jobs instead of ubuntu-latest to see if we get any change.

So this would involve changing just this one line in the update cache job:
https://github.com/intel/cve-bin-tool/blob/main/.github/workflows/update-cache.yml#L18

(If it works we'd consider changing other jobs, but no need to do them all for a test)

I'm not sure off the top of my head what other versions of ubuntu that github actions supports, I guess try to use one that works but is unlikely to be used by a lot of other people? The available ones should be listed in the github actions docs -- please check what's actually supported right now and don't rely on old stackexchange/redit/blogs to give you a random number that may or may not work.

@terriko terriko added the CI Related to our continuous integration service (GitHub Actions) label Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Related to our continuous integration service (GitHub Actions)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant