Enable Release Management for the configured Bamboo Plan
Asked by KGolbang:

hello there,  

I've installed the latest Version of Bamboo ( 4.4.0) and added a new plan to it (which is actually a Maven project that compiles successfully). By now, I want to use the release management plugin as described in here: [http://blogs.atlassian.com/2010/09/bamboo_jira_release_management_plugin_part_2/
Actually](http://blogs.atlassian.com/2010/09/bamboo_jira_release_management_plugin_part_2/%3Cbr%3E%3Cbr%3EActually), there should be a checkbox "Enable release management" in the section "Miscellaneous" inside a plan configuration which unfortunately doesn't appear in my Bamboo instance. There are two checkboxes only: build expiry and maven artifact sharing.  

Should I install an additional software or provide another configuration?  

thank you in advance  
kind regards  

K. Golbang


Answers:
author: SGD
body: Hi Katerina-

I brought this to the attention of our support engineers, and they said they'd be happy to do a screen-share session with you and figure this out. File a ticket at [support.atlassian.com](http://support.atlassian.com), and they'll get back to you shortly.

We can post the results back here, for posterity :o)


author: John Chin
body: Hi,

Perhaps, you can try the answer here [https://answers.atlassian.com/questions/117730/error-when-releasing-from-jira-to-bamboo-no-active-plans-bamboo-server-has-not-returned-any-plans](/questions/117730/error-when-releasing-from-jira-to-bamboo-no-active-plans-bamboo-server-has-not-returned-any-plans)

If you run any proxy or SSL configuration behind JIRA or Bamboo instance, please try bypass and see how it goes.

Cheers,

John Chin


author: Harry Christodoulou
body: Is there a solution or answers to Katerina's questions?


author: Brad Holmes
body: I am having exactly the same problem ... was this ever sorted out?


author: PiotrA
body: Hello Katarina,

I think that maybe you should contact <http://support.atlassian.com> - there Atlassian Support Engineers might be able to better help you (they have large experience with supporting Bamboo and Jira product, so I speculate they might have better understanding the problem you're encountering). And if you're evaluating Bamboo I'm certain you're entitled for the Atlassian Support.

As for me, I think that you're using wrong plugin. I've looked at the <http://blogs.atlassian.com/2010/09/bamboo_jira_release_management_plugin_part_2> and it describes how to use 3rd party plugin, which was AFAIK deprecated around Bamboo 3.2 and was replaced with atlassian's bamboo-jira-plugin (this one: <https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugin.ext.bamboo> ). So... may I ask what are you trying to achieve and with which plugins?

Also, can I ask you whether you have seen these docs:  
\* <https://confluence.atlassian.com/display/BAMBOO/Integrating+Bamboo+with+JIRA>\* <https://confluence.atlassian.com/display/JIRA/Running+a+Bamboo+Build+when+Releasing+a+Version>

...I'm asking because I'd like to know if we stand on the same ground.

regards,   
Piotr Stefaniak  
Bamboo developer

comments: author: KGolbang
body: Hi Piotr,

thank you for your answer and sorry because of the inaccurate information.

I'm running JIRA (port 8180) and Bamboo (port 8085) at the same machine. They are connected (bi-directional) by the application link. Additionally, the JIRA plugin

<https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugin.ext.bamboo>

is installed as well (I've checked this)!

And they (JIRA + Bamboo) can already "speak" with each other! As long as I provide an issue identifier for my subversion commits the builds appear in JIRA accordingly.

My issue is actually related to the Release management. Apparently, JIRA doesn't recognize which Bamboo plan should be associated with it.

As you can see in JIRA Screenshot # 1 the Bamboo builds are displayed in JIRA (because I provided the issue number in my subversion commits).

![](../../upfiles/jira_bamboo_1.png)

The are also associated with the particular issue (JIRA Screenshot # 2).

![](../../upfiles/jira_bamboo_2.png)

**BUT they aren't associated with a version (JIRA Screenshot # 3).**

![](../../upfiles/jira_bamboo_3.png)

... and ... it's not possible to enable the built-in release managment inside Bamboo either (see Bamboo Screenshot #1).

![](../../upfiles/jira_bamboo_4.png)

My Bamboo project is a Maven 3 project (clean install). What should I configure or change in my project POM to get the automated release management enabled?

Are there any conventions I should consider? Should I set some Bamboo variables or should I provide some properties in my POM?

One more question: is the Bamboo release management implementation suitable for multi-module (reactor) maven projects as well?

Thank you in advance!

K. Golbang


author: KGolbang
body: **We are about to buy a Bamboo licence but as long as we're struggling with this kind of problems it's not easy to put it into operation.**

We need support regarding the integration of Bamboo \<--\> JIRA.

We are running the following versions:

\* JIRA version v5.1.5#784-sha1:6c72993

\* Bamboo Version 4.4.0 build 3501 - 28 Jan 13.

The both of them are connected by the Application Link (Trusted, JIRA to Bamboo and vice versa).

The following phenomenons occur:

\* JIRA: when klicking "Release" button then the message "No active plans. Bamboo server has not returned any Plans." is displayed.

\* Bamboo: when I go to the section "Plan configuration / Miscellaneous" there isn't any "enable release management" checkbox!

Why? What should I do to get them integrated? What should I do to enable the release management?

Thank you!


Tags: app

management

release