Disable auto setting on dependencies
Is it possible to disable the auto settings in the dependency view? or make someone have to pick an explicit action?
Example:
We have 3 dependencies, 2 are set to just artifact dependencies on latest successful one.
the last one is set to a snapshot dependency and you're allowed to pick a branch from the snapshot in the changes screen.
If you do, auto seems to pick a random build (containing the commits on the branch + more).
whereas `rebuild` does the right thing. I guess the problem is the system's believe that a branch containing commits is equivalent to a branch with ONLY those commits?.
Concretely, is there a way to force someone to make a choice on the dependency tab? They may want auto, rebuild or whatever but I want them to explicitly choose to avoid the ambiguity.
Please sign in to leave a comment.
Hello Tamar,
The 'auto' option would normally reuse the build according to your Artifact Dependency settings. E.g. if the artifact dependency is configured to take the artifact from the build from the same chain, the 'auto' option will do that. Which option do you have there? Also, could you elaborate on the part regarding the "random build", possible with examples? What do you mean by "containing the commits on the branch + more"?
-Anatoly
Register for TeamCity Technology Day - Nov 5th
Hi Anatoly,
For the "Last successfu build" or "Pinned Build" artifact dependencies auto's behavior is pretty obvious and as expected.
However for "enforce dependency synchronization" and "buid from the same chain" the auto setting seems to be erratic.
As described here https://youtrack.jetbrains.com/issue/TW-67440#focus=Comments-27-4472325.0-0 you can do it a couple of time and the auto will pick the build it previously made.
However every so often it rebuilds the dependency. My guess here is because some other branch changed in the multi vcs build. Note I also have "Do not run new build if there is a suitable one" unchecked because teamcity was merging builds when it doesn't.
What I don't get is, if the branch corresponding to the dependency doesn't change, why does it randomly think it needs to rebuild. Is there any log for this?
Thanks,
Tamar