-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Branch strategy on ci.jenkins.io diverges from prior configuration #3650
Comments
Caused by the operation in #3535 |
@NotMyFault for which job(s) do you see this behavior? |
For the https://ci.jenkins.io/job/Core/ organization scanning, applying the following change (will trigger and indexation):
|
Applied recursively, the "Abort build" option is now present on each. |
I did a quick demo earlier with jenkinsci/console-column-plugin#123:
Shouldn't that be applied to every folder? We don't really need to index archived repositories anywhere. |
For the https://ci.jenkins.io/job/Plugins/ organization scanning, applying the following change (will trigger an indexation):
|
Thanks! Applying to the "Plugins" org scanning (#3650 (comment)). Brace youselves.
100% agree with you. Worth working on #3071 |
Ran with success (and only 1 rate limit). Result:
|
For the https://ci.jenkins.io/job/Tools/ organization scanning, applying the following change (will trigger an indexation):
|
|
For the https://ci.jenkins.io/job/Infra organization scanning, applying the following change (will trigger an indexation):
|
|
For the https://ci.jenkins.io/job/jenkinsfile-runner organization scanning, applying the following change (will trigger an indexation):
|
|
For the https://ci.jenkins.io/job/jenkinsci-libraries organization scanning, applying the following change (will trigger an indexation):
|
|
For the https://ci.jenkins.io/job/Packaging/ organization scanning, applying the following change (will trigger an indexation):
|
|
For the https://ci.jenkins.io/job/Stapler/ organization scanning, applying the following change (will trigger an indexation):
|
|
Setup applied everywhere. I'm closing, thanks @NotMyFault ! Feel free to reopen if I missed anything! |
Service(s)
ci.jenkins.io
Summary
The previous configuration aborted branch builds, once a PR has been created (e.g., dependabot/renovate, or when working directly on the repository). That's no longer the case. Currently, if you create an upstream branch and a PR, both are built, doubling the prior workload.
Reproduction steps
No response
The text was updated successfully, but these errors were encountered: