Steffen Opel [Utoolity] Community Champion

Except for the variable syntax, there is nothing fundamentally Linux specific in that solution I think: * the non existing 'touch' command is just for illustration anyway, you want to work with your own modified files of course * you obviously need to install Git for Windows * a bit tricky is Bamboo's variable syntax for…

As of the recently released Bamboo 6.7, you can use the new Repository Commit and Repository Push tasks that accompany the existing Source Control tasks (Checkout, Branch, Tag). For earlier Bamboo versions, you can refer to the script based solution outlined in the dedicated KB article How to commit and push to a Git repo…

This is really slowing me down a lot (and seemingly other Thunderbird users), so I've had another look and found the related MailNews:Message Threading docs - the resp. 'E-mail Threading Primer' paragraph seems to confirm that while Lithium does add the fundamental message ID to each mail, it simply does not use the common…

@Jules Clements - the documentation has not been updated it seems, insofar this has been a preliminary YAML export feature that existed before the introduction of Bamboo Specs and has since been replaced by 'View project as Bamboo Specs', which only supports Bamboo Specs (Java) at this point though. In terms of 'formally…

Most of Atlassian's Java based products are using Jersey under the hood, which provides WADL support out of the box under a well known runtime URL, e.g. for Bamboo and Crowd: * https://{{host}}/bamboo/rest/api/latest/application.wadl (still works, just tested) *…

The REST API equivalent for 'triggerManualBuild.Action?buildKey=<project>-<plan>' is: * https://{{host}}/rest/api/latest/queue/{projectKey}-{buildKey} Unfortunately that REST endpoint lacks detailed docs for the parameters, though they are all explained for the related /queue/{projectKey}-{buildKey}-{buildNumber :…

The Bamboo REST API and esp. its documentation leaves a lot to be desired unfortunately. Regardless, based on the docs for /queue/{projectKey}-{buildKey}-{buildNumber : ([0-9]+)}?stage&executeAllStages, I've been able to trigger a build with one automatic and two manual stages in various ways as follows: *…

I've just verified that I can build the Bamboo Docker Plugin via the Atlassian Plugin SDK and Maven >= 3.2.5 (the SDK ships with Maven 3.2.1). This is probably the simplest way to gain access to the required Atlassian Maven Repositories that make those Atlassian dependencies available to your builds (they are not published…

Have just been about to ask the same - I honestly never quite understood why DC has been introduced for large user tiers only, and still remains positioned as such for Jira/Confluence, with the Bitbucket reduction being a highly welcome exception. As for specific use cases, there are e.g. many regulated industries with…

Hi @Corey Fruitman, you connect Jira to SES via SMTP similar to how you would do this for other mail providers. The entire process is conceptually covered in Using the Amazon SES SMTP Interface to Send Email, and the sub-topic Sending Email Through Amazon SES From Software Packages includes a Jira specific example by…

I think /opt/atlassian/jira/ is the default installation directory on Linux, whereas /var/atlassian/application-data/JIRA is the default Jira Server configuration directory on Linux, aka Jira home. You can search for the folders listed in the preceding section Set up the shared directory or the files listed in Important…

Hi Keith, As per Configure your existing Jira instance to work in a cluster, the 'cluster.properties' file has to be created in the Jira local home directory, and as per Jira home directory, the default location of the Jira home directory is: * C:\Program Files\Atlassian\Application Data\JIRA (on Windows) or *…

@Monique vdB - does everyone one this photo automatically qualify for the September challenge? While this particularly great shot has been taken by Sven, the entire photo shoot setting has technically been a group-selfie ;)

As Craig already pointed out (+1), you have most likely overstretched the performance profile of that T2 Instance, in particular due to running a long-lived process with constant CPU load. While T2 Instances have an excellent price/performance value for spiky workloads, their documented burst behavior is not suited for…

Hi Sebastian, We (Utoolity) are currently improving the public AWS Quick Starts for Atlassian products for our own needs, with a primary focus on cost reduction for development scenarios, and a secondary focus on UX/DX in terms of consistency across all products (many differences seem to be arbitrary indeed). We have…

Good question, somehow this URL seems gone, and the version navigator within the Bamboo docs seems broken (e.g. an older version for Bamboo 5.9 offers to switch to 6.6, but it does not work), hope someone from the Atlassian team takes note and fixes this. That being said, you can find the current version under Integrating…

Given you have the prerequisite AWS knowledge, the best way to achieve configuration 2 might be via the AWS Quick Starts for Jira Data Center and Confluence Data Center: As long as you restrict the Auto Scaling group to a single node, it used to be possible to simply install a Server license instead of a Data Center…

Just in case you haven't found it yet, I actually took the time to look it up and already provided the link about Using automatic merging from the 4.3 docs in parentheses behind the 6.6 one ;)

First of, to state the obvious, Bamboo 4.3 has reached its end of life in November 2014, which means it has not received any security updates since over 3.5 years. If this instance isn't completely locked out of the public internet, even just starting it "is not an option at this point, so please keep that in mind" ;)…

Assuming you are referring to one of the two Lambda related AWS integrations in the Atlassian Marketplace, the answer is yes, both are commercial and supported offerings as follows: * Tasks for AWS (Bamboo) provides the AWS Lambda Function task (see pricing, and try it free) * Automation with AWS (Bamboo) provides…

I'm afraid something like this is not available out of the box anymore, after Atlassian opted to remove the watch page feature from the published version of the Confluence Bamboo releases, which now states: You can get automated notifications about major Bamboo releases by subscribing to the Atlassian blog. Unfortunately…

Unfortunately Bamboo does not yet provide an advanced UI to guide users through custom build parameters, and I'm also not aware of any app that is able to offer a solution similar to what's available in Jenkins for example - please watch and vote for the following issue to further raise Atlassian's priority for this long…

As the vendor of any app published via the Atlassian Marketplace (formerly known as addon, formerly known as plugin), you can "Get a specific app’s active installation counts over time, aggregated by app version" from the app's listing page and via the Marketplace API: * UI => App's Marketplace listing => Link 'Manage app'…

Specifying arguments for Bamboo's Docker Runner is not supported yet - please watch and vote for the following issue to raise Atlassian's awareness of this requirement (workflow status is currently 'gathering interest'): * Allow use of arguments for Docker Runner (BAM-19793)

As outlined in more detail within Plan directory information REST API, the "bamboo.plan.directory.info.rest is a system property with the following settings": disabled (default) The plan directory information REST API is disabled and all requests will be rejected local The plan directory information REST API is available…

I see, sorry I misread your question - to further clarify the issue: * Your two statements "buildKey can get the value, but it is returning empty null string" and now "${buildKey} [...] gives value as PROJ1-PLAN1" seem to contradict each other? * Does your statement "This problem is occurring in Bamboo 5.9.7 version and…

This should work conceptually, are you correctly passing the variable to the builder? This is a required step that's easy to forget, see Passing Bamboo variables to a build script: Bamboo global and build specific variables can be referred to in build scripts or maven pom.xml. Bamboo variables are not directly available in…

Yes, you can optionally specify a custom domain name via a parameter of the CloudFormation template that deploys the Jira Data Center Quick Start, see parameter 'Existing DNS Name' in the deployment guide (AWS) or Configuring JIRA Data Center on AWS (Atlassian): Existing custom DNS name for your JIRA Data Center instance.…

This is not possible as such for tasks in general - that being said, given you are using the Bamboo Script task, you could store your script in a repository and use a Script location of type File rather than Inline: Script location Select the location of the script file. * File — enter the location of the file in…

You can achieve this by migrating your entire Bamboo plan configuration to Bamboo Specs, which precisely aims to "store build plans configuration as code". Job artifacts are supported in both the Bamboo Specs (Java) and the Bamboo Specs (YAML) flavor, but please note that the former offers considerably more encompassing…