-
Notifications
You must be signed in to change notification settings - Fork 15
ROX-21124: Move release branch jobs from OSCI to GHA #1376
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
Conversation
fe094c3 to
2f1911f
Compare
RTann
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we want to run diff-dumps in release-* branches. Just master and PR with the generate-dumps-on-pr label.
We also want to run upload-dumps-for-downstream upon tag (would that be in a separate PR?)
| push: | ||
| branches: | ||
| - master | ||
| - 'release-*' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we may need to run these things upon tag creation, too? Not sure how to convert the OSCI release process into GHA release
2f1911f to
e2b90fd
Compare
e2b90fd to
208fe6b
Compare
dcaravel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Regarding testing - assuming since some of the jobs only run on merge to master will have to monitor the runs to ensure no issues.
Description
These changes enable GitHub Action workflows for jobs that were previously running in OSCI. Once merged, any new tags containing these changes will have OSCI configs that look more like master's than the other release branch OSCI configs.
Note for reviewers: here's the OSCI config that gates certain jobs from running in certain contexts: https://github.com/stackrox/scanner/blob/master/scripts/ci/gate-jobs-config.json. We should generally try to follow this for now unless we see a compelling reason not to.