Personal Build snapshot dependency on a normal build
Answered
Hello, we have a snapshot dependency of build configuration A->B (and reusing a suitable build of B if available). Now this works well when A is a normal build, which makes B also a normal build. However, if A is being triggered as a personal build with changes, B also becomes personal. Our requirement is to force B to always be a normal build, and not personal build with changes. Is this possible?
Please sign in to leave a comment.
Hello,
What TeamCity version do you use? How the builds A and B are triggered?
We are using TeamCity 10.0.4 (build 42538). The build A is triggered via command-line remote run, and we want B to be triggered as a normal snapshot dependency when A is triggered.
The requirement is that there we want to compare certain statistics (via artifacts) on the main integration branch with respect to the build triggered as a personal build, and fail the personal build if the comparison is negative.
When build A is triggered by the user as a personal build, there might already be certain changes on the main branch since the last time B was built, so we want to build B as a snapshot dependency and as a normal build (so that it can be used in further private builds of A, and counted as a suitable build), and use that to compare the statistics.
At the moment this is by design behavior. Please feel free to create a feature request and describe your use case.