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,458,610
Community Members
 
Community Events
176
Community Groups

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

Atlassian Community Events