Bamboo build on new git tag

[Jeff Behl]

We're using Stash and Bamboo. I'd like to have a build triggered on a tag whenever a tag is added to a specific branch. It seems this feature request is something along those lines, though not precisely:

https://jira.atlassian.com/browse/BAM-13618

Since this doesn't seem to be possible currently out of the box, what would be the best way to accomplish this, even if it involved some scripting?

Thanks

[cofarrell · Accepted solution]

Hi Jeff,

Unfortunately Bamboo doesn't currently have support for anything other than branches. For now you will have to create branches to match your tags. There really isn't anything else you can do.

Whether that's in a client-side script that pushes new branches to Stash, or whether that's a plugin in Stash that does it automatically when somone pushes a tag that's up to you. I'm happy to help if you get stuck on this part.

If you're worried/against the idea of putting branches in your normal repository the slight variation would be to mirror your repository and only create the branches in the fork. That means that normal users won't be aware of those extra branches being created, but bamboo can build from them.

I hope that helps.

Charles

PS. While this may seem unrelated, you might want to vote on the following as well. Depending on how this is implemented, if Bamboo supports all refs then that should encompass tags as well:

https://jira.atlassian.com/browse/BAM-11205

[Jeff Behl]

Thanks for the information Charles. One followup question: you say "Bamboo doesn't currently have support for anything other than branches." However, you can specify a tag when specifying a new branch in Bamboo, as mentioned in the dialogue "The name of the branch (or tag) containing source code". This being the case, I support I could script up something that adds a new "branch", but is actually basing it on a tag, correct?

Pardon if any of the above doesn't make sense. I'm relatively new to git/stash, and bamboo.

[cofarrell]

Hi Jeff,

Thanks for the correction. You're quite right that you can build against a tag in a new repository in a plan (which is where that text comes from).

However, the problem lies specfically with "branch builds", which are unfortunately exactly that. You can't automatically detect _new_ tags (or any ref - which can be used for things like pull requests).

So for now, if you want Bamboo to automatically create a 'branch' build against your tags, you will need some form of script.

Cheers,

Charles

[Ulrik Hald]

This question is about a year old new, so I would like to know if there are any improvements when it comes to handling git tags in Bamboo? Our CI model is built around git tags and thus I need to auto-trigger a build in Bamboo whenever I push an annotated tag to my repository (which is hosted in Stash). Similarly, once a build is triggered this way, I would like for Bamboo to point out that a new tag was the reason for the build. If the workaround "For now you will have to create branches to match your tags." still applies, I would like to have some guidance in how to manage this automatically inside Stash (eg. using plugin), if possible.

[Rowan]

+1 can we get an update on this? Branches and tags are just refs in git, so it seems like it should be reasonably easy to trigger on new tags...

[Mart Klanberg]

+1 Relevant even 6 months later.

[AlexandruB]

+1 Is there any new information about this ?

[zhouhuab NA]

+1 trigger on tag is really important

[Tim Foster]

+1 would like this feature as well

[Ondrej Medek]

+1 too

[Ronny Weil]

+1

[Mark Gabriel]

+1

[alex_sherwin]

+1

[h17liner]

+1

[Francois Montmasson]

+1

[Ilya Mazya]

+1

[David Schlesinger]

+1

[Martin Strycek]

+1

[Dion Gonano]

+1

[Matthew Frey]

+1

Supporting this would make npm version driven builds much cleaner.

[Grzegorz Śliwiński]

+1

[Rita_Garcia]

We use tags to help denote the latest version to use. It would be nice to have this tag used as well for deployments.

+1

[IT ADVITOS]

+1

[Jack Cheung]

+1 We also need tag for QA and deployment

[dsanchezpillot]

+1

[Yagnesh_Mistry]

+1

[Shubham Ranjan]

+1

[Matthew Pearsall]

+1

[zaf.dalvie]

+1

[jjaenike]

+1

[Александр Колпаков]

+1

[schow-lmi3d]

+2

[Aaron Williams]

+1 omg 6 years later

[ulutasriza]

Its almost 6 years, still no solution ??

[conan_chen]

+1

[shaynen]

2020 and this fundamental show stopper of a feature still isn't in! 

This is a product that prevents you from using *standard best practices*, and that means Bamboo isn't a functional product yet.

+1

[Bill Wang]

Ask for votes, yes, we voted, it is already 166 votes. 

Surprise after 6 years, we still don't get this basic feature assigned. 

https://jira.atlassian.com/browse/BAM-11205

[Ole Koeckemann]

so sad

[Jason Kinnear]

+1

[Krystian Brazulewicz]

Hi everyone,

Thanks for your interest in this issue. We fully understand that many of you are dependent on this functionality.

If you're interested in Bamboo support for building forks of repositories please vote on https://jira.atlassian.com/browse/BAM-11205

If you're interested in Bamboo support for triggering builds after tag has been pushed to repository please vote on https://jira.atlassian.com/browse/BAM-17800

We typically review highly voted suggestions every 6 months, at which point we consider whether we want to include it on our roadmap.

Cheers,

Krystian Brazulewicz

Bamboo Team

[Gustavo Muniz do Carmo]

+1

[Andres]

+1

[johngillwp]

+1

Five years later and still no solution...

[Orion IT Team]

+1

[Levente Szabo _Midori_]

While Atlassian delivers this, there is an alternative way you can try. Create an automation rule using the Automation for Jira and the Better DevOps Automation for Jira apps.

Use the Tag Created trigger and one of the "starting a Bamboo build..." recipes.

The trigger also sets a smart value for the tag that you can use in your automation action -  {{devops.tag}}

(Please note that Better DevOps Automation is a paid and supported app, and I'm part of the team developing it.)

[stsivin]

+1

[roman_breuer_hta]

+1

[Vaisakh PS]

+1 . why atlassian is not ready to implement this functionality?

[Xavi Pedrals]

+1

[diegomarcov-uns]

+1