Package should be build after tests
Maybe I am wrong, maybe I am too old, but don't you think that building your nuget package should be done _after_ the tests are run? In that way we will be sure we have nuget packages that actually pass our tests.
And this refers to automatic nuget packaging, yes, I know I can build my custom powershell script and do the packaging (or invoke nuget pack or something from my yaml).
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 27 Jul, 2015 07:42 PM
It's packaged during the build phase, but uploaded and published after test phase, so if tests fail it won't get uploaded/published.
2 Posted by Cristian Prieto on 27 Jul, 2015 07:45 PM
Does this mean I won’t get the artefact if test fails?
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.
--
Cristian Prieto
Sent with Airmail
Support Staff 3 Posted by Feodor Fitsner on 27 Jul, 2015 08:39 PM
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 after tests.
4 Posted by Cristian Prieto on 27 Jul, 2015 08:43 PM
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.
I guess this won’t be a problem with AppVeyor.
--
Cristian Prieto
Sent with Airmail
Support Staff 5 Posted by Feodor Fitsner on 27 Jul, 2015 08:44 PM
Ah, OK then :)
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:58 AM.