Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,467,594
Community Members
 
Community Events
177
Community Groups

Re-ask: How to get bamboo to intelligently re-use build results?

This is a re-ask of this question as it appears to have been both misunderstood and to have fallen off the radar.

 

The question boils down to getting bamboo to work nicely with a fast-forward merge strategy. In such a strategy, not every merge to the master branch results in a merge commit. Some simply re-point the master branch to the relevant commit, which might already have a build associated with it. Since builds can take a long time in some cases, it would be great if bamboo could automatically update the master branch plan to point to the results of the build from the development branch plan instead of re-running a build. Given that the commit hash would be the same in a case of a fast-forward merge, this would be completely safe to do (unless the build makes use of timestamps in a weird way, but that's a separate issue)

If bamboo isn't capable of this, how might one submit a ticket for it and try to get attention to said ticket?

1 answer

1 vote
Foong Atlassian Team Sep 03, 2018

Since Bamboo Script task can be scripted to perform different command depending on the branches, Bamboo will just run the build for the same commit in the master plan.

Have created the feature request https://jira.atlassian.com/browse/BAM-20074

I can't comment on the ticket, but it would be nice in general if bamboo could trigger builds based on the tree hash instead of the commit hash. You can get the tree by `git show --pretty=format:%T HEAD`. This way someone could modify their commit message or change authorship without having to re-run tests.

Can see all commit metadata with git cat-file commit HEAD

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events