This repository has been archived by the owner on Oct 22, 2021. It is now read-only.
Remove "version: every" when "passed:" contraints are defined #1243
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
because that blocks automatic triggering of jobs concourse/concourse#736 This combination of settting was introduced when we tried to force Concourse to run later jobs on every version that passed the previous one. E.g. ver1 passed job 1, ver2 passed job 1 job2 should trigger both for ver1 and ver2 otherwise ver1 would never be tested on job2. The new scheduling algorighm may have solved this: https://concourse-ci.org/scheduler.html#scheduling-behavior Given our pipeline needs us to manually trigger jobs all the time, this worths a shot.
|
See "Breaking change" here: https://github.com/concourse/concourse/releases/tag/v6.0.0 |
prabalsharma
approved these changes
Aug 21, 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.
because that blocks automatic triggering of jobs
concourse/concourse#736
This combination of settting was introduced when we tried to force
Concourse to run later jobs on every version that passed the previous
one. E.g.
ver1 passed job 1, ver2 passed job 1
job2 should trigger both for ver1 and ver2 otherwise ver1 would never
be tested on job2. The new scheduling algorighm may have solved this:
https://concourse-ci.org/scheduler.html#scheduling-behavior
Given our pipeline needs us to manually trigger jobs all the time, this
worths a shot.