Steffen Opel [Utoolity] Community Champion

Unfortunately you seem to be be affected by the following bug, which you might want to watch accordingly: * SLA panel is empty when new issues are created and SLA does not stop/pause, when using MS SQL with JSD 4.0.1 (JSDSERVER-6253) The issue currently refers to the following workaround: Perform the POST-REST API call…

Are you by chance using MS SQL? If so, you might be affected by the following bug: * Customer notifications are no longer created and sent when using MS SQL with JSD 4.0.1 (JSDSERVER-6252) At the time of this writing there does not seem to be an official workaround, however, several users have reported their's in the…

Unfortunately Bamboo currently lacks sufficiently fine grained permissions to address this - please watch and vote for the following issues to raise Atlassian's awareness of this notable limitation: * Add security setting to Block users from being able to Dedicate Agents to Build Plans and Deployment Environments…

You can achieve this with the 'requirements' parameter of a job definition, which is available as Job.requirements in Bamboo Specs (Java), and job.requirements in Bamboo Specs (YAML) - here's the Java example: <span>Job</span> <span>job</span> <span>=</span> <span>new</span> <span>Job</span><span>(</span><span>"My…

You need to run the X11 display server in a headless fashion, which is commonly achieved via the X virtual framebuffer (Xvfb). Not 100% positive on this, but I think Xvfb is included on the stock Bamboo Elastic images (despite the lack of a preconfigured capability), either way none of this is properly documented. You can…

As Martyn already confirmed, Bamboo is a perfectly capable platform for such a project - more specifically, you might want to check out the following related topics: * Getting started with Node.js and Bamboo * Bamboo, Docker, and building web apps These older posts emphasize the classic UI driven build configuration in…

This sounds like you are already using Bamboo with a Bamboo Starter license, which offers unlimited local agents, but indeed only 10 jobs and 0 remote agents? You do not need to download a new evaluation copy of Bamboo (the binaries are identical), rather you can simply log into your my.atlassian.com account and request a…

I'm not 100% positive, but I think you cannot further limit the result shapes returned by default - that being said, the Bamboo REST API does use a similar mechanism conceptually, albeit only to further expand the default shapes with potentially significant additional details for the returned collections, see How to use…

I think you are accidentally reaching out to the wrong community: This community here is about Atlassian products, which indeed includes the issue and project tracking tool Jira - however, there is no version 2.121.1, the currently supported versions are starting at 7.3. A search for 2.121.1 suggests that you might…

The easiest way to achieve this would probably be the Jenkins Generic Webhook Trigger Plugin. Once you have configured an inbound webhook trigger in Jenkins, you need to invoke it somehow. As is, the various curl based examples there could all be executed via Bamboo's Script task. If you are wondering why a webhook is not…

Yes, Importing data from Jenkins is a built-in Bamboo feature, though obviously not all of the myriad of Jenkins plugins and features can be migrated to Bamboo as is, see the matrix on the referenced page for an overview. That being said, the process is well guided and produces an import log with possible configuration…

The Bamboo password log obfuscation indeed masks anything that has the value of any password variable in the executing build/deployment context, which can have confusing effects for simple 'password' values that by chance occur elsewhere in the log as well, for example: Say you have a global variable…

You should be able to achieve this via the Bamboo REST API, which supports adding/removing labels from plans/builds - relevant resources are: * Verify/Apply labels across historic results * http://myhost.com:8085/rest/api/latest/result [GET] *…

I'm not aware of any way to configure Bitbucket to ignore particular Bamboo build results. That being said, the build status API for both Bitbucket Server and Bitbucket Cloud are based on associating the build status against a particular commit, so in case your auxiliary plan Y does not actually use the resp. source code,…

The current Plan permissions enable you to allow users the ability to Add a comment or label to a build result by checking the View permission, while denying the ability to Trigger a manual plan build and Pause and resume a plan build by unchecking the Build permission. However, Bamboo currently lacks sufficiently fine…

Ah, I see - if I get this correctly now, you could use the ${bamboo.deploy.environment} deployment variable as (part of) the Git tag name. Tags are visible in the commit log view, albeit admittedly not as rich and prominent as you might have envisioned for a build status symbol. I'm not aware of the latter being readily…

Agreed - it's kinda weird that the only alternative option seems to be the service startup wrapper itself (also on Linux), but that's were we stand apparently.

You can achieve this via the BUILDING_DISABLED system property (usually by passing -Datlassian.bamboo.build.disable=true at startup): Disable triggering plans globally in Bamboo. Plan can be started manually only. Please note that this only works as expected for Bamboo >= 6.3.1, see the following issue for details: *…

As of Bamboo 6.7 it is possible to use the extended/new Repository Tag (previously known as VCS Tagging, which only worked for Subversion) to create a Git tag and push it to a remote repository. If you configure the task after the deployment task(s), it will only execute if the preceding tasks succeed. The task…

Unfortunately the option to "Don't execute upon initial branch detection" is not yet available - please watch and vote for the following issue to raise Atlassian's priority to address this limitation: * Prevent first build on new branch/plan until change detection occurs (BAM-17048)

Unfortunately Bamboo currently lacks sufficiently fine grained permissions to properly address this - please watch and vote for the following issue to raise Atlassian's priority for addressing this notable limitation: * Create JIRA Issue from failed test is only available to Plan Admins (BAM-15060) That being said, it…

You could propagate the name by means of an artifact and the Bamboo Variables task, roughly: * Dump the name to a properties file via the Bamboo Script task in your build plan, i.e. (from the top of my head) something like:* 'echo "zipname = ..." >zip.properties' for PowerShell * Configure an artifact for the…

I'm afraid Bamboo variables are not (officially) exposed to the Freemarker notification templates - please watch and vote for the following issue to raise Atlassian's awareness of this obvious feature gap: * Expose build environment variables to notification templates (BAM-15901) That being said, please note that the last…

You could propagate the ${bamboo.repository.revision.number} variable by means of a secondary artifact and the Bamboo Variables task, roughly: * Dump the variable to a properties file via the Bamboo Script task in plans A and B, i.e. (from the top of my head) something like:* 'echo "plan1hash=…

Bamboo supports manually Rerunning a failed stage as follows: If a stage has failed in your build, you can choose to rerun the stage (with exactly the same data) instead of the entire plan. To rerun a stage: * Navigate to the failed build result, as described on Viewing a build result. * Choose Run > Rerun all failed…

Bamboo supports rebuilds from a changeset by Running a customized manual build where you can Choose the revision of the default repository that should be used: Choose a repository revision to use for the build. Note that: * You can only choose revisions from the default repository. * The build is not included in plan…

I'm afraid this is not yet available - please watch and vote for the following issue to raise Atlassian's awareness of this obvious security and usability flaw: * As an Administrator I do not want Bamboo to expose the list of all projects to all users (BAM-19612)

Go to My Atlassian (you need to login with your Atlassian ID, or sign up for an Atlassian account if you do not have one already), click New Evaluation License, select Bamboo and follow the prompts.

I'm afraid this is not yet available - please watch and vote for the following issue to raise Atlassian's awareness of this obvious usability flaw: * Allow timezone to be specified for Single Daily Build or Cron triggers (BAM-13365)

Go to My Atlassian (you need to login with your Atlassian ID, or sign up for an Atlassian account if you do not have one already), click New Evaluation License, select Bamboo and follow the prompts.