Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bamboo Specs scanning clobbers Build Status screen

I am on Bamboo 6.8.1

I am using a mono-repo with 200 components in it using change detection to limit what change triggers each plan.

This means I have 200 PlanSpec*.java files which get processed by the Bamboo specs scanner.

If I change one of those Java Specs files, the scanner detects the change and compiles all 200 specs.

I could live with that if that was all it did but here is the issue it causes.

On my Build Dashboard page (All Build Plans), I have a mixture of successful/failed builds.

After the scanner runs, they all turn green with the Reason field set to "Specs configuration updated"

So, I can not see the "real" Build failures anymore.

Thiis would be fine if I could filter the results to ignore "Specs configuration updated" and/or show only those builds where the "real" build failed"

Any ideas on:

  • Only trigger Spec compilation for the changed spec only
  • A way of filtering Build results

Thanks

1 answer

2 votes

Internally Bamboo updates plan only if Java specs was modified. It improves performance of heavy operation to run massive update of 200 plans. But then it has to report execution and Specs result attached to every plan was a decision to improve visibility of this feature. 

Now when more and more people switch to this solution it doesn't look so wise. We're working to improve user experience and detach build result from specs result so it's not appear at dashboard anymore.

As I see our support engineer already created issue for tracking our work at it - https://jira.atlassian.com/browse/BAM-20519

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

215 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you