-
Notifications
You must be signed in to change notification settings - Fork 92
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
Add ceph-dev-pipeline #2310
base: main
Are you sure you want to change the base?
Add ceph-dev-pipeline #2310
Conversation
An example run: https://jenkins.ceph.com/job/preserve-ceph-dev-pipeline/141/ |
#!/bin/bash | ||
# vim: ts=4 sw=4 expandtab | ||
set -ex | ||
PS4="\$(date --rfc-3339=seconds) + " |
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.
TIL... 👏
Incredible work. I have no qualms, suggestions, or nits. |
I wanted to set up label-based triggers to run this pipeline on ceph PRs, but it seems like I'd need to move the Jenkinsfile to the ceph repository to make that happen. |
d8cbb97
to
f33931b
Compare
This may ultimately replace the existing ceph-*build jobs; for now, it is a work in-progress. Signed-off-by: Zack Cerza <[email protected]>
Signed-off-by: Zack Cerza <[email protected]>
Signed-off-by: Zack Cerza <[email protected]>
This job serves to trigger ceph-dev-pipeline via webhook payloads, but is opt-in. This implementation initially targets only GitHub push event payloads. On each push, it will inspect the head commit for [git trailers][0]. The trailer required to opt in is "CI-PIPELINE: true". If that trailer is found, the job looks for these others: ARCHS, CI_COMPILE, CI_CONTAINER, CI_PIPELINE, DISTROS, DWZ, FLAVOR, SCCACHE Any that are found are passed as parameters. [0] https://git-scm.com/docs/git-interpret-trailers Signed-off-by: Zack Cerza <[email protected]>
This may ultimately replace the existing ceph-*build jobs; for now, it is a
work in-progress.