tag:help.appveyor.com,2012-11-13:/discussions/suggestions/752-package-should-be-build-after-testsAppVeyor: Discussion 2018-08-25T01:58:19Ztag:help.appveyor.com,2012-11-13:Comment/374908202015-07-27T19:42:38Z2015-07-27T19:42:38ZPackage should be build after tests<div><p>It's packaged during the build phase, but uploaded and published
after test phase, so if tests fail it won't get
uploaded/published.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/374908202015-07-27T19:45:27Z2015-07-27T19:45:27ZPackage should be build after tests<div><p>Does this mean I won’t get the artefact if test fails?</p>
<p>Yes, I understand this, I already figured out when the package
is build and that it is not going to be published if it fails, but
any reason why the order is in that way? I am just asking if there
is any technical reason why you do that.</p>
<p>-- Cristian Prieto<br>
Sent with Airmail</p></div>Cristian Prietotag:help.appveyor.com,2012-11-13:Comment/374908202015-07-27T20:39:06Z2015-07-27T20:39:17ZPackage should be build after tests<div><p>Right, you won't get artifact if test fails. But what's you goal
then? In the initial post you were asking about building package
<em>after</em> tests.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/374908202015-07-27T20:43:51Z2015-07-27T20:43:51ZPackage should be build after tests<div><p>I understand, nothing wrong. We had some issues with other CI
providers/servers when building the package before tests, for
example, we ended up with packages build and published even when
the test phase was failing.</p>
<p>I guess this won’t be a problem with AppVeyor.</p>
<p>-- Cristian Prieto<br>
Sent with Airmail</p></div>Cristian Prietotag:help.appveyor.com,2012-11-13:Comment/374908202015-07-27T20:44:38Z2015-07-27T20:44:38ZPackage should be build after tests<div><p>Ah, OK then :)</p></div>Feodor Fitsner