This repository has been archived by the owner on Sep 8, 2024. It is now read-only.
Add resource lock tests in Jenkinsfile #2522
Merged
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
devs-mycroft
added
the
CLA: Yes
forslund
force-pushed
the
bugfix/Jenkins-file-branch-lock
branch
from
bab5364
to
5f71d32
Compare
forslund
changed the title
chrisveilleux
approved these changes
Apr 1, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Add a lock for the pipeline, different branches were able to run on top of each-other since each branch/pr gets a separate "job"
This lock is global across the pipeline and will force all branches to wait for the Lock to be free.
Things that needs this lock seems to be
The allure data could possibly be handled without the lock by creating a temporary directory for each run.