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 have verified this is the correct repository for opening this issue.
I have verified no other issues exist related to my request.
Is Your Feature Request Related To A Problem? Please describe.
When we create a hotfix branch, TeamCity picks up the new reference and starts a build. Because the build is on a tag, it initiates all of the signing and other tagged requirements. This means it will get a version that is already published, and it will also sign the artifacts.
Describe The Solution. Why is it needed?
At some point in the recipe (I imagine it being after determining the version to use), determine if the version being built has already been published, if it has already been published abort the build (either success or failure, doesn't really matter, although success reduces alert fatigue).
Additional Context
It is possible that this logic is better stored in the TeamCity configuration. If that's the case we can close this issue and open issues on the corresponding repositories.
Related Issues
No response
The text was updated successfully, but these errors were encountered:
Checklist
Is Your Feature Request Related To A Problem? Please describe.
When we create a hotfix branch, TeamCity picks up the new reference and starts a build. Because the build is on a tag, it initiates all of the signing and other tagged requirements. This means it will get a version that is already published, and it will also sign the artifacts.
Describe The Solution. Why is it needed?
At some point in the recipe (I imagine it being after determining the version to use), determine if the version being built has already been published, if it has already been published abort the build (either success or failure, doesn't really matter, although success reduces alert fatigue).
Additional Context
It is possible that this logic is better stored in the TeamCity configuration. If that's the case we can close this issue and open issues on the corresponding repositories.
Related Issues
No response
The text was updated successfully, but these errors were encountered: