Not expecting deployment to occur when an older build is run after a newer build. In my case x.0.96 was built and deployed after x.0.97 as two commits were present in a single push.
Building a earlier commit results in a deployment over a newer commit
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
#1 Posted by Feodor Fitsner Support staff on 02 Jun, 2014 06:37 PM
Hi Bryan,
Meaning you did a second commit (0.97) while the first one's build was in "queued" state and second build came through first?
#2 Posted by bryan on 03 Jun, 2014 07:31 AM
No,
I pushed two commits at the same time (A -> B) where A is the parent commit of B
A gets added to build queue as 0.96
B gets added to build queue as 0.97
0.97 gets built first then deployed
0.96 gets build second then deployed
I end up with an older commit and build deployed
Thanks :)
#3 Posted by Feodor Fitsner Support staff on 03 Jun, 2014 04:51 PM
So there were two pushes, right? AppVeyor uses "head" commit only from push webhook payload, so it's always one push - one build.
We deployed an update yesterday which fixed incorrect ordering of running builds. That should fix the issue with immediate subsequent pushes.
Let me know if it happens again.
#4 Posted by bryan on 05 Jun, 2014 04:47 AM
That's fixed my issue and sorry it must've been two pushes >.<
Thanks for the help :)
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:44 AM.