Allow location of FlowExecutionList.xml to be overridden
#312
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
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.
Matches jenkinsci/jenkins#8531 and uses the same system property for a similar purpose in CloudBees CI (not needed for OSS Jenkins). Ideally
FlowExecutionListcould be dispensed with as it duplicates information (the set of running Pipeline builds); unfortunately the system of lazy-loadingbuild.xmlfrom the filesystem, and the fact that the latest build of a job (or even the latest 100 builds) are complete while some earlier builds remain running, makes it impossible to efficiently enumerate these, which must be done in order to ensure that builds are resumed.