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
jenkins: build all job #1711
Comments
Makes sense.
Nope. The phrase sounds good to me. |
If we also want to exclude the build jobs that were executed by default, we might better have two phrases:
("build all" is still relevant if master is changed because this wont trigger the default build jobs for the PRs) |
You are right. In that case I am for including the PR build jobs too. The simplification (only one special build phrase) should make up for the overhead of building the PR jobs twice. |
I just added the new build phrase to the triggers of almost all jobs. I did not incorporate the phrase in the build jobs
, since I am not sure that building the packages makes much sense in the case of a pull request. I also did not attach the phrase to
. Do you think we should add some of the build jobs above to |
Thank you so much, its great to have Yes, the buildpackage jobs do not work for PRs. I do not know what PR-checks is for, afaik it was created by @BernhardDenner The |
I am already working on it.
Okay. I just added the phrase to both jobs. |
We now can use the phrase jenkins build all please to build (almost) all Jenkins jobs. This commit closes ElektraInitiative#1711.
As proposed by @sanssecours we could add the "jenkins build all please" phrase to every build job.
This way we could avoid merging PRs that break some build job.
Maybe we should exclude the build jobs that are already triggered immediately anyway?
Any suggestions for a better name than "jenkins build all please"?
(see also #160)
The text was updated successfully, but these errors were encountered: