-
Notifications
You must be signed in to change notification settings - Fork 604
BUG: Skip "CI (Build)" workflow if any SuperBuild changes on "nightly-main" #7945
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
This comment was marked as outdated.
This comment was marked as outdated.
bc60d64
to
5765229
Compare
Simplify the logic for determining when to upload the Slicer package artifact in the "CI (Build)" workflow.
Skip the "CI (Build)" workflow if changes to "External_*.cmake" files are detected since the last Preview build. Pull request builds likely require an updated Docker image, which provides external dependencies, and building with outdated dependencies could lead to failures. To avoid this, the CI build is skipped when SuperBuild file changes may require an updated image. Additionally, since the GitHub action `dorny/paths-filter` does not suppor specifying the `base` input for pull request events, we replaced it with the `tj-actions/changed-files` action. This resolves the warning: "'base' input parameter is ignored when action is triggered by pull request event".
7c85d01
to
729b9f1
Compare
NextCheck if latest
|
@lassoan @jamesobutler @pieper When you have a chance, let me know if you have any questions 🙏 |
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
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.
Thank you, it looks good to me.
Could we an action for running tests, too?
Skip the "CI (Build)" workflow if changes to
External_*.cmake
files are detected since the last Preview build. Pull request builds likely require an updated Docker image, which provides external dependencies, and building with outdated dependencies could lead to failures. To avoid this, the CI build is skipped when SuperBuild file changes may require an updated image.Additionally, since the GitHub action
dorny/paths-filter
does not suppor specifying thebase
input for pull request events, we replaced it with thetj-actions/changed-files
action. This resolves the warning:Follow-up of #7942 (comment)