nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to link a bamboo build to a Jira release version (yet another backward step in Jira cloud?)

Chris Mann

I have found this reference which suggests that you can no longer link bamboo builds with a release version in Jira.

Does anyone have any suggestions on how to relate the information? Or is this just another case of something that the cloud version doesn't do?

Just seems like everything I try to do in the Jira cloud is difficult or not possible compared to the Jira server (and so far, definately NOT a cheaper solution!)

Unsupported features

Bamboo: Running release builds when releasing a version

Running Bamboo release builds when releasing a version in Jira Software Cloud is being deprecated in December 2021, and you won’t be able to use it. For more info, see Run a Bamboo build when releasing a version.

Accepted answers

Aron Gombas _Midori_

Can't you replace the old mechanism with an automation rule using the following components?

trigger: "version released" (trivial)
action: "send web request" (use it to send a request to the Bamboo REST API end-point that starts a build)

It should be rather straight-forward.

All comments

Aron Gombas _Midori_

Can't you replace the old mechanism with an automation rule using the following components?

trigger: "version released" (trivial)
action: "send web request" (use it to send a request to the Bamboo REST API end-point that starts a build)

It should be rather straight-forward.

Chris Mann

Thanks. - I have a plan building now!

But, a couple of follow on questions that I hope you might have suggestions for:

1. Is there a way to prevent the version being released if the build has failed?

2. How would I then link the artifacts from this specific build to this specific release version?

Thanks!

Aron Gombas _Midori_

I don't think it is possible because the rule will execute when triggered by the release created. What you could do is that in the Bamboo side, add an "error handler" to your build which would connect back to the Jira REST API and "unrelease" the version! It should be totally possible.
The trigger's doc says that the trigger will populate the smart value {{version}} to the rule. you can access it with your "send web request" action and pass that to the Bamboo side. Then in Bamboo, you could add it as metadata to the artifact (if Bamboo supports labels, for example) or just create a directory with the version's name and produce the artifacts there. The bottom line is that you can see the version which triggered the build!

Chris Mann

Aron,

Thanks - good suggestions, just very frustrating because this all works seamlessly with Jira Server and has been taken away by the forced move to the cloud offerings!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bamboo

jira-software

jira-software-cloud