'Fail and stop build if number of code duplicates is more by at least 1 compared to the latest successful build' executed after all build steps
Hi. Failure condition 'Fail and stop build if number of code duplicates is more by at least 1 compared to the latest successful build' is executed after all build steps in the end of the build process. Is it possible to force TeamCity to check code duplicates immediately after the build step which run duplicates finder? In my last build step I send the package to Octopus, but failure condition for code duplicates is execute afterwords. As a result, build failed but the package is pushed to Octopus. In the failure condition itself I ticked the box next to 'Immediately stop the build if it fails due to the condition' item.
How this can be prevented? All I need is to check failure condition straight away after duplicates finder build step.
Thanks.
Please sign in to leave a comment.
Hi Stanislav,
could you send us the build log of a build where it should have stopped and it didn't? Please use the submit a request button above for it.
While we investigate it, a workaround would be to send the package to octopus in a separate build configuration, tied by a snapshot + artifact dependency. Because of the failed build (which should be marked as failed), the snapshot dependency shouldn't execute.