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: new workflow for triggering ALCF GitLab CI on Polaris #976

Merged
merged 3 commits into from
Feb 9, 2024

Conversation

shanedsnyder
Copy link
Contributor

@github-actions github-actions bot added the CI continuous integration label Feb 7, 2024
only run on pushes to main and manual dispatches via web interface
@shanedsnyder
Copy link
Contributor Author

Okay, all done here (well, there are some smaller unrelated Python issues, but haven't had a close look there yet).

This new workflow will kickoff a series of regression tests on our ALCF GitLab CI instance which builds Darshan and runs test on the Polaris system. Right now, the workflow is configured to run on push events to main and via manual triggers via Github actions tab. Allowing the workflow to be run on every commit to a PR leads to potentially piling up jobs on Gitlab CI (which can take quite some time as its serially running 8 different batch jobs on compute nodes). I also further restricted the workflow to only run on changes to darshan-runtime (and to the workflow itself) -- testing darshan-util stuff on a supercomputer is probably unnecessary.

@shanedsnyder shanedsnyder reopened this Feb 9, 2024
@shanedsnyder shanedsnyder merged commit 84862c8 into main Feb 9, 2024
23 of 35 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI continuous integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants