youngmon/atlassian-qna huggingface dataset:
Bamboo build radiators
Asked by CI Engineer:

Hi,

I am trying to setup Build radiator for my Bamboo environment and wanted to know what the available options are. I was not able to find any plugin unlike the many plugins available for CruiseControl and Jenkins. Are there no plugins for build radiators in Bamboo. My aim is to display the project status and also show the stages through which the project has passed.


Answers:
author: Mark McD
body: Adding to what James has said: if you have both Bamboo \& Jira and they are set up through Application Links, then you can add [Bamboo build gadgets](https://confluence.atlassian.com/display/JIRA/Adding+the+Bamboo+Plans+Gadget) to your Jira dashboards / wallboards for an even more complete project overview.

comments: author: James Dumay
body: Thats a great point Mark - the gadgets are really useful and underutilised!


author: riosjdmnsdf
body: @Moderator - pls ban this spam account.


author: James Dumay
body: No plugins are needed for setting up a radiator for Bamboo - we call them "Wallboards" and you can [learn more about them in our documentation](https://confluence.atlassian.com/display/BAMBOO/Displaying+the+wallboard).

comments: author: Andrei Markov
body: Is there a way to save filters so users can easily switch between Walls? Can predefined Walls be shared?


Tags: dashboard

wallboard
How to switch from using Source Repositories to Shared Repositories
Asked by dustingooding:

I have created a number of plans with individual source repositories defined per-plan (not really realizing that shared repositories were an option). Realizing I needed to make a change to all of them, I assumed there was a better way... shared repositories. So, I created a shared repository that mirrored how I set up my source repositories. Then I went and tried to reconfigure my plans to use this new shared repository.... but I can't figure out how. Any ideas? Surely I don't have to re-create all my plans from scratch...


Answers:
author: James Dumay
body: Once you have created your shared repository, browse to the Source Repositories tab of the plan you want to switch to the Shared Repository, click on the Repository in question and select the Shared Repository you have created useing the Source Repository dropdown.

comments: author: dustingooding
body: My issue was that the Shared Repositories being listed in the Source Repositories drop-down was non-obvious. I never even considered looking there. I made a suggestion that the label for that drop-down be changed to just "Repositories".
When upgrading can I skip versions
Asked by Samantha Burnside:

When we purchased the suite of tools, each tool had a download that specified "standalone". Is there a particular file we should use when getting the upgrades (WAR or TAR)? Also, is it recommended to upgrade by each version vs jumping? For instance we have Bamboo 3.4.3. is it OK to just get the latest version or do I need to get each version in between 3.4.3 and the latest version of 4.2?


Answers:
author: SimonS
body: Hi Samantha,

You should use the installer files (Linux/Windows). The War files are for users who are not using the built-in Tomcat server. The installers are the same as "standalone" and the TAR file is just a compression filetype (like .zip)

We recommend upgrading to each major version of a product (3.4.3 -\> 4.0 -\> 4.1 -\> 4.2) but it really depends on the types of changes that took place between versions. Study the release notes carefully - if major changes to the database took place in an upgrade, for example, you should be sure to upgrade to that specific version.

That being said, you may be able to make the jump from 3.4.3 right to 4.2 - I would file a support ticket just to be sure:

<http://support.atlassian.com>

-Simon

comments: author: Samantha Burnside
body: Thanks very much. I will start reading the release notes.


author: Samantha Burnside
body: Need to upgrade from Jira 4.4.4, FECR 2.7.10, Bamboo 3.4.3.


Tags: atlassian-support
Branch builds being triggered by default repository
Asked by AmitB:

I have a plan using our svn trunk and another branch of that plan in which I ,manually override the repository with a svn branch.

The problem is that branch builds are being triggered whenever any change is commited to the trunk as well as to the branch. How do I make the branch plan trigger only when a change has been commited to the trunk?


Answers:
author: Marcin Gardias
body: This should not happen. Either you have your branch misconfigured (for example it still references trunk because you have multiple repositories defined) or you found a bug.

Are you sure you don't have duplicate repository definition on your 'trunk' plan? Please verify and if you are still convinced that you got your plan right perhaps you should contact Atlassian Support. Bug reports posted there are handled much faster ;-)

comments: author: AmitB
body: I do have multiple repositories defined, but I am only able to override one in the branch plan. Is this a limitation in Bamboo?


author: AmitB
body: Sounds like we should upgrade to 4.2. Thanks!


author: Marcin Gardias
body: Yep, currently you can only override 1 repository (default) So if you have change detection on master plan configured to check more than 1 repo, branch will check them too.

However, in Bamboo 4.2 you have an option to override Build Strategy in Branches. Would that help?


author: Marek Podyma
body: It seams that in Bamboo 4.3.3 branch build overrides only Default Plan Repository. Other plan repositories remain untouched. Why?


author: AmitB
body: I upgraded to 4.2, but it' still not clear how to do this. When I override the Build Strategy, it allows me to pick which repositories to poll, but includes the same repositories (sub-folders) off the trunk. Is there a way to automatically use the same folders, but have the branch as the root of these folders?


Tags: branch

trigger
promotion plugin
Asked by Matt Florence:

I used to use a hudson feature (plugin maybe) that allowed for promoting builds to different environments. The basic idea is once someone is ready to deploy a new build to an enviornment they can click a button on any successful build and elect (on demand) for some other automation (rake) to deploy that build to some environment. I would expect something like this exists for bamboo, but I'm having trouble finding it.


Answers:
author: James Dumay
body: Have a look at [Bamboo Stages](http://blogs.atlassian.com/2012/01/continuous-delivery-with-bamboo-stages/)for setting up a deployment pipeline.

comments: author: Matt Florence
body: Cool. I looked briefly at stages but didn't notice the manual switch. This might do the trick nicely. Thank you.


author: James Dumay
body: No problems - would love to hear how it works out for you :)
Installation type query
Asked by Ewan Scott:

I have downloaded the Bamboo 4.2 EAR-WAR file from the website to a RHEL6 server. The file atlassian-bamboo-4.2.1.zip just unzipsall files fully to the current directory. There is no WAR file as in install instructions on the website. Can you confirm that it is just the installation instructions which are out of date and I do not have the wrong version of the software.

Thanks.

Ewan


Answers:
author: Nic Brough -Adaptavist-
body: (Apologies for the last answer, I was aiming a Jira installation query at a colleague and got confuddled)

The file you have downloaded is a .war file. I'm guessing you are using Internet Explorer, which has a (deliberate and stupid-by-design) bug in it in that it renames files as .zip without even bothering to tell you, let alone bothering to think about why the files are named correctly.

Take the downloaded file, rename it from xxx.zip to xxx.war and proceed as the instructions say.


author: Nic Brough -Adaptavist-
body: You have to build the WAR from the unzipped file you downloaded.


Tags: install
Should Bamboo password variables be visible in Metadata?
Asked by Andre van der Schyff:

We are using passwords stored in global and plan variables, which for obvious reasons we don't want visible to everyone with access to the build results. While the password is correctly blanked out in the build logs, it is still visible in clear text in the 'Metadata' tab.

Is this by design? If so, how can we store passwords without having it visible from the build results screen? If not should I log an issue?

We are using Bamboo version 4.1 build 3100.


Answers:
author: Przemek Bruski
body: Bamboo hides variables with names containing the word "password" but unfortunately, not everywhere in the UI. There's a good chance this will be addressed in 4.3.

comments: author: Przemek Bruski
body: Update: it WILL be addressed in 4.3.


Tags: password
Upgrade SW versions first, then add more user licences - or the other way around?
Asked by Thomas Strangert:

Hi there,

We have just over a year ago (the licences has hence just expired) installed a basic package with a few Atlassian products, all on the up-to-10-users entry level or similar.

Products and versions we have now:

Jira v4.4.1#660-r161644

GreenHopper 5.7.1

Confluence 3.5.13

FishEye 2.7.11 Build:20120227023831

Crucible 2.7.11 20120227023831

Bamboo 3.2.2 build 2602

All of it now running on a Linux box with Apache.

We are now in the need to:

\* Upgrade SW versions (on most products)

\* Renew the support/upgrade licences

\* Add more user licences (at least for a few of the products)

\* We would also like to add a few new programs and plugins.

We would like to:

\* Increase the number of users in Jira and Confluence to 25.

\* I suppose that means that we also need to have 25 licences for GreenHopper?

\* Keep the number of user licences to 10 on the other products.

\* Introduce the Crowd product so that we can have single sign-on integrated with our Windows Server. This means moving the user/password management from Atlassian to Windows (I suppose?)

\* Perhaps later on also install the Salesforce (Jira plugin) and Sharepoint Connector (Confluence plugin)

My question is about your recommendation of in what order and steps to do all these things!

Regards,

Thomas


Answers:
author: Nic Brough -Adaptavist-
body: The new licenses will be compatible with all versions, so don't worry about the order too much. However, I'd be strongly tempted to do them first for one reason - you can't upgrade past the end of the license. For example, if your license ended yesterday, and Atlassian release Jira 5.2 tomorrow, you can't upgrade to it. You can't go higher than 5.1

You are correct about Greenhopper and Jira - you will need to make sure they have the same number of seats.

If you implement Crowd, then think of it as a two-part thing. First, you can remove user maintenance from the individual services and move it all into Crowd, which makes it all a lot more simple and centralised. The second step might be to integrate Crowd with some other system, so that it takes it's data from there (i.e. your Windows stuff) instead of using a local independent user base. I'd think of it as two distinct pieces of work, even though you might end up implementing them simultaneously (makes it easier to break up the work into manageable chunks, and debug stuff - if you can say "crowd and windows are fine, but it's not talking to Jira", that's easier to debug than "Jira won't accept my password")

comments: author: Thomas Strangert
body: Thanks,

Your answer is informative and to the point - and better than what I got from Atlassian's official support.


Tags: install

migration

upgrade
Can Bamboo automatically "copy" links to failed JIRA issues to next build?
Asked by Alexis Michaelides:

Say we have a build (call it x) which includes changes from 5 JIRA issues, and 1 of them causes the build to fail... The issue is then fixed, further code is committed against that issue, and finally a new Bamboo build is started (call it x+1).

My problem is that build x is no longer valid for us, as it never completed, but the latest successful build is x+1 which Bamboo thinks only has a fix for 1 issue - whereas in fact it contains all 5 issues since the previous build had failed.

I was looking for a way to have Bamboo automatically link to all JIRA tickets from previous failed builds in subsequent ones. This of course may happen more than once (where you have sequential builds failing until all the underlying problems are resolved).

I'm using locally hosted (downloaded) versions of Bamboo \& JIRA.

Any thoughts?

Thanks,

-Alex


Answers:
author: Przemek Bruski
body: Basically, for any green build you want to have a list of issues that went into this build and any previous failed build, right? If you need to have it in UI, you'd need to build a plugin for it.

If you only need the list, you can set up a relatively simple script using REST calls to Bambo to generate the issue list.

comments: author: Alexis Michaelides
body: In a perfect world we'd want this in both Bamboo UI and JIRA as well - we have a lot of tickets in JIRA where their last build is a failed one, and we have no quick way of finding which successful build contains that fix. This is not be as simple as saying it's in "failed build no + 1", as it may take several consecutive (failed) builds to get to a successful one.

I guess plugin is the best way to go, we'll have to do without for now as we don't have the resources to go down that path! I'll take a look at Bamboo's REST API to come up with an interim solution, thanks.

-Alex
Set Merge Options in Bamboo auto-merge
Asked by Collin O_Connor:

The title prettymuch says it all; in particular when using the autobranching with Branch Updater I'd like to have git use --no-ff. Is there a good way to set this there? As well as other options?


Answers:
author: James Dumay
body: There is no way to disable the fast forward merging at the moment but I [opened a feature request](https://jira.atlassian.com/browse/BAM-12147) for you so we can implement it in the future. Please watch and vote for it!
How to configure Ivy repository isolation?
Asked by Serge Dukic:

There's a section of the Bamboo documentation that deals with [isolating repositories for Maven executables](https://confluence.atlassian.com/display/BAMBOO/Configuring+repository+isolation+for+Maven+executables). We're running into similar problems with Ivy, when multiple stages are run in parallel and cause issues with the shared Ivy repository.

In order to solve this problem, we'd like to configure each agent to have their own isolated Ivy repository. This could be acheived if there was a Bamboo build-time variable identifying the agent that the build is being run on. However, looking at the [variable documentation](https://confluence.atlassian.com/display/BAMBOO/Using+global%2C+plan+or+build-specific+variables), I can't see any such variable. Does any such variable exist?

If not, does anyone else have any ideas how this might be resolved?


Answers:
author: Przemek Bruski
body: I don't think we have a variable for that atm. What you could do instead (apart from writing a plugin):

* on remote agents, set an environment variable in a script starting the agent. Your best option would be the content of \<id\> tag from bamboo_agent_home/bamboo-agent.cg.xml
* on local agents, it's trickier you can extract the id from variable called "build.working.directory" It will be the last number in the path right before the string avaialble in "buildKey" variable.

I've opened [an improvement request](https://jira.atlassian.com/browse/BAM-12153) to make agent id available via a variable - please watch and vote.

comments: author: Przemek Bruski
body: You can also use bamboo.agentId on recent versions of Bamboo.


author: jfghrthroioerio
body: spam


Tags: isolation

repository
sourcing environment in bamboo task?
Asked by Keyhan Hadjari:

I am a newbie using bamboo, I want to create a scenario like this:

1. Source a schell scripts to setup environment paths and generate tools

2. Used the generated tools and paths created in step 1. to run a command.

Since each task is run in a seperate shell seems like, step 2 is unaware of step one so its environment is clean from generated tools and environment variables in steup 1. So how do I do this?

thanks in advance.


Answers:
author: James Dumay
body: There isn't any way to source the environment so that all tasks use the sourced environment right now unless you call all your build commands within the one script task.
RE: Quarantined Tests
Asked by SHANNEL KAHIGA:

Is it possible to retrieve detailed information about a quarantined test for a particular plan in Bamboo using a REST API url? Example of information I would like to retrieve from the link can be; Name of Test, Name of Plan, Date, Associated JIRA and Quarantined by whom.

kind regards,

Shannel.


Answers:
author: SHANNEL KAHIGA
body: Sorry put my question in the wrong place. I have moved it to download

kind regards

Shannel.


Tags: cloud
Bamboo Windows instance doesn't use snapshot EBS
Asked by Zee:

I started a windows instance (Default bamboo windows ami)

Installed a whole bunch of stuff the instance is missing; like updates, .net mvc3, etc

Corrected nant script dlls

Configured scripts

Did a few builds to get source on there

Restarted a few times, built Again

in AWSCreated snapshot

Generated cert and key

Configured bamboo to use the snapshot

Terminated instance

Started new instance

Volume doesn't have any if the stuff I installed and configured. and is not using the specified snapshot EBS


Answers:
author: Zee
body: The real answer is that this isnt supporting out of the box

i ended up with this

<http://zxed.wordpress.com/2012/09/12/mvc3-net-continuous-integration-and-deployment-in-the-cloud-part-i/>


author: Przemek Bruski
body: EBS support for Windows will be available with Bamboo 5.


author: LucasA
body: Hello,

The best way is re-deploy your instance inside one EBS volume and boot up your instance directly form it: <http://4sysops.com/archives/amazon-ec2-boot-from-amazon-ebs-volumes/>

Please if you need any further assistance, raise a support issue on <http://support.atlassian.com>

Lucas Lima

Atlassian Support


Tags: aws

beanstalk

cloud

snapshot
Any plans for support for Bamboo 4.2+ in the eclipse connector?
Asked by Martin Eriksson:

Hi,

Just had a bit of a chock.. Upgaded from 3.3.1 to 4.2.1 of Bamboo, only to find out that the Atlassian Eclipse connector does not support this verison of bamboo!!!

if there are no plans to do this soon i see no alternative then to roll back the upgrade because if developers can not double click on failed tests inside eclipse they will never fix them and basically making bamboo pointless in my company..

please fix this soon as possible.


Answers:
author: Martin Eriksson
body: Hi sorry for this, I was searching around and i only came up with version 3.0.2! but clicking around here a bit i found references to 3.0.5! and then on the documentation page i found refernece to the 3.0.6! so finally found that and now updating the plugin.. so hopefully all will be well now..

thanks


author: jjaroczynski
body: Yes. Eclipse Connector 3.0.6 should work fine with new Bamboo.

Cheers,  
Jacek


author: jjaroczynski
body: Hi Martin,

What version of the Eclipse Connector do you use?

Cheers,  
Jacek


Tags: eclipse

ide-connector
Configuring an Ubuntu agent with Bamboo OnDemand
Asked by Tobias Cohen:

Any advice on how to setup Ubuntu on elastic cloud to use as a Bamboo agent? CentOS is not suitable for running our tests (QT library not available).

I've tried following a combination of the custom linux image guide here [https://confluence.atlassian.com/display/BAMBOO041/Creating+a+custom+elastic+image+-+Linux](https://confluence.atlassian.com/display/BAMBOO041/Creating+a+custom+elastic+image+-+Linux,) and this blog post [http://wkmacura.tumblr.com/post/5511638182/ubuntu-bamboo-ec2-ami](http://wkmacura.tumblr.com/post/5511638182/ubuntu-bamboo-ec2-ami,), but I'm getting stuck with the Bamboo agent not starting up, and no messages in the system log.

Does the Bamboo agent produce any log files, and is there a way to run it manually to test if it's configured correctly?


Answers:
author: Przemek Bruski
body: ```
You can try run the agent manually to see if it works:
su -c /opt/bamboo-elastic-agent/bin/bamboo-elastic-agent - bamboo

Does it work?
```

comments: author: Tobias Cohen
body: Yes, running that worked OK. It looks like the problem was that my /etc/init.d/bamboo was referring just to "bamboo-elastic-agent" when starting the agent. Changing it to use the full path of "/opt/bamboo-elastic-agent/bin/bamboo-elastic-agent" seems to have fixed it.


author: Steve Buzonas
body: The stock images add a script to /etc/profile.d/bamboo.sh that adds /opt/bamboo-elastic-agent/bin to the path.


Tags: cloud
How to get e-mail notification on failed builds
Asked by AmitB:

We are using svn and would like to set up notifications such that whenever a build breaks, the user that commited the change that broke the build will get an e-mail. I set up **First Failed Job For Plan** for a specific bamboo user successfully, but I would to send the e-mail to the commiter (svn user), not a bamboo user. How do I link e-mail addresses to svn commiters? When I set up the notification to **Committers (users who have committed to the build)** instead of a specific bamboo user, it does not work.


Answers:
author: Adam Myatt
body: Try associating their repo username with their Bamboo user. A user can edit their profile (click the dropdown arrow next to your name in the upper right while logged in to Bamboo), select Profile, Edit Profile, and try setting the Source Repository Alias. This should let the committer user be associated with a Bamboo user and thus their email.

comments: author: AmitB
body: We have more svn users than bamboo users. Is there a way to link an e-mail address to a svn user with being a bamboo user?


author: Adam Myatt
body: If you meant 'without' being a Bamboo user, then I'm not aware of how to do that. I believe you need to have a user set up, wther or not someone actually uses it, to tie a source repo alias (SVN user) to an account with an email address. You can link multiple aliases (SVN usernames) to a single Bamboo user account in case that scenario helps you at all.

comments: author: AmitB
body: I mean we have 5 bamboo users and about 20 svn users. How do I link multiple svn users to a single bamboo user? Can I then set up a separate e-mail for each svn user, or is it tied to the original single bamboo user?


author: Adam Myatt
body: In the Edit Profile section for a Bamboo user, they can associate multiple SVN aliases using the Source Repo Alias field. You can only have 1 email for each Bamboo user.


author: AmitB
body: We have bamboo linked to Jira, on which we do have users for each developer. Is there a way to open a new Jira issue to a Jira user linked to the commiter once a build is broken?


author: James Dumay
body: You can use the [Create issue](https://confluence.atlassian.com/display/BAMBOO/Creating+JIRA+issues+from+a+build) action to create a JIRA issue but you would have to set the assignee manually from within JIRA.


author: AmitB
body: How can I create an issue automatically based on a build result as part of the build script? I can only see how to do it manually after the build is done.


author: James Dumay
body: You can create a JIRA issue in a Script task by using [JIRAs REST API](http://docs.atlassian.com/jira/REST/latest/).


Tags: notification