concourse
Ability to specify maximum number of retries?
Recently, I have this problem during rebase that it's causing an infinite loop
Is there a way to specify a "max retry" count? Or some other way to have the job fail after a certain amount of time?
Thank you for your time, I appreciate it.
Experiencing the same issue
Identity added: /tmp/git-resource-private-key (/tmp/git-resource-private-key)
rebasing...
From github.com:cloudfoundry/bosh-deployment
* branch develop -> FETCH_HEAD
* [new branch] develop -> push-target/develop
Already up to date.
Successfully rebased and updated refs/heads/develop.
Updated tag '270.5.0' (was 942d6dc)
To github.com:cloudfoundry/bosh-deployment
! [rejected] 270.5.0 -> 270.5.0 (already exists)
error: failed to push some refs to '[email protected]:cloudfoundry/bosh-deployment'
hint: Updates were rejected because the tag already exists in the remote.
rebasing and trying again...
rebasing...
From github.com:cloudfoundry/bosh-deployment
* branch develop -> FETCH_HEAD
Already up to date.
Successfully rebased and updated refs/heads/develop.
To github.com:cloudfoundry/bosh-deployment
! [rejected] 270.5.0 -> 270.5.0 (already exists)
error: failed to push some refs to '[email protected]:cloudfoundry/bosh-deployment'
hint: Updates were rejected because the tag already exists in the remote.
rebasing and trying again...
rebasing...
From github.com:cloudfoundry/bosh-deployment
* branch develop -> FETCH_HEAD
Already up to date.
Successfully rebased and updated refs/heads/develop.
To github.com:cloudfoundry/bosh-deployment
! [rejected] 270.5.0 -> 270.5.0 (already exists)
error: failed to push some refs to '[email protected]:cloudfoundry/bosh-deployment'
hint: Updates were rejected because the tag already exists in the remote.
rebasing and trying again...
rebasing...
From github.com:cloudfoundry/bosh-deployment
* branch develop -> FETCH_HEAD
Already up to date.
Successfully rebased and updated refs/heads/develop.
To github.com:cloudfoundry/bosh-deployment
! [rejected] 270.5.0 -> 270.5.0 (already exists)
error: failed to push some refs to '[email protected]:cloudfoundry/bosh-deployment'
hint: Updates were rejected because the tag already exists in the remote.
rebasing and trying again...
I am wary of using force in order to force the tag push.
We have the same issue. It really should fail after a few retries (there should be a default max number of retries).
After submitting a PR for this, I realized concourse already has a timeout option which will stop the step after some time. In the absence of retries I think that should do the trick.
Workaround provided by @spion to use the timeout step modifier. Closing this issue since it's not worth fixing since timeout will get you the same behaviour, albeit slightly less robust.
