Steffen Opel [Utoolity] Community Champion

Unfortunately Bamboo doesn't support automated feature branching workflows based on deployment plans or environments as of today, despite Atlassian (rightfully) promoting this very development process in general, for example in section Feature Branch Workflow within the excellent 'Getting Git Right' guide, or in…

Hi @Bryce Ashey - are you using Bamboo Cloud or Bamboo Server?

There are two Slack notification add-ons available in the Atlassian Marketplace, which address these requirements for Bamboo Server scenarios (I realize that you are on Bamboo Cloud, see below): * Slack Bamboo Plugin (free) * Slack Notifications for Bamboo (commercial) Unfortunately 3rd party add-ons are not available for…

Sigh, same for me of course, sorry for not checking this right away - hopefully this is just by chance of a permission issue, I wouldn't expect anyone to enable public sign-up, only to deny any participation thereafter (David should have gotten a notification from my mention above, so hopefully he'll be able to fix this…

@Swift Capital - sorry, just realized your comment about the official issue tracker not allowing for new tickets. I've been able to sign-up for a new account just fine a few seconds ago (which is a requirement though), so maybe you want to try again?

@Swift Capital - given version 1.3.0 has been specifically released for compatibility with Bamboo 5.10 (which had significant API changes, though the topic at hand only rings a faint bell for me right now), it seems like this might be an oversight or regression in this regard. Accordingly, a fix would most likely require a…

Which version of Bamboo and the New Relic for Bamboo add-on are you using (see versions for the latter)?

This timeout does not seem to be configurable yet: Due to Atlassian's AWS CodeDeploy task being easy to confuse with the various AWS CodeDeploy tasks offered by Utoolity's Tasks for AWS add-on for Bamboo Server (notably the AWS CodeDeploy Deployment task), a user recently asked the related question How to increase the…

To search for issues NOT flagged, you can simply negate the advanced search query, i.e. use either an explicit negation NOT not (Flagged = Impediment) or the shorthand notation for inequality Flagged != Impediment or, to be more future proof if more flag values get introduced, use NOT IN Flagged not in (Impediment)

Ah, good to know, thanks - hopefully this can/will be picked up by someone anytime soon 

Unfortunately this is indeed not yet available for deployments - please watch and vote for the following issue to guide Atlassian's roadmap in this regard: * https://jira.atlassian.com/browse/BAM-13274 Potential Workarounds I've contemplated the following limited workarounds: * You could use any of the many available OSS…

The support guy from Slack is mistaken: I'm not even aware of any Bitbucket Cloud add-ons for integrating with Slack (though there might be some that are not listed in the Atlassian Marketplace yet). Either way, the Slack notifications plugin (only) supports Bitbucket Server and seems to work fine for several hundred…

The Slack notifications plugin already supports Bitbucket Server (formerly Stash) up to and including the most recent 4.4.x versions (refer to its Version History for details). * Many Bitbucket Server add-ons still carry 'Stash' in the add-on key, because the host product has simply been renamed from Stash to Bitbucket…

Unfortunately project level configuration and permissions are amongst the longest standing Bamboo feature requests, and I'm not aware of any workaround - please watch/vote/comment on the following issues to further raise awareness for this significant limitation: * https://jira.atlassian.com/browse/BAM-2470 *…

I think this is not possible at this point - you can vote/watch/comment on the resp. issue https://jira.atlassian.com/browse/CQ-1873 to raise awareness for this usability flaw.

@Thiago Bomfim - thanks much for the update and handling this so thoroughly, much appreciated.

@Sander Verschuren - agreed: I have referenced your suggestion on BAM-15464, hopefully Atlassian will add a resp. note to the documentation to spare other users the trouble until HTTP(S) authentication is available.

Unfortunately Bamboo does not yet support HTTP(S) authentication with Stash repositories - you can vote/watch/comment on the resp. issue to raise awareness for this scenario: * https://jira.atlassian.com/browse/BAM-15464

The docs seem to be defunct cross link wise (as increasingly often I'm afraid), and strangely nothing shows up in a search for "pull request task" even, despite the feature being properly documented as such in section Pull request tasks within Review and discuss a pull request (manually crafted anchor link): You can attach…

Utoolity's (commercial) Tasks for AWS (Bamboo) add-on offers dedicated tasks for several Amazon Web Services (AWS) products, including AWS Elastic Beanstalk, see Deploying to AWS Elastic Beanstalk for details - available tasks related to Elastic Beanstalk integration are: * Elastic Beanstalk Environment task * Elastic…

Inline editing is surprisingly not available as a built-in feature in Bitbucket Server yet, please watch/vote/comment on the following feature request to raise Atlassian's priority in this regard: * https://jira.atlassian.com/browse/BSERV-3032 The issue references the two available add-ons that do address this: *…

Atlassian Crowd does not offer any auditing features as of today, unfortunately (and somewhat ironically, given Crowd is primarily used in more security sensitive Enterprise scenarios) - please watch/vote/comment on the following feature request to further increase awareness for this notable limitation (it's one of the…

I see, sorry for missing that important aspect - I've amended my answer accordingly, with the TL;DR being that I think you need to resort to manually queuing and launching builds indeed. Are you by chance using AWS? We (Utoolity) are contemplating a conceptually related 'Amazon S3 repository' type so that we could add…

Good question, that's indeed not obvious when reading about Configuring plans, where Linking to source code repositories seems to be a required step, even though using Bamboo without a source code repository is no problem at all - somewhat counter intuitively, you still need to select 'Link new repository', but with a…

You need to follow the steps outlined in Defining a new Docker capability that are appropriate for your agent configuration: You need to define (that is, 'register') a Docker capability in Bamboo before you can use a Docker task in Bamboo builds and deployments. It sounds like you plan to use your local agents, so likely…

I have not tested this, but given AWS CodeCommit facilitates a credential helper too and the error being`command not found`, I would assume you are affected by the same issue outlined in the SourceTree Knowledge Base article Credential helpers "git: 'credential-osxkeychain' is not a git command. See 'git --help'." The…

This can be achieved with Edward Webb's excellent Bamboo Agent REST APIs add-on, which, amongst other features, exposes REST endpoints to: * force enable and disable agents (same as UI but uses tokens) * request maintenance & disable (ideal for automation, limits impact to total capacity) * [...] It specifically addresses…

@Dev Ops - this won't help you right away, but Utoolity is currently working on a (commercial) add-on that would ultimately allow this (we have just postponed the 1.0 release in favor of a related and enabling feature within https://marketplace.atlassian.com/plugins/net.utoolity.atlassian.bamboo.tasks-for-aws though).…

This feature does not yet exist in Bamboo, and I'm not aware of a resp. add-on either. More specifically, your use case has two aspects/requirements: * A new notification recipient type that implements a webhook for Bamboo, similar to e.g. the POST service webhook for Stash or Webhooks in JIRA - this requires Building a…

There are certainly a couple of alternatives and/or workarounds, though most seem to come with their own constraints in turn, see for example: * https://jira.atlassian.com/browse/BAM-17260 * https://jira.atlassian.com/browse/BAM-17886 The latter specifically mentions a trigger that's based on a tag, and then refers to…