Pointed here from this question on Slack and related to #358: "is there any way to ask the input git resource for the all the "skipped" commits since the last one which was built by a given job? E.g. to provide that list info to a task which publishes all of the commits which could have caused a build to fail?" -

For jobs that are expensive (e.g. long builds) I would like a way to still use the "latest" version (i.e., not "every" as described in #358 because running for every version especially across feature branches could exhaust CI resources), but still allow the job to have access to the list of every version since the last build for that job (so you know the subset of builds which might have caused the failure, and could bisect those locally).