Jeyanthan I Atlassian Team

Hi Sino, This is definitely possible with the help of Dependency blocking strategy. This ensures that a "tree" of dependent builds always runs in tree hierarchy order, even if child plan builds are triggered independently of their parents. All you need to do is to set Plan A and Plan B as a parent of Plan C and enable…

Hi Andrew, You can find this link having steps to define your job requirements. You would just have to create a custom capability in the appropriate agent(s) in Bamboo UI, and specify it as a requirement for this job. It looks something like this. <span>---</span><span>project</span><span>:</span>…

Hi Akhil, I believe the English translation to the error is this: <cmd> is not recognized as an internal or external command We see this problem often, and it's often related to the SYSTEM path not working when using the agent as a Windows Service which is outlined in the below knowledge base article: * Bamboo or remote…

Glad to hear that you sorted it out. Thanks for acknowledging here.

Hi @sta-szek, Is it possible for you to configure your first stage into a child plan and keep your second stage as your parent plan? This way, you can set the option Block build if parent builds are queued or in progress in Dependency blocking startegy section, so that new builds are blocked until the existing one is…

Hi Niranjan, I believe you're using XCode task to run this. When you say that you get dependency error, were you able to run this outside Bamboo (via command line) as the same user in the same machine running this build?

Hi Michael, There is no option to customise Build dashboard (yet). I see there is a feature requests for this - https://jira.atlassian.com/browse/BAM-15309

Hi, When you say that the newly created users are not able to login, do you see that user being listed under Users section in Bamboo? The way how it works is that once you activate LDAP authentication, you cannot manage LDAP accounts or user groups from Bamboo. All the authentication requests are routed to LDAP and Bamboo…

Hi Lakshmi, I was able to trigger a build using the below curl command as explained in this page. curl -X POST http://host:port/rest/api/latest/queue/PLAN-KEY?os_authType=basic --user username:password You might also use the action call (/api/rest/updateAndBuild.action?buildKey=) using the endpoint updateAndBuild.action to…

I followed the KB article and the new instance stops working after importing the backup of the old server Bamboo 5.15.x shipped with a new System-wide encryption feature. The encryption key is stored in the database and on the filesystem. Both the filesystem and the database key parts are required to perform successful…

Just to close the loop after following up on the support request you raised internally. Summarising the actual issue: When there are two plan branches created in Bitbucket, Bamboo creates 2 plan branches and queues them to build subsequently (as we dedicate to 1 agent). When the Gate keeper merge option is configured, the…

Hi Kyle, If your intention is to trigger a build upon a JIRA transition, the action call (/api/rest/updateAndBuild.action?buildKey=) using the endpoint updateAndBuild.action can be used to trigger a build. This checks whether there are changes in the repository associated with the planKey provided as parameter. Upon doing,…

Hi Shane, What is the NUnit version you are running 3.x or 2.x? (Bamboo is only able to parse NUnit reports in NUnit2 format). There's an open feature request for this to support NUnit 3.0. Please vote and comment on it. The workaround is that the NUnit tests need to be converted to NUnit 2 if they are running NUnit 3. You…

Glad you figured it out :)

Hi Suvankar, There appears to be no option to pass custom parameters to an SSH task. If your intention is to connect to multiple environments via SSH, what you can do is to use a Script task and define your custom environment using plan variables in Configure plan -> Variables(tab) and define the environment hostname like…

Hi, If your intention is to just trigger a build soon after a new commit is made on Bitbucket repository, you would have to add that Bitbucket repository as a Linked repository in your plan and then configure Triggers, so that a new build is triggered when changes are committed.

Like Jobin mentioned, If you see a grey build status icon on Bitbucket side, you might want to start with looking at the Bamboo server log in <bamboo-home>/logs/atlassian-bamboo.log and see what went wrong while transmitting.

In general, the best idea is to define a plan in Bamboo UI and then export it to Bamboo Specs source code in Actions -> Configure Plan -> View plan as Bamboo Specs as described here. Hope you have figured out the issue by now.

Just for records, Bamboo 6.5 now supports multiple repository types other than Bitbucket Server. * Git * Bitbucket Cloud * GitHub * Subversion Upon using one of these, users will need to set up proper webhooks. The webhooks must send HTTP requests to Bamboo on commits. More info on these can be found here in the release…

Is it possible for you to move the artifacts to a different location before you had to clean your working directory? This way, you avoid artifacts from being deleted.

Hi @Chris Flynn, It looks like the fortify code analyser can be accessed via command line. This means that you can just use a script task to invoke this tool and achieve what you want. Their documentation explains how to achieve this. A basic command sequence can be like this. * builds the code using sourceanalyzer -b…

Hi Suvankar, If your intention is to connect to multiple environments, it is necessary to define multiple ssh tasks to connect to multiple environments preferably in a different job/plan based on your requirement. If you want to run using the same job, you may use plan variables and define the hostname in *Configure plan…

The solution suggested by my colleague might just work fine. Just in case, if you happen to have issues on line endings or something due the operating system shift, you must consider using the export feature and do an import onto a newly installed latest Bamboo 6.x in your Linux operating system. If you happen to get an…

Hi Reetesh, I came across the following KB article that explains how to alter the banner color - Customizing the color of Bamboo banner. You may extend it to match your requirement. That said, it could be that it no longer works with latest versions. I also came across this feature request Customisable header styling . I…

Sure, J! Glad to help.

Hi J, Could it be that you are using any sensitive commands like rm -rf on your build task that deletes the build directory and the respective logs? Build logs are usually stored in the respective agent's home <Bamboo-Home>/xml-data/builds/<plan>/download-data/build-logs/ Do you see the corresponding build log listed…

Just for records, one can parse the shebang and execute that interpretor inline directly only from Bamboo 6.4 onwards (via BAM-17864).

Bamboo doesn't have a feature to notify users when an agent goes offline. You can configure a cron job to check the service status periodically and make it restart if it went down. This can be extended to send a notification based on that. I was thinking of another way by utilizing Bamboo's default feature, but not…

Hi Chad, Bamboo does not provide the REST end point to create a new linked repository (yet as of Bamboo 6.4.1). I found an open feature request for this - BAM-18453 I recommend you vote for it and comment to get it prioritised.

For your use case, is it possible for you to utilise one of the bamboo's automatic merge strategies to do the merge instead of relying on automatic merge in Bitbucket?