youngmon/atlassian-qna huggingface dataset:
Why does bamboo not recognize image identity when limiting elastic instances?
Asked by Andy Longshaw:

We have just been building some EC2 server images for Windows/VS2012 CI servers triggered through bamboo (see <http://davidstringeratwork.wordpress.com/2012/10/04/using-atlassian-bamboo-ondemand-for-visual-studio-2012-projects-part-1/>). We built an AMI image of the CI server and configured bamboo to launch that when we committed to GITHub.

We encountered a problem when we added some other, non-transient instances to help with specialist testing. At that point, our automated CI builds would no longer trigger. We were helped out by the support folks to identify that the problem related to the "number of elastic instances on your AWS account that are **not** controlled by Bamboo does not exceed" setting in the bamboo configuration. Once we had some more running instances we had exceeded this value so bamboo would not launch any more instances, even though the instances were for different purposes.

The question is this: should this bamboo configuration setting not just relate to instances started from AMI images are launched by bamboo rather than all instances regardles of the AMI from which they originate? Is there something we are missing here in terms of a problem the current behaviour is solving that we haven't encountered yet?

Thanks

Andy


Answers:
author: Przemek Bruski
body: > The question is this: should this bamboo configuration setting not just relate to instances started from AMI images are launched by bamboo rather than all instances regardles of the AMI from which they originate?

It's a failsafe measure. Some cases to consider:

* you upgrade your Bamboo and get new stock images, your old instances are still running
* you remove some AMI configurations from Bamboo
* you kill your other Bamboo instance and have no warning that some old instances are still running

comments: author: Andy Longshaw
body: Could I propose this as a feature? If so, how do I best do this? Do I need to leave this as an open question for it to be considered?


author: Andy Longshaw
body: Interesting. For our own current purposes (running CI servers) I would never think of running a stock image but I can see that for people who do use stock images rather than custom that this could be an issue. Even so, I think that all of these cases woudl be improved if there was a way of telling bamboo (or bamboo working it out) which image types it can (or has been able to) launch and only including these in the count.


author: Przemek Bruski
body: You can open an improvement at our public issue tracker: [jira.atlassian.com](http://jira.atlassian.com)


author: Andy Longshaw
body: OK. Thanks. Will do this and close the question.


Tags: cloud
Disabled manual tasks in Bamboo
Asked by John Bowker:

Is it expected behaviour for a disabled manual task to affect following stages in a plan? A manual job was added to a plan but was disabled as we didn't need to use it yet but this caused the release portion of the plan to not execute and bamboo reported the build as successful.

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

Is this a bug?


Answers:
author: James Dumay
body: Just to confirm, both "Cleanup" and "Commit to Release" are disabled?

comments: author: John Bowker
body: No, both of those tasks are enabled. The disabled manual task is between "Sanity Check" and "Cleanup".


author: James Dumay
body: It should execute them just fine :( Could you contact support and provide your bamboo server log for debugging?


author: John Bowker
body: I'll contact support.


Tags: bug

task
Bamboo not building off a tag
Asked by CI Engineer:

Hi,

I am trying to do a build off a GIT tag in bamboo. When I try to enter the tag in the Source repository config and run the build, it says repository exception. Any idea why it fails. Is it not possible to build off a tag in Git?


Answers:
author: CI Engineer
body: Strangely it worked after a couple of tries....


Tags: git
Artifact Sharing with multiple build agents
Asked by Darby Coquet:

Having an issue with artifact sharing. The issue is that the first stage of my plan builds the artifact (zip file) on build server 1. The second stage of the plan is executed manually and when executed the stage is to use the zip file from the previous stage. The issue I'm having is that the second stage executes on a different build agent so the artifact is can't be found.

Assistance with understanding how to have the second stage continue on the same build agent as the first stage would be greatly appreciated.

Thank you.


Answers:
author: Przemek Bruski
body: Options:

* define your artifacts as Bamboo artifacts - Bamboo will make sure that they are available wherever the build takes place
* manually share your artifacts (e.g. through a shared network directory) - you need to make sure that all agents have access to that directory
* manually share your artifacts on a local drive - you need to make sure that all stages execute on the same machine through capabilities


author: William McCroskey
body: Funny that this has never been answered. Any suggestions? I have the same issue 6 years later.

comments: author: Alexey Chystoprudov
body: Can you please explain why Przemek's answer doesn't fit your needs?


author: Andrew Morin
body: I also work with Darby. We have a cluster of 7 build servers supporting this and multiple other applications. We already use capabilities to point the applications to this cluster and not our other three servers. We don't want to restrict this to a single server so this won't work for us unless I am missing something...?


author: Adam Myatt
body: If you want multiple Stages to execute on the same agent, just use capabilities. Define a capability on the agent like "agent.number = 1" and then just add that capability to each Job in each Stage you want to run on the same agent.


author: PiotrA
body: Hm... that's weird. From your comments I think you're using artifact sharing properly and the build agent used for the second stage should have been receiving your .zip file correctly. Have you considered contacting with Atlassian support - <http://support.atlassian.com> ? Maybe you're encountering some specific bug in Bamboo?


author: Darby Coquet
body: I'm using the artifact sharing feature within Bamboo. In the first stage I've selected the ZIP as the zrtifact to be shared and created the artifact dependency in the second stage.

Thank you


author: PiotrA
body: Hello Darby,

Can I ask you how do you have your artifact sharing configured? Are you using 'artifacts sharing' feature in Bamboo, or do you rely on some external artifact sharing mechanism? I'm not sure after looking at the description you provided...
Build .NET 4.5 projects with Bamboo
Asked by Oleksandr Kobylianskyi:

Can I build .NET 4.5 projects with Bamboo?

Write now it seems it is build using .NET 4.0. In some cases it's fine but when type definitions don't match in .NET 4.0 and .NET 4.5 compilation errors occur.

Is there any proper way to build .NET 4.5 projects and if no how soon it can appeat in future?


Answers:
author: James Dumay
body: Hi mate,

Bamboo OnDemand is due for an upgrade to the Windows 8 SDK, which includes .NET 4.5. You can watch for the completion of this [improvement here](https://jira.atlassian.com/browse/BAM-12103). Please be sure to vote too!

Thanks

James

comments: author: Vlad Salagean
body: Hi @James Dumay \[Atlassian\],

do you have any update on BAM-12103?

<https://jira.atlassian.com/browse/BAM-12103>

The issue is open since pretty long. Please provide an update on that or close with won't fix.

Thank you,

Vlad


author: Vlad Grigore
body: Same issue once more here but with higher priority: <https://jira.atlassian.com/browse/BAM-15840>Please vote to get some attention.


author: Adam Myatt
body: Additionally if you're building on anything earlier than Windows 8, such as Windows 7/Server/etc. if you install the .NET Framework 4.5 the msbuild 4.5 no longer is packaged in the .framework. According to some Googling I did you will supposedly have to install Visual Studio 2012 to get msbuild 4.5. I installed Vis Studio 2012 Express but it does not seem to include msbuild 4.5, so you need the full version of VS 2012.


Tags: .net

cloud
Repository layout for branch detection
Asked by Scott Bai:

We have a Subversion repository with dozens of related projects, each with its own Maven pom.xml file. Currently the layout is:

/project-a/trunk

/project-a/branches

/project-a/tags

/project-b/trunk

/project-b/branches

/project-b/tags

etc. This is pretty standard and works fine with automatic branch detection in Bamboo 4.2. I can set the repository location to /project-a/trunk and it will look for branches in /project-a/branches. However, I've been considering an alternate repository layout that looks like this:

/trunk/project-a

/trunk/project-b

/branches/\<branch-name\>/project-a

/branches/\<branch-name\>/project-b

etc. This would allow us to create a branch that encompasses multiple related projects, all of which will be modified together in that branch, instead of creating separate but inter-dependent branches under each project's own trunk/branches/tags structure.

However, this structure doesn't work well with Bamboo. I can configure it to look for branches of project-a under /branches, but then it thinks /branches/\<branch-name\> is a branch of project-a. In reality, the branched version of project-a is one level deeper at /branches/\<branch-name\>/project-a.

Is there anything I can do to make automatic branch detection work on this repository setup?

(Of course, I can still add each plan branch manually.)


Answers:
author: ArmenA
body: I see what you mean. Your description is a feature request for a flexible SVN directory organization. I have raised a new [feature request](https://jira.atlassian.com/browse/BAM-12257) that will be implemented as per [Atlassian policy](https://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy). Please let me know if you have any further questions or concerns.

Cheers,  
Armen


author: ArmenA
body: Hi there,

Old Bamboo versions assume that you have the structure that you described initially. As you see in the attachment, Bamboo version 4.2.1 allows to specify the directory where the branches will be looked for. Please let me know if that answers your question or if you have any further concerns.![](../../upfiles/Screen_Shot_2012-10-08_at_10.12.31_AM.png)

Cheers,  
Armen

comments: author: Scott Bai
body: Yes, I know it lets me specify the location, but as I said, I have an extra directory level between "branches" and the individual projects that Bamboo is looking for. This is because there are multiple projects within each branch. So if I tell Bamboo to manage branches for "project-a" by looking under "branches", it looks for any folder named

/branches/\*

but it needs to be looking for folders named

/branches/\*/project-a


Tags: branch

repository
Git and project subdirectories
Asked by Dave Sanders:

I'm testing out Bamboo, putting together a rails project similar to this blog article: <http://blogs.atlassian.com/2012/06/building-ruby-projects-with-bundler-and-the-bamboo-ruby-plugin/>

The issue I think is that our git project does not have the rails project at the root. Our git repo is laid out so that the rails app is in a subfolder, because we have other non-rails files at the root also. I think this is causing issues like, bundler not finding the gemfile, etc. (which makes sense because you couldn't run these commands from a folder above the rails folder in command line.

How can I do this without changing my repo? I was thinking that maybe I could issue a cd command as a task, but no dice I'm afraid. And I don't see how I can set a working folder for bundle or rake?


Answers:
author: Mark Wolfe
body: As the author of the Ruby Plugin for bamboo I had never considered this problem, that said I can most certainly assist in resolving it.

As each of the "tasks" spawns independent processes I will just need to configure this for all tasks within the build.

I have added an issue on my project to solve it <https://github.com/wolfeidau/rake-bamboo-plugin/issues/29>

Thanks for taking the time to post this question!

Update:

This morning I shipped an updated version with this feature added.

<https://marketplace.atlassian.com/plugins/au.id.wolfe.bamboo.rake-bamboo-plugin/version/48>

Screen shots illustrate the case where a project in bitbucket has a rails project directory nested within it which needs to be tested (see example project below).

<https://bitbucket.org/wolfeidau/zooper/src>

If you have any issues I am happy to help.


author: Dave Sanders
body: Shoot! I thought I picked the right one. No its about the downloaded version. My bad.


author: James Dumay
body: Dave, is this really an OnDemand question?


Tags: cloud

rails
HipchatNotificationTransport exception when sending hipchat notifications
Asked by Rick Kilcoyne:

We're seeing the following exception in our bamboo server logs when bamboo attempts to send a notification to hipchat:

2012-10-05 12:51:17,268 ERROR qtp1977220433-6806274 HipchatNotificationTransport Error using Hipchat API: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

at com.atlassian.bamboo.hipchat.HipchatNotificationTransport.sendNotification(HipchatNotificationTransport.java:75)

2012-10-05 12:55:08,067 ERROR AtlassianEvent::0-BAM::EVENTS:pool-2-thread-5 HipchatNotificationTransport Error using Hipchat API: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

<br />


Answers:
author: John Garcia
body: This means that the SSL is not convinced that Bamboo is using the host it says it's using. If you're using a self-signed cert, make sure that it has your FQDN, or if you're using a commercial cert, make sure Tomcat is aware of its network location.


Tags: hipchat

integration
How release an aplication version on JIRA without use Bamboo?
Asked by Emerson Oliveira:

We're just starting the project, and for while (at least), we don't want to depend on Bamboo to release versions.

How can we do that? If is necessary disable some plugin or whatever that only the support team can do, I ask to be done.

Thanks in advanced!


Answers:
author: Arthur Gon?alves
body: Hello Emerson,

You can follow the steps described [here](https://confluence.atlassian.com/display/JIRA/Managing+Versions#ManagingVersions-Releasingaversion) to Release Versions within JIRA, but without using Bamboo for that.

I hope this information helps! :)

Cheers,

Arthur Gon?alves

comments: author: Emerson Oliveira
body: Hello Arthur,  

Thanks for your answer (and sorry for my delay). I'll try do it, and post here the result.  

Cheers,  

Emerson Oliveira


author: Emerson Oliveira
body: Hello (again) Arthur,  

It was exactly what I was looking for, and work perfectly. Thanks a lot!  

Cheers,  

Emerson Oliveira.


author: Emerson Oliveira
body: Hello Arthur,  

Thanks for your answer (and sorry for my delay). I'll try do it, and post here the result.  

Cheers,  

Emerson Oliveira
How do you get overwritten parameters for a Bamboo build via REST?
Asked by Brent Villalobos:

I can see that there is a section labeled "Overwritten parameters" on a Bamboo build summary page when someone ran it with the "Run Customized" option. Can I get the overwritten parameters using Bamboo's REST API when querying build results?


Answers:
author: PiotrA
body: Hello Brent,

I think you can't get overwritten parameters using REST API yet. Though I'd say it shouldn't be hard to add such functionality into Bamboo. Brent, in case no other answer appear here, can I ask you to raise an issue on [jira.attlassian.com](http://jira.attlassian.com) (and ping me up, for example by leaving a comment here)?

regards,

comments: author: PiotrA
body: note to self:

\* <http://bitbucket.org/atlassian/bamboo/annotate/default/components/bamboo-core/src/main/java/com/atlassian/bamboo/resultsummary/BaseResultSummary.java#cl-471>

\* <https://bitbucket.org/atlassian/bamboo/annotate/default/components/bamboo-core/src/main/java/com/atlassian/bamboo/resultsummary/AbstractResultsSummary.java#cl-578>


author: Brent Villalobos
body: I know this is highly unorthodox and potentially dangerous, but is there a table I can look at in the Bamboo database that shows the overwritten variables for a build? I looked at the usual suspects like BUILDRESULTSSUMMARY and couldn't find anything. But maybe that information is there, but just burried or not in an obvious column.


author: PiotrA
body: It's stored in a separate table, the VARIABLE_SUBSTITUTION table. But pls, if somebody from Atlassian asks I hadn't told you that, OK?
Bamboo and maven release plugin
Asked by CI Engineer:

Hi,

I was wondering if there is a way in which Bamboo can be made interactive. I am working on automating the maven release:prepare and perform in bamboo plans. The issue is that the plan fails as I have to resolve snapshot dependencies before the release:prepare. Hence was wondering if we can make bamboo take input when it runs.


Answers:
author: Felipe Cuozzo
body: Hi Maverick,

What you can try is creating a profile in the pom.xml that enables the Enforcer plugin to prevent Snapshot dependencies, see <http://maven.apache.org/plugins/maven-enforcer-plugin/rules/noSnapshots.html>

Then you can have two different Stages on the Bamboo Plan.

1. Builds and tests (i.e. mvn verify) with the noSnapshots profile so it will fail if something is wrong.

2. [Manual Stage](https://confluence.atlassian.com/display/BAMBOO/Triggering+a+plan+build+manually) so it will only allow you to run the release:prepare if the previous stage was successful.

Does this accomplish what you're trying to do? If not, can you please explain better what would be the input you expect Bamboo to ask for?

Cheers,  
Felipe  
OnDemand Dev

comments: author: CI Engineer
body: Thanks Felipe. But the solution provided doesnt look good to me. The thing achieved by the enforcer plugin doesnt seem to be very useful as the maven release plugin by default fails if there are SNAPSHOT dependencies. So adding a profile to check the same seems redundant to me.

I will only perform a release after sorting the SNAPSHOT issue but wanted to chek if there is any feature in Bamboo where the command line interactive mode can be emulated using bamboo. So for instance when I say mvn:release it should pop up a window asking me for resolving the dependencies and then ask for the release version, tag name etc. Just wondering if that is possible in Bamboo.


author: Felipe Cuozzo
body: Usually here at Atlassian we use the default suggested tag name and version bump strategy used by Maven and specify the --batch-mode so Maven will use the default values on the mvn release:prepare step, moreover we have a policy of not commiting SNAPSHOT dependencies to the STABLE/RELEASE branch so it prevents you from hitting the crossroad of having to sort out SNAPSHOT deps just before a release, again this is just one of the ways of approaching this issue.

But answering your question, no, Bamboo doesn't have a interactive mode/popup-like way in Bamboo to ask for user input during the execution of the build process.


Tags: maven
Local Bamboo isntallation and OnDemand Jira setup
Asked by Stefan Johansson:

Hello,

if I host a local Bamboo installation, is it still possible to connect this with an OnDemand Jira setup or do they both have to be OnDemand?

Thank you.


Answers:
author: Abdoulaye Kindy Diallo
body: Based on the [Restricted Functions in Atlassian OnDemand](https://confluence.atlassian.com/display/AOD/Restricted+Functions+in+Atlassian+OnDemand), "Connecting local Bamboo installations" with JIRA OnDemand is a "NO". Kindly have a look.

comments: author: Stefan Johansson
body: Many thanks for the quick reply.
How to export plans as xml
Asked by Abhi Vaishnav [X]:

Hi,

Is there a way to export an individual plan as an xml file?


Answers:
author: AlysonA
body: Hi Abhi,

Can you please elaborate further on what you mean for "plan"?

If you're referring to Confluence, you can export spaces to an XML file or even the entire site. Same thing for JIRA, you can configure backups to be generated as XML files.

Please let us know if that's the information you were looking for.

Cheers.
Running Bamboo behind an IIS proxy
Asked by Jeff Gardner:

I want to run Bamboo behind an IIS proxy on Windows Server 2008. I have Jira and Stash both running behind this instance of IIS, but Bamboo's structure seems to be completely different so I am struggling to get it set up. I found something online that said to add these entries to the wrapper.conf file:

* wrapper.java.additional.5=-Dhttp.proxySet=true
* wrapper.java.additional.6=-Dhttp.proxyHost=\<the proxy host\>
* wrapper.java.additional.7=-Dhttp.proxyPort=\<the proxy port\>

I set the proxyHost entry to the URL that IIS is forwarding from, and the proxyPort to 80. When I access the URL that I set up, I get a 403 Forbidden error. Some examples have additional entries for proxyUser and proxyPassword, but I don't know what user/password this is referring to or how to set them up. Am I on the right track? How do I get this to work?


Answers:
author: danielwester
body: In Bamboo the port is at: *webapp/WEB-INF/classes/jetty.xml*. Default is 8085


author: Harry Chan
body: Hi, what settings did you put for JIRA and Stash? It should be exactly the same in Bamboo, except as you have already described, those additional JVM arguments, go 1 on each line in the wrapper.conf file.

comments: author: Jeff Gardner
body: For Jira and Stash, I added "proxyName=\<forwarded URL\>" and "proxyPort=80" to the Connector element in the server.xml file, similar to what I added here in the wrapper.conf file.

Do you know what would cause a 403 Forbidden error?


author: Harry Chan
body: As in you added this in Tomcat and not as a JVM argument. Bamboo uses Jetty - take a look at Jetty's documentation on how to do this compared to Tomcat.


author: Jeff Gardner
body: I am looking at the Jetty documentation, and I see sections for "Apache mod_proxy (Reverse Proxy)" and "Apache mod_proxy_ajp and mod_jk for AJP". This seems to be the equivalent of what I want to do, but using Apache. I have to use IIS because of our existing architecture. I have IIS set up to forward requests to the Bamboo URL, but I can't figure out what I need to change on the Jetty side to accept requests from the proxy URL without getting a 403 Forbidden error.


author: Harry Chan
body: I would use the Apache mod_proxy section. Give that a try but put in the IIS information.