Steffen Opel [Utoolity] Community Champion

There used to be a Bamboo Cloud version, but unfortunately Atlassian has decided to discontinue it as of January 31, 2017- the former Bamboo Cloud EOL announcement is nowhere to be found anymore, but you can find some details in the Bamboo Cloud end of life? thread. The TL;DR is that Atlassian meanwhile recommends…

While 2 is possible (Bamboo supports Windows just fine), I would highly recommend against running two Bamboo servers just for this reason, because it will unnecessarily increase your infrastructure cost and operational complexity. Option 1 is therefore the recommended and widely used approach: Provided your license…

It is indeed possible to Customize the issue collector 'in a number of different ways', e.g.: * Set up a custom trigger, so the feedback form launches from a different link or button than the packaged triggers provided. * Set the default values of fields for your users, using JavaScript. * Specify the values of fields on…

Alternatively, is there a way to identify the organization name from the exported ID number? E.g. is there is a way to export an organizations list containing ID and Name? I don't have an answer for your preferred scenario, but as for this question, you can achieve this by means of the Jira Service Desk REST API (Server |…

As a licensee, you can download all (well, most ...) sources of Atlassian products from your my.atlassian.com page: * find and expand an active license of the product in question * click the 'Download source' action beneath your license key on the right * click the archive link for the version(s) you are interested in For…

Interesting question - I'm not a shell scripting expert, but the following approach based on I/O Redirection to additional file descriptors seems to work well: #!/bin/bash exec 5>&1 RESULT=$(<cmd> | tee /dev/fd/5) IMAGE_ID=$(python -c "<do sth. with $RESULT>") Here's a test command to demonstrate it with Bamboo's Script…

@Nadine Racine -Yes, JSD automation and Automation (Lite) for Jira are using two entirely separate automation rule engines behind the scenes, so conceptually you can mix and match them as you please. Of course, you need to avoid interfering with yourself by creating loops (rules in both engines triggering each other),…

Glad it helps @William King - 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!

@Nadine Racine - I only just now noticed you response and that I messed up my answer here, sorry about that: Other than many apps, 'Automation Lite for Jira' has a separate Marketplace listing for the Cloud version, and I accidentally linked the Server version instead (now corrected). I hope you have found it yourself…

Scheduled deployments are a popular feature request, but unfortunately not available yet - please watch and vote for the following related issues to further raise Atlassian's awareness of this requirement: * Ability to schedule a one-off deployment (BAM-13819) * Allow deployments at a specific date & time (BAM-13517)

@Lars Olav Velle - most likely this refers to Introducing Identity Manager for Atlassian Cloud products: Atlassian Cloud customers have received an email "Updates to password policies & Atlassian Cloud administration", advising them now being part of the early access program and thus able to continue Identity…

Apparently not just yet, but the Identity Manager landing page claims that its "features work across your users on the following Atlassian Cloud products", and the resp. table lists "SAML single sign-on" and "Enforced two-step verification" for Bitbucket as "Coming soon".

There is not yet a native automation rule for Jira Service Desk that covers this, please watch and vote for the following related issues to raise Atlassian's awareness of this scenario: * Create Linked Issue Automation Rule (JSDCLOUD-4673) * Automation rule to create new issue in another project with information from…

I realize you have identified a solution already, just in case: The information is a bit buried, but given you are implementing a custom plugin, you might want to check section 'Reading Logs' in the Task overview, which references a dedicated Java interface for log interception at runtime: We've added infrastructure for…

This is most likely an error on the Notify.events service side of things, because they managed to let their Let's encrypt based SSL certificate expire a couple of days ago and apparently didn't even notice yet (which isn't exactly encouraging regarding the quality of a public software as a service offering btw.) - here's…

I'm afraid this feature is only partially available at this time, insofar the respective -Datlassian.bamboo.build.disable=true system property currently only works for remote and repository triggered builds, but does not yet cover scheduled builds - please watch and vote for the following issues to increase…

I'm afraid this has been a deliberate change based on Atlassian's observation that the behavior you've been relying on was considered a usability flaw, as further detailed in Disabling a job from the plan branch results does not disable the job for the main plan (BAM-18365): Disabling a job from the plan branch results…

Thanks @Boris Berenberg - Atlas Authority - seems a no is the correct answer then. The request is for Server right now, but would apply to Cloud scenarios too down the road. I've scheduled a backlog item for our team now, let's see whether we can up with something (looks like the typical 'hardly enough pain to tackle it'…

I'm assuming you are referring to Modifying notification templates?! IIRC, similar to how the Freemarker ${buildSummary} variable basically exposes the resp. Java API BuildResultsSummary interface, the ${deploymentResult} variable basically exposes the resp. Java API DeploymentResult interface. You can see this in action…

The -e and --email flags flags have been removed from Docker engine as of release 17.06, so presumably the Docker CLI on your agents is a more recent version. I don't know off hand how the Bamboo Docker task handles this, but given that all fields are optional because you can "Leave these credentials empty to use the…

Thanks for the follow-up @Philip Colmer, using plan branches without the main plan is a neat approach I never even considered!

As long as you are only using long lived branches as outlined, you should be able to just use a single plan, create a manual plan branch, and then override the variables in the plan branch details configuration:

@Johannes_Brunswicker - I have updated my answer regarding the meanwhile available Bamboo 6.1 release, which now supports plan permissions in Bamboo Specs.

Assuming "querying apis from users endpoint" means sending REST requests from external systems to Bitbucket Server, you might want to read Mibex Software's nice walk through on How to use OAuth with Atlassian products - their example is based on Bamboo, but applies to Bitbucket Server as well: While Atlassian’s cloud…

You do not need to build a custom application in AWS for this to work, and as per Mibex Software's nice walk through on How to use OAuth with Atlassian products you can "just use any application URL"- their example is based on Bamboo, but applies to JIRA as well: While Atlassian’s cloud solutions like Bitbucket Cloud make…

Just a best guess from previous SES usage, but I think you might be encountering the following two issues: * As per Amazon SES SMTP Issues, "Amazon EC2 imposes default sending limits on email sent via port 25 and throttles outbound connections if you attempt to exceed those limits. [...] You can also connect to Amazon SES…

Glad it helps @Brad Riching - 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!

I have not done this before, but it's an interesting challenge :) To expand on @Alexey Chystoprudov's answer (+1), here's how I'd try to tackle an end to end automation based on our own (commercial) add-on (which currently requires that you have an AWS account yourself): * Implement the code to dedicate the agents via the…

For undisclosed reasons those examples seem to have been archived to atlassianarchive/bamboo-sdk-examples (presumably due to being considered outdated). That being said, I think following the applicable tutorials linked in the page's Resources section (in particular the Introduction to writing Tasks) should be your…

@Jeremy Roelfs - I'm not well versed in UI testing, sorry. Accordingly, I recommend to either ask a new question here, or reach out to one of the two vendors that seem to support UI test integration with a Bamboo add-on directly: * Charlotte - ask a tagged question here or submit a support request to them * X-Ray - ask a…