opened
vito
username_0
When a resource is pinned, it should only take effect for jobs that use the input without `passed` constraints.

Otherwise pinning would imply that all of those jobs need to run with a set of candidates which both use the version and satisfy the `passed` constraints. In practice, a user is not likely to want all of those jobs to fire at once; instead it makes more sense for the farthest upstream job to run with the pinned version and then propagate it downstream gradually.
Pinning and `passed` constraints should be mutually exclusive
issue
created
vito
username_0
Closing per https://github.com/concourse/concourse/issues/5274
comment
closed
vito
username_0
issue