Steffen Opel [Utoolity] Community Champion

It would be very odd if we were using anything else. 😆 You mean like say, using Lithium rather than Questions for Confluence for Atlassian's very own community Q&A site? 😆

Thanks for the clarification @Mathias Gebbe, I've misread your question indeed. As Grzegorz already pointed out, other than Bamboo Specs (Java), Bamboo Specs (YAML) do not yet support tasks - given Maven's POM is XML based, I've updated my answer with a few pointers how you might achieve this via Xpath/XSLT.

This can be achieved with the Task: Maven Bamboo Specs syntax for Java, for example: <span>MavenTask</span> <span>mavenTask</span> <span>=</span> <span>new</span> <span>MavenTask</span><span>()</span> <span>.</span><span>goal</span><span>(</span><span>"clean install"</span><span>)</span>…

In terms of plugins, you might want to check out David Ehringer's excellent Maven POM Value Extractor, which "Extracts values from Maven POMs and keep your Bamboo variables in sync with your Maven POM", thus precisely addresses your requirements! Given the latest version is from 2016, it cannot have built-in Bamboo Specs…

This can be achieved via the advanced option Include/Exclude Files when you configure a source repository in Bamboo, see section 'Change detection options' within Bitbucket Server (formerly Stash): Allows you to specify the files that Bamboo should, or should not, use to detect changes. When you configure the Include…

Update 2018-02-26: We have fixed the below referenced example from our docs by adding the required 'Env:' prefix for accessing environment variables from PowerShell. According to the related documentation for our (Utoolity's) AWS Credentials Variables task, the following syntax for referencing Bamboo environment variables…

Hi @paulvandrunendigitaslbi - all Bamboo variables are available as environment variables in the Script task, with details depending on which shell you are using. Unfortunately this is not well documented by Atlassian indeed, please refer to e.g. Utoolity's section on Environment variables for the specific syntax…

Assuming you are using the 'bamboo.planRepository.branchName' Bamboo variable to get the branchname, you can manipulate the variable value in a Script task, write the adjusted value to a file, and then inject it again as a new variable by means of one of the following tasks: * the built-in Bamboo Variables task * David…

Yes, but only with an indirection - you can manipulate the variable values in a script, write them to a file, and then inject them again as new variables by means of one of the following tasks: * the built-in Bamboo Variables task * David Ehringer's YAML and JSON Variables Loader * llucIT Software's Variable Extractor…

You can achieve this by facilitating Bamboo variables in the build step that produces the artifact, in particular you likely want to use ${bamboo.buildTimeStamp} and/or ${bambooBuildNumber}. The specifics depend on the build step you are using to produce the artifact, but all Bamboo tasks including the Script task should…

Seems the system doesn't play well with links to on page anchors, I've now just linked the main page with a pointer to the section as a workaround.

@Jayasree Tadanki - sorry, not sure why the system is garbling the workflow link, maybe it works here: https://confluence.atlassian.com/bamboo/understanding-the-bamboo-ci-server-289277285.html#UnderstandingtheBambooCIServer-HowisaBambooworkfloworganized?

With the exception of the 10 job limitation for the $10 Bamboo 'Starter' licenses, I'm not aware of any formal limitations, so you should be able to create as many workflow entities as your hardware configuration supports (memory/storage/CPU constraints etc. - Bamboo Best Practice - System Requirements has a table with…

@Jayasree Tadanki - I highly recommend to ask a separate question for each separate topic: This provides the best chance for a qualified answer, because everyone monitors the title and tags of new (!) questions to check whether one has the specific know how to provide a valuable answer (in other words, comments to 'old'…

Cloning plans is completely fine, and so is manually cleaning up (part of) the build folder in exceptional circumstances like you are doing there for 'lib', insofar most of the files are temporary build results anyway - I just wanted to make sure you are aware that the main build artifacts and logs are also stored there…

Probably not, though this depends on your retention needs for the build and deployment artifacts etc. - please see section /xml-data/builds/ within Bamboo server home directory (also applies to Bamboo agent home directory) for details: This is known as the Build Directory. This is where Bamboo stores build results (note…

After the recent introduction of Crowd Data Center and HipChat Data Center, Bamboo remains the only main Atlassian Server product that doesn't yet offer a high availability (HA) deployment option, unfortunately. Admittedly its highly flexible remote and esp. elastic agent concepts do cover some ground in this regard, but…

Based on Modifying notification templates, I think you'll need to explore the Java interfaces that are backing the Freemarker ${buildSummary} and ${deploymentResult} variables, i.e. the Java BuildResultsSummary and DeploymentResult interfaces respectively. The former provides an Iterable getResultVariables() in turn, which…

Unfortunately the example 'helloworld' task implementation formerly included within 'atlas-create-bamboo-plugin' got removed from the SDK at some point, even though this "most relevant and most frequently implemented extension point" is still not available via 'atlas-create-bamboo-plugin-module' as of today - please watch…

Other than for GitHub, AWS CodePipeline does not yet provide an official integration with Bitbucket Server, though there's a potential workaround by means of an AWS Quick Start. AWS Quick Start If you are willing to invest a tiny bit of work into your own (serverless) solution, you can deploy the AWS Quick Start Git…

This is indeed not easy to discover (and also not mentioned in the plan permissions docs) and might thus be considered a slight usability flaw: You simply need to remove all individual plan permissions from that user by toggling each active checkbox individually - once all checkboxes are cleared, the user does not have any…

Glad to hear @Xavier Naud - please also 'accept' my answer as solution via the checkmark on the left side so that it doesn't show up as unanswered anymore, thereby keeping others and myself focused on and motivated to assist with new questions :) - thanks!

Possibly this has just been caused by an intermittent operational error with Bitbucket Pipelines, see the following incident: * OutOfMemory errors using Bitbucket Pipelines docker service Accordingly, things might just work if you try again now?

I'm afraid this is not possible right now. There's a related issue you might want to watch and vote for though: * Option to revert to the old style of Help Center (JSDSERVER-3527) While I doubt that it will ever be addressed as phrased in its title, Jean-Pierre's comment proposes the 'ability to either remove "popular" and…

Good question, the bootstrapping of secrets is a complex problem for configuration in code in general. I'm not aware of a dedicated recommendation from the Bamboo team and would appreciate if they'd chime in as well, but here are two approaches that I'd consider at this point: 1. In line with the Twelve-Factor App's Config…

I'm not aware of any other code examples outside of those within Customize the issue collector, sorry @Brianna Barnes - that being said, I'd highly recommend to ask a frontend developer from your team for half a day of her/his time, anyone moderately familiar with JavaScript should be able to quickly understand and…

The answer is 2, i.e. it is indeed possible to override global Bamboo variables with plan variables for builds and deployments: Plan variables are similar to global variables, but are defined for specific plans. Plan variables override global variables with the same name. You can also override a plan variable for a build…

Unfortunately there is no official way to do achieve this, and it's a fairly highly voted improvement accordingly (one might actually consider it to be a bug, given it erroneously reports build errors) - please watch and vote for the following issue to further raise Atlassian's awareness of this major annoyance: * Prevent…

Guess that's obvious, but I'd strongly recommend to identify why the build is not failing in your scenario, usually the build tool in question just requires an additional flag to return an error code to Bamboo (for example, you can return a non zero exit code from script tasks to let the build fail). That being said, there…

@Abhineet Tikoo - You can find a quick start and 'Everything you need to know about Bitbucket Pipelines in action' within the Build, test, and deploy with Pipelines documentation, including build and test guides for various languages, and deployment guides for various cloud providers and Docker images.