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,459,369
Community Members
 
Community Events
176
Community Groups

Bamboo limitations Vs. Jenkins : Conditional stages

So .. I am currently looking to migrate our existing Jenkins environment to Bamboo (the obvious advantages being better integration with Jira/Bitbucket/etc .. Repo caching on the Bamboo Server, ... )

But .. it is proving very frustrating to implement anything other than the absolute simplest of strategies .... which are simply not adequate for us. I am hoping I am just not seeing something obvious and maybe someone out there has any ideas as to how I might achieve what we need ..

We make a number of changes to our source code repos that require a bit of analysis and based upon that analysis may or may not trigger a rebuild. In order to take advantage of Plan Dependencies, I need to be able to trigger a Plan and then (preferably within the first Stage of that plan) decide whether the change warrants a version increment and a rebuild. The best example here being C++ libraries that may or may not contain ABI breaking code. We rebuild our libraries and update the reference (usually a symbolic link) within the downstream repo to point to the new C++ libraries. If the new library maintains the same ABI then the module does not need to be rebuilt but an ABI break would warrant a rebuild.

What I would like to be able to do is, within the first stage of the build plan, look at the code base and decide whether the current changeset warrants a rebuild. I cannot see any way of exiting the plan without 'Failing' the build .. 

The best option would be 'No Build Required' status or a 'Success' status (but without executing the subsequent stages).

The functionality we require has, as far as I can see, already been rejected in https://jira.atlassian.com/browse/BAM-13321 but I was wondering if anyone has found a workaround ...

 

This is a big blocker for us and (especially given improved integration to Jenkins in Bitbucket 6.8) makes tools like Jenkins more attractive :( 

 

Thanks in advance for any help

Mark

 

PS. I know Bamboo get's used for lots of different projects but I this comment in BAM-13321 made me laugh..!

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events