How to force Snapshot dependency and promote the build

Scenario: we have three configurations Build, Test and Deploy. Test has Snapshot and Artifact dependency on Build. Deploy has Snapshot and Artifact dependency on Build AND Snapshot dependency on Test. The point is - Deploy must wait for tests to pass and then deploy the artifacts created by Build.

Now imagine we have "emergency" build. It is compiled, but we don't have time to go through tests - we want that build to be promoted to Deploy.

We go to Build, select the one we want and do Actions->Promote to Deploy.

I have attached the picture of the dialog we get. It shows two dependencies for Deploy. For the first one we have that build we want preselected. But second one says Auto and another option is Rebuild. In either case Deploy does not start until the second dependency (snapshot dependency on Test) finishes,

Question - how to force it through? How to tell it - ignore snapshot dependencies, just process artifacts created by particular build.


Thank you!
Konstantin



Attachment(s):
PromoteDialog.png
4 comments
Comment actions Permalink

Hi Konstantin,

It is not possible to ignore snapshot dependency, cause it's contrary to the logic of dependencies. I would recommend you to create a separate build configuration for emergency deploy which depends only from Build build configuration. You can extract template from existing Deploy build configuration and create new one based on this template.

0
Comment actions Permalink

When we "promote" the build we basically command the next build in chain to start taking particular version of dependent build.

Now when we have configuration (Deploy) which depends on two other configurations it seems logical to be able to Promote BOTH dependent builds and have Deploy run on very specific versions of dependent builds.It is not "ignore", it is more like "force".

Anyway I understand your advice and probably going to take it for the lack of better options.

Thank you!
Konstantin

1
Comment actions Permalink

Is there any progress? May be some new workarounds or issue to vote?

0
Comment actions Permalink

Hi Max,

there is no new workaround. The solution proposed by Alina was and is still the best way to approach this scenario: Create a template out of the build configurations, and two different configurations that have the different set of dependencies. Both "final" builds can depend on the same initial build but will have different dependencies (one depends on both build and test, the other only on build)

0

Please sign in to leave a comment.