tag:help.appveyor.com,2012-11-13:/discussions/problems/368-building-a-earlier-commit-results-in-a-deployment-over-a-newer-commitAppVeyor: Discussion 2018-10-19T08:16:34Ztag:help.appveyor.com,2012-11-13:Comment/332241292014-06-02T18:37:38Z2014-06-02T18:37:38ZBuilding a earlier commit results in a deployment over a newer commit<div><p>Hi Bryan,</p>
<p>Meaning you did a second commit (0.97) while the first one's
build was in "queued" state and second build came through
first?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/332241292014-06-03T07:31:22Z2014-12-12T13:15:45ZBuilding a earlier commit results in a deployment over a newer commit<div><p>No,<br>
I pushed two commits at the same time (A -> B) where A is the
parent commit of B<br>
A gets added to build queue as 0.96<br>
B gets added to build queue as 0.97<br>
0.97 gets built first then deployed<br>
0.96 gets build second then deployed<br>
I end up with an older commit and build deployed</p>
<p>Thanks :)</p></div>bryantag:help.appveyor.com,2012-11-13:Comment/332241292014-06-03T16:51:14Z2014-06-03T16:51:14ZBuilding a earlier commit results in a deployment over a newer commit<div><p>So there were two pushes, right? AppVeyor uses "head" commit
only from push webhook payload, so it's always one push - one
build.</p>
<p>We deployed an update yesterday which fixed incorrect ordering
of running builds. That should fix the issue with immediate
subsequent pushes.</p>
<p>Let me know if it happens again.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/332241292014-06-05T04:47:48Z2014-12-12T13:15:45ZBuilding a earlier commit results in a deployment over a newer commit<div><p>That's fixed my issue and sorry it must've been two pushes
>.<</p>
<p>Thanks for the help :)</p></div>bryan