-
Notifications
You must be signed in to change notification settings - Fork 26
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 Copr nightly test pipeline #349
Add Copr nightly test pipeline #349
Conversation
f00da79
to
7504f47
Compare
I am using these as a playground, we do not necessarily need independent jobs in the end. I've expressed this here the options as I see them: |
This will be adapted based upon the approach settled with the client -- #351 |
1d26169
to
855d4a2
Compare
bf4eee7
to
89de1a4
Compare
89de1a4
to
9d939a6
Compare
Proposed order of operations:
|
|
||
steps { | ||
script { | ||
runDuffyPipeline('foreman-rpm', foreman_version) |
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.
should/could this pass staging_source
somehow, so we don't need theforeman/forklift#1717?
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.
mhh, runDuffyPipeline
doesn't allow us to pass arbitrary parameters to the job, so probably not so easy.
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.
I reached the same conclusion. However, forklift should match CI if someone goes to run things so I think it's OK.
No description provided.