A push of 40 tags to GitHub causes job numbering disaster!
Accidentally I have
pushed all my local git tags and many jobs have been created.
Some of them got renamed to something like
129-dup-lkg2ibgg and failed immediately with an error
messageBuild
version 129 already existed and a random string was appended to its
version to avoid collision. Update next build number or change
version format.
(why? what if I wanted really to queue them all?).
Worse still, some of them still retain the original number. I
have five jobs #131 (plus two detected duplicates) at the moment.
Those additional #131 cannot be cancelled - clicking on "cancel" on
the history list has no effect, and doing hat on the job detail
page results in The build has finished already.
message.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 09 Sep, 2015 02:06 PM
I've reset build jobs under your account, so new builds could be started.
Well, that was a great stress test! :) Looks like there was racing condition while working with database. Definitely, build version counter reliability should be improved.
Support Staff 2 Posted by Feodor Fitsner on 09 Sep, 2015 02:07 PM
Added a bug: https://github.com/appveyor/ci/issues/405
3 Posted by saper on 09 Sep, 2015 10:24 PM
Thank you! There is also a milder Github-related issue https://help.appveyor.com/users/3388534, where two builds are started where one would suffice.
saper closed this discussion on 10 Sep, 2015 06:49 AM.