Menu
How do I set up TeamCity so that it does not publish build artifacts if the build fails because a unit test failed? I'm pretty sure it worked this way prior to version 6.0, but since upgrading to 6.0 it always produces artifacts even if a test fails. I have "Fail build if at least one test failed" checked.
We had an outage with the e-mail notification and I didn't know we had a build problem because it continued producing artifacts.
556
On the Project Settings page, open the Actions menu and click Pause/Activate. In the dialog that opens, clear the box next to the project to activate all its build configurations or clear the boxes of the configurations selectively: the unselected build configurations will be activated.
Automatic Clean Checkout You can also enable automatic cleaning the sources before every build, if you check the option Clean all files before build on the Create/Edit Build Configuration> Version Control Settings page. If this option is checked, TeamCity performs a full checkout before each build.
Another build failure condition causes TeamCity to mark build as failed when a certain text is present in the build log. To add such failure condition, click Add build failure condition and select from the list: Fail build on metric change.
The artifacts are stored on the server "as is" without additional compression. By default, the artifacts are stored under the <TeamCity Data Directory\>/system/artifacts directory which can be changed. You can configure an external artifacts storage to replace the built-in one.
Please watch/vote for this issue: http://youtrack.jetbrains.net/issue/TW-12194
97
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
