-
Notifications
You must be signed in to change notification settings - Fork 10
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
Use CSCS GitLab CI to replace as many Jenkins builds as possible #32
Labels
effort: 3
A few days of work.
priority: high
This is essential functionality or a serious bug. Not addressing this blocks progress.
type: refactoring
Milestone
Comments
msimberg
added
effort: 3
A few days of work.
priority: low
Nice to have, but nobody is going to be sad if this is never done.
type: refactoring
labels
Jan 19, 2022
msimberg
added
priority: high
This is essential functionality or a serious bug. Not addressing this blocks progress.
and removed
priority: low
Nice to have, but nobody is going to be sad if this is never done.
labels
Mar 10, 2023
This may be a useful starting point: https://github.com/electronic-structure/SIRIUS/blob/master/ci/.gitlab-ci.yml. |
This was referenced Sep 26, 2023
This was referenced Nov 3, 2023
This was referenced Nov 18, 2023
I'll close this as almost all CI configurations have now been moved to CSCS CI. We won't be getting a CPE configuration anytime soon, and moving the performance CI is tracked separately in #936. |
github-project-automation
bot
moved this from In Progress
to Done
in pika planning board
May 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
effort: 3
A few days of work.
priority: high
This is essential functionality or a serious bug. Not addressing this blocks progress.
type: refactoring
In practice this means replacing the non-Cray builds currently running on Jenkins. Work was started on STEllAR-GROUP/hpx-local#5.
Make use of the gitlab matrix functionality at least for release/debug builds, if not for different compiler etc. configurations.
Also replace the HIP testing done with Jenkins with
container-runner-hohgant-mi200
(as already started in eth-cscs/DLA-Future#982 for DLA-Future, though that is blocked on an MPI issue; we can initially run all non-MPI tests for pika).The text was updated successfully, but these errors were encountered: