feat(jenkins-jobs) allow disabling git tag discovery #797
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…uild strategy) Signed-off-by: Damien Duportal <[email protected]>
dduportal
changed the title
lemeurherve
approved these changes
Sep 25, 2023
This was referenced Sep 25, 2023
dduportal
deleted the
feat/jenkins-jobs/allow-disabling-tagdiscovery
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We see a lot of problems in our
updatecliprocess when run from our Jenkins controller infra.ci.jenkins.io.The root cause is that the jobs in charge of running updatecli are running a lot of concurent builds at the same time.
This PR allows to disable the tag discovery (and associated buidl strategy) as a step in solving this large scale problem.
Note that I used a double negation because Helm interprets
falseas emptiness so it's hard to have an easy way without breaking existing.