You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am requesting that an option be added that would allow the resource to not immediately return new versions found. Basically, if this option is set, after a new version is found, the resource will wait for a specified period of time before indicating that there is a new version.
We currently have a GitHub action that updates the version in a package.json when commits are made to master. Sometimes that results in 2 concourse builds (1 from the initial commit to master, 1 from the automated commit bumping the version) but sometimes it only results in 1 concourse build (from the automated commit). This is of course because when checks are made every minute it may occur after the initial commit but before the automated commit from the action.
I'm not entirely sure how this would work, but I could imagine that the process that does the check for a new version could simply wait for the specified period of time before returning what it found. It could periodically check for newer commits and grab those instead for what gets returned when the quiet period expires.
The text was updated successfully, but these errors were encountered:
I am requesting that an option be added that would allow the resource to not immediately return new versions found. Basically, if this option is set, after a new version is found, the resource will wait for a specified period of time before indicating that there is a new version.
We currently have a GitHub action that updates the version in a package.json when commits are made to master. Sometimes that results in 2 concourse builds (1 from the initial commit to master, 1 from the automated commit bumping the version) but sometimes it only results in 1 concourse build (from the automated commit). This is of course because when checks are made every minute it may occur after the initial commit but before the automated commit from the action.
I'm not entirely sure how this would work, but I could imagine that the process that does the check for a new version could simply wait for the specified period of time before returning what it found. It could periodically check for newer commits and grab those instead for what gets returned when the quiet period expires.
The text was updated successfully, but these errors were encountered: