This repository has been archived by the owner on Nov 16, 2020. It is now read-only.
Workaround for scheduling issue in concourse #373
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
imikushin
approved these changes
Apr 11, 2018
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.
Sometimes jobs are not getting triggered multiple jobs in a single pipeline run together, and they don't finish in order they were triggered by PRs (see issue concourse/concourse#736). This patch adds a workaround mentioned in concourse/concourse#736 (comment). In essence, the
timeresource is used as an additional trigger. Whenbuild-imagesfinishes, it updates the time resource, effectively creating new version of it, which in turn will trigger the tests jobs. Because the time resource is updated at the end ofbuild-imagesjob, it's not affected by the time it takes to finish the job.