8000 BUG: Skip "CI (Build)" workflow if any SuperBuild changes on "nightly-main" by jcfr · Pull Request #7945 · Slicer/Slicer · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

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

Merged
merged 2 commits into from
Sep 20, 2024

Conversation

jcfr
Copy link
Member
@jcfr jcfr commented Sep 18, 2024

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"

Follow-up of #7942 (comment)

@jcfr

This comment was marked as outdated.

@jcfr jcfr force-pushed the fix-ci-workflow branch 5 times, most recently from bc60d64 to 5765229 Compare September 19, 2024 18:53
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".
@jcfr jcfr force-pushed the fix-ci-workflow branch 2 times, most recently from 7c85d01 to 729b9f1 Compare September 19, 2024 19:25
@jcfr
Copy link
Member Author
jcfr commented Sep 19, 2024

Next

Check if latest slicer/slicer-base image is published

A follow-up pull request will further improve to skip "CI (Build)" workflow if latest slicer-base image not yet published.

Indeed, due to potential delays between the update of the 'nightly-main' branch and the publication of the corresponding Docker image, the workflow now checks if the latest slicer-base image is available. If the image has not been published yet, the build is skipped, preventing unnecessary failures.

Github scheduled workflow for updating nightly-main

Instead of running a scheduled job on metroplex, another pull request will instead implement a GitHub workflow. This will allow us to notify relevant administrator in case of failure.

@jcfr
Copy link
Member Author
jcfr commented Sep 20, 2024

@lassoan @jamesobutler @pieper

When you have a chance, let me know if you have any questions 🙏

Copy link
Contributor
@sjh26 sjh26 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Copy link
Contributor
@lassoan lassoan left a 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?

@jcfr jcfr merged commit fb06d97 into main Sep 20, 2024
11 checks passed
@jcfr jcfr deleted the fix-ci-workflow branch September 20, 2024 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0