youngmon/atlassian-qna huggingface dataset:
Elastic Bamboo static URL
Asked by Sebastien Marion:

Hi,

We have a build/deployment process running on Bamboo OnDemand, which uses elastic EC2 instances to perform its tasks. We were thinking of adding a product which requires a web server (SonarQube) to the build, but is there a way to have a static URL associated with the latest instance?

In other words, can we configure access to the machine from [](http://sq.example.com)<http://sq.example.com>in some ways?

Cheers,

Seb


Answers:
author: Sebastien Marion
body: Hi Alexey,

I can't see how this helps me as I want developers to access the webserver on the box that runs the builds.

I actually found a solution, by using a DynDNS.

Cheers,

<br />

Seb


author: Alexey_Rjeutski__Polontech_
body: Have you looked into [](https://confluence.atlassian.com/display/BAMBOO/Using+the+SCP+task+in+Bamboo)<https://confluence.atlassian.com/display/BAMBOO/Using+the+SCP+task+in+Bamboo>

and [](https://confluence.atlassian.com/display/BAMBOO/Using+the+SSH+task+in+Bamboo)<https://confluence.atlassian.com/display/BAMBOO/Using+the+SSH+task+in+Bamboo>? It seems you can configure access and all needed operations here


Tags: cloud
Bamboo Windows service crashes shortly after startup
Asked by Cathy King:

After stopping and starting our Bamboo service in Windows, the service appears to crash shortly after Windows reports that the service is running. Bamboo is using the default hsqldb database. It it likely the files there are corrupt and should be restored from a backup?


Answers:
author: ssetayeshfar
body: Hi Cathy,

Do you see an error message? If so what is the error?

If you stop the service completely and try running Bamboo by right clicking on "bambooConsole.bat" file under installation directory and selecting"Run as Administrator", are you able to correctly run Bamboo?

Thanks!

Cheers,

Sepideh


Tags: bamboo-administration
Keychain access when starting Bamboo at boot (OSX)
Asked by J.R. Hass:

I've run into a very bizarre issue:

We recently changed one of our OSX agents to start bamboo at boot, following the instructions here:

[](https://confluence.atlassian.com/display/BAMKB/Configuring+Bamboo+to+start+automatically+on+startup+on+Mac+OSX)<https://confluence.atlassian.com/display/BAMKB/Configuring+Bamboo+to+start+automatically+on+startup+on+Mac+OSX>

This seems to work just fine and launches the agent online when the system boots.

The problem is, when I try and do a build from the command line, Xcode cannot find my certificates that are in my keychain. I absolutely know they are there because I can build find from the GUI and even through SSH. I even run security unlock on the keychain (which reports success) and yet Xcode still can't find the certs/keys.

If we \*don't\* launch Bamboo at boot, and instead ssh in and launch bamboo as the build-user, i.e. ./build-agent.sh start, this problem goes away and everything builds just fine.

In other words, there seems to be a difference between starting bamboo at boot and starting bamboo through ssh manually. Has anyone run into this? Is this a known issue? I've tried to look around, and apologies if I've missed something and just need to RTFM.

EDIT: by "starting bamboo" and "launching bamboo" I mean starting the agent -- Bamboo itself is running just fine :)


Answers:
author: Philip Provoost
body: What I found out is when setting up the bamboo server not using the LaunchDaemon but the LaunchAgent it is using the correct user. Downside is that you need to login to be able to start the service, but that can be automated as well. Then the keychain can stay the same.


author: Colin Cornaby
body: Bamboo is likely not running as your user now, it's running as a system user. Keychains are typically user specific, not machine specific, so you'll run into all sorts of problems.

There are a few ways to deal with this, but the easiest is just to copy your certificates and signing profiles from your keychain to the system keychain in Keychain Access.


author: J.R. Hass
body: Hi Philip!

Unfortunately I have not found a solution. Since the machines are not rebooted that often, I've just continued to use ssh as the mechanism to bring the agent back online (when we do reboot).


author: Philip Provoost
body: Hi,

I run in exactly the same issue, did you find a solution for this?

Cheers,

Philip


Tags: bamboo-administration
Capability to define custom Build Working Directories in bamboo
Asked by Supun De Silva:

Currently in bamboo each stage runs in a seperate working directory.

for example if we set

buildWorkingDirectory = /home/supund/abc

inside the buildWorkingDirectory, it creates seperate directory for each stage as follows

\<buildWorkingDirectory\>/"\<PROJECT_KEY\>_\<PLAN_KEY\>_\<STAGE_KEY\>"

This is a bit tricky if we want two stages to run in the same directory.

We are having a pre-built system that builds and deploys all the components that we need, in single commands.

The issue being that this is already included in to git so when the code gets checked out, the script lies in the source directory. After building the components we use the same tool to deploy the test binaries to a test environment where we run seperate test suits.

The issue is that since the script is in the Checkout stage directory, we cannot have a seperate stage to spawn the test deploy since test deploy stage has a different build-working-dir.

If we can override the limitation of having seperate build-working-dir for each stage it becomes much easier. This is one of our concerns of 'build-working-dir' not being able to configure.

Is there a workaround for this ??


Answers:
author: Gretchen
body: Yes, copy the contents of the other folder into your cwd using a script command. You're not going to check it in so it won't matter in the long run and you'll have your stuff where you need it.

For example cp ${bamboo.build.working.directory}..\\(name of other directory)\\\*.\* ${bamboo.build.working.directory} usually gets the trick done for me.

We have several builds with repositories checked out from other places (runtime libraries etc.) Since the build working dir is a SVN workspace (in our case) you can't check out two repos to a single workspace (svn limitation) we have to do it this way.

It does cause a clean build but that's small price.
Bamboo For .Net Windows Application
Asked by Teddy Suyanto:

From what I see in Bamboo, I have a feeling that Bamboo is best suited for Web Application.

I see that we can build, test, deploy in Bamboo.

How about Windows application (e.g. .Net), does Bamboo still offer same capabilities like in Web Application?


Answers:
author: Gretchen
body: Depends on what it is specifically you're interested in. You weren't very specific in your question so I can only offer a general answer.

It can easily do command line builds using msbuild and devenv (or whatever the other msbuild command is). You can use nunit for reporting nunit testing results.

comments: author: Jason Monsorno
body: Adding  
* MSTest for testing as well.

* NCover for coverage reports.


author: Teddy Suyanto
body: Ok, so let me summarize, what we can do in bamboo for win forms:

* MSBuild -\> to build
* MSTest -\> for unit testing
* NCover -\> coverage report

1. How about msi package? is it possible using bamboo?

2. For bamboo I was thinking about using it (for .net win forms) to build, run unit test, deploy (create .msi). If you could give me more example or suggestion on what else I can do with bamboo, would be great.

Thanks

comments: author: Jason Monsorno
body: The simple answer is yes.

There are a few built-in (technically 'Atlassian Bamboo .NET Plugin') tasks like the MSBuild, MSTest Runner but you can run any command line, batch script, or PowerShell from Bamboo.

The only special things Bamboo does that you can't customize are display. The Test Runners and Parsers will display the tests in a special view, I believe NCover works the same but haven't used it in Bamboo yet.


author: Jason Monsorno
body: What capabilities does it offer you for your web application?

Over here we're building and deploying Web Forms, MVC, ASMX Services, Console Applications with Scheduled Tasks, and Windows Services -- all .net 4.0
PhpUnit tests doesn't recognized by Bamboo as tests
Asked by Roman Arkharov:

Hello.

My name is Roman. I'm trying to set up build in Bamboo and I've added PHPUnit task in my plan. When I run this plan I see following messages in log:
> 08-Aug-2014 18:54:33PHPUnit 4.2.0 by Sebastian Bergmann.
>
> 08-Aug-2014 18:54:33
>
> 08-Aug-2014 18:54:33Configuration read from /var/atlassian/application-data/bamboo/xml-data/build-dir/BAB-TP-JOB1/phpunit.xml
>
> 08-Aug-2014 18:54:33
>
> 08-Aug-2014 18:54:39...........................
>
> 08-Aug-2014 18:54:40
>
> 08-Aug-2014 18:54:40Time: 7.08 seconds, Memory: 47.75Mb
>
> 08-Aug-2014 18:54:40
>
> 08-Aug-2014 18:54:40OK (27 tests, 159 assertions)
>
> 08-Aug-2014 18:54:40
>
> 08-Aug-2014 18:55:42Generating code coverage report in HTML format ... done

But, on "Tests" tab (on current build page) I see message "Test results. 0 test in total".

Is it possible to show on this tab actual counter of PHPUnit tests which were successfully run?


Answers:
author: Przemek Bruski
body: Maybe you need to add a test parser task.

comments: author: Roman Arkharov
body: Thank you, you are right!


Tags: bamboo-administration

phpunit
There is no link to configure build expiry settings
Asked by Lee Myring:

I am getting multiple jars being copied because they exist in my bamboo on demand. I want to set expiration but all the articles refer to links that are not available in my bamboo ondemand UI.

How do I expire stuff in bamboo on demand???


Answers:
author: cbenard1
body: Hi Lee,

As of Bamboo's update to 5.6 the options to manually set build expiry have been removed. My apologies that the documentation has fallen out of date. I've created an internal request to have those updated. As it stands now build expiry is automatically enforced with the following parameters:

* Build and deployment expiry period of 30 days
* Log files under 10Mb are kept regardless of expiry
* Keep last version/build regardless of expiry

Thanks!

<br />

Turner

comments: author: Lee Myring
body: That's a real problem for us as we have new build artifacts that are getting deployed as we want them to expire every week not every 30 days....can artifact deletion be put back?


author: cbenard1
body: Hi Lee,

Just so I don't leave you hanging here. Currently there is no way to add these features back to the software. I'm recording this issue and presenting it to our development team to see if we can add the functionality back for y'all that want to expire artifacts more quickly than they are expired by default. I'll update you here once that's complete.

Thanks!

Turner


author: corinne
body: Ah man. The documentation had me excited about the expiry features. It would be great if the documentation was updated. It would have saved the time I spent this morning developing my expiry plan and not being able to figure out how to implement it.


Tags: cloud
Setting branch default notification
Asked by Richard Jones:

Hello

I have bamboo set up to auto create plans when branches are created in GIT. This works really really well. My only problem is that i have go through each branch in each module and set up the notifications to be the same as the plan. Is it possible to set up any new branches to use the parent plan's notifications settings?

See attachement for what I mean

Thanks

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


Answers:
author: Ron Chan
body: You can do that under Plan Configurations -\> Branches -\> Notifications.

This makes it effective for all your new branches.

comments: author: Richard Jones
body: Thanks - that;s just what Im after


Tags: bamboo-administration

notification
default plan running twice in bamboo
Asked by Richard Jones:

Hello

I have a git repo that I have hooked up to Bamboo. I am using GitFlow so i'll use their terminology here.

I have a master branch which is default. I'd like this not to be the case but I am not sure I can change the default branch.

When I commit to master I end up with two builds running on bamboo. See attachment. If I commit on any other branch I just get the correct one build running. Do you know why?

Thanks![](../../upfiles/Bamboo.png)


Answers:
author: Marcin Gardias
body: - you can point the 'main' plan in Bamboo to whatever git branch you want.

- it seems that you have 'main' plan set to master and at the same time there's a Plan Branch set to master as well. Both do change detection and both build. Simply go to Plan configuration, scroll down to Branches, find the one called 'master' and disable it. (alternatively set your main plan to the branch you really want it to point to)

comments: author: Richard Jones
body: Thanks Marcin, I'd like to change my main plan to solve this. How can I do that? I havent seen how to change the default plan. THanks for your reply!


author: Marcin Gardias
body: Go to plan configuration, click on Repositories tab. There should be a list of repositories, select the first one (probably that's the only one you have)

Simply set the Branch text box to correct value. Press save. You might want to run a manual build afterwards to test that your edit is correct and to make sure that Bamboo's change detection will correctly pick up changes from the new branch.


Tags: bamboo-administration

git
How can i list subversion tags just like in Jenkins?
Asked by Ashish Manandhar:

How can i list subversion tags just like in Jenkins in Atlassian Bamboo? I need a list or dropdown menus when i use a variable for available tags in from svn.


Answers:
author: Gretchen
body: If you're talking about to build from you can specify it in branches (treat the tag like a branch for the purpose of building). We build our release builds locally then in a remote bamboo the customer builds from the tag we created ensuring they get exactly what we recommended. To do this do either manually create a branch or put a regex in your automatic branch management that looks for whatever it is your tags look like. The branch build will build from the selected tag.

comments: author: Ashish Manandhar
body: Actually we build from tag manually....we have old setup from jenkins that we would like to migrate to bamboo. In jenkins while doing manual build with parameters, we can actually select the tag/tagnumber from the list of available tags under same folder ( example if [](https://svn.../abc/tag1)<https://svn.../abc/tag1>; [](https://svn.../abc/tag2)<https://svn.../abc/tag2>; [](https://svn.../abc/tag3)<https://svn.../abc/tag3> are the available tags then we can do parameter build with pull down select options of tag1, tag2, tag3...)Here all the tags are under same svn repo: [](https://svn.../abc/)<https://svn.../abc/>.This way we can manual select if i want to build tag1 or tag2 or tag3 because it show all the available tags in the folder abc. Can we replicate same behavior in bamboo ? Please help.
Source Checkout Repo dropdown is empty in Bamboo Deployment
Asked by Kalen Wessel:

I'm trying to create a deployment project which does QA. When I create a task in the deployment environment and select the "Source Code Checkout" task it doesn't give me a list of repositories to select. It's just an empty dropdown box.   

I've tried creating a shared repository to see if it would appear in the list but it still doesn't. I'm using Bamboo 5.4.2. Any suggestions would be greatly appreciated.


Answers:
author: Kalen Wessel
body: Figured out the problem, they won't show CVS repos. I created a test GIT repo and it showed up just fine. This is super frusturating. I guess it's time to create a bug report.

Edit: You can find the bug report here: <https://jira.atlassian.com/browse/BAM-14888>


author: Justin Frost
body: Have you created a linked repository in configuration ? I believe deployments use these.

comments: author: Kalen Wessel
body: I don't believe Bamboo 5.4.2 has linked repositories. Or at least that's the new name they gave shared repoistories in 5.5. Maybe I should try upgrading?  

<https://confluence.atlassian.com/display/BAMBOO/Bamboo+5.5+Release+Notes>


author: Justin Frost
body: I believe shared repositories should show up. Checkout the comments in this page:

[](https://confluence.atlassian.com/display/BAMBOO/Deployment+projects)<https://confluence.atlassian.com/display/BAMBOO/Deployment+projects>

Someone has the same issue and the answer is to create a shared repo.


author: Kalen Wessel
body: Thanks for the help none the less.


author: Justin Frost
body: Ah ok. We were using SVN.


Tags: bamboo-administration
Bamboo Remote Agent limit - 100?
Asked by ARM Ltd. (old account):

Hi All

I am trying to find out any kind of information why Bamboo is limited to 100 remote agent?

If I have Powerful enough Server why not allow more?

Is it just Licensisg limitation?

Regards,

Areg


Answers:
author: Przemek Bruski
body: It's a licensing limitation. We've been thinking of introducting new license tiers in the future.

Internally at Atlassian, we have servers with about 200 agents.

comments: author: ARM Ltd. (old account)
body: Is there a possibility to have this kind of license on special request as we are hitting the 100 limit?

We have raised the Support request.


author: Sten Pittet
body: Hi,

At this stage we are not likely to give license above 100 agents on special request. Our Build Engineering is able to do this internally at Atlassian under very specific conditions and it is hard for us to ensure that those conditions can be respected by our customers.

If we were to give out a license allowing to use 100 agents it might lead to instances failing and we will have to ask customers to downgrade their number of agents before we can support them.

As Przemek mentioned it we want to invest in Performance and scaling the number of agents is something that we will look at in the future, however it is not something that we will be able to address before the end of the year.

Regards,

Sten  
Bamboo Product Manager


author: suresh nallamilli
body: Is there any update on this? Its been more than a year and i see that hard limit is still 100 agents


Tags: hardware

remote-agent
Nodejs plugin for bamboo 5.6.0
Asked by Walter Heestermans:

When can we expect nodejs plugin compatible for bamboo 5.6.0?

Regards

Walter


Answers:
author: Walter Heestermans
body: Restarted the bamboo environment and warning is goen. Closed.


author: Walter Heestermans
body: I have reinstalled the plugin version 1.5.2 inside my test bamboo 5.6.0, but still says 'INCOMPATIBLE'?

Regards

Walter


author: Marcin Oles
body: I've tested the plugin (v1.5.2) against Bamboo 5.6.0 and it is compatible. Changed compatibility details on the Atlassian Marketplace.
Triggering child builds with Bamboo automatic dependencies
Asked by David Moles:

We've configured Bamboo to use [automatic dependencies](https://confluence.atlassian.com/display/BAMBOO/Setting+up+plan+build+dependencies#Settingupplanbuilddependencies-AutomaticdependencymanagementwithMaven3) based on Maven POM files. This appears to be working, insofar as the Bamboo interface correctly shows which the Maven artifacts required by and created by each plan, which upstream plans provide the dependencies and which downstream plans depend on the artifacts.

However, it also appears to not work, insofar as building an upstream artifact doesn't trigger a downstream build. Is it necessary to manually create child plans to trigger downstream builds -- an error-prone duplication of the information in the POM files? If so, the automatic dependency management isn't much use and it's hard to understand what the feature is for.


Answers:
author: Pawel Skierczynski
body: First thing to check is if version that downstream build depends on is SNAPSHOT and if version that upstream builds is the same SNAPSHOT. It works only for SNAPSHOTS.

comments: author: David Moles
body: Everything is 1.0-SNAPSHOT AFAICT.


Tags: maven
Do I need to support renewal when upgrading Bamboo
Asked by cybage_bitbucket:

Currently we have Bamboo 5.5.1 license version installed on Linux (CentOS) Server. We need to upgrade Bamboo to latest version (5.6.0). Bamboo Support period has been expired. Do I need to renew support period before upgradation of Bamboo?

If we upgrade Bamboo to latest version without support period renewal process so Bamboo will work properly with upgraded version?

Please suggest on this.

SEN-2727793

Support period expired on - 25 Jul 2014


Answers:
author: Nic Brough -Adaptavist-
body: All the Atlassian products follow the same licence rules. The answer you got when you asked this about Jira is exactly the same for Bamboo.

comments: author: cybage_bitbucket
body: Hello Nic,

Thanks for your updates but there is some cofusion in released Bamboo.

When I am downloading Bamboo to lateset version in that it shows released on 22-Jul-2014 \& it shows 29-Jul-2014 in release notes. so could you please confirm the Bamboo 5.6.0 released date so accordingly I will take action on it.


author: Nic Brough -Adaptavist-
body: The release notes are often generated after the download is released. The important date is the release date. At least, last time I tested that was the case.
Is Bamboo suitable for deployments to multiplie client production environments.
Asked by Justin Frost:

We have setup bamboo for CI builds and releases. What we want to do is to deploy the releases to multiple customer production environments in the cloud (in addition to our internal testing environments also in the cloud.).

The deployment is made up of a web app (.war), database changes (.jar) and other artifacts (openRoad app server images etc).

Is Bamboo able to handle this, we could end up with over 100 environments setup for deployment.

Is there a recomended 3rd party tool to handle the deployment side of things ?


Answers:
author: Gretchen
body: That's a tough one without knowing a bit more. If the deployable objects (wars, jars etc.) are identical you might get a good result scripting it on each customer's site to pull from a central repository (whether that is source or something like nexus or artifactory) on demand or on a cron job for example. This might have the benefit of allowing the customer to control when their deployment occurs.

Are all 100 customers expecting the deployment of new apps to occur at the same time? If not this could be a snag. What happens if the file transfers work successfully at 97 customers, but three customers fail (due to something like network issues etc. outside your control). This would make scripting it as a single deployment push script undesirable. If one or two customers don't want a particular release until a later date (due to some unforseen ridiculousness) having a single script to deploy to all customers would also be inconvenient.

Perhaps the best option would be to set up a deployment project for each customer and schedule it, or in the case of continuous deployment just deploy on successful build (or another deployment plan success). I think you can have multiple deployments from the same build (therefore pulling the same build artifacts).

That might be a pretty good solution, assuming the transfer mechanism you require and the access is available from your bamboo server. This would be kind of a nuisance to setup but I think would work pretty well and give you good visibility into what customers had successful deployments and which ones failed. (out of 100 you have to figure one or two will fail occasionally, just due to Murphy's Law).

In any case Bamboo can help with all but the first scenario.


Tags: bamboo-administration