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

Your Points Tracker
  • 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
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?
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

After recent Bamboo upgrade to 5.15.5 we are noticing automatic plan branch detection issues Edited

After a couple of days post our bamboo upgrade to 5.15.5 version, we are noticing few issues in bamboo. Branches added in Bitbucket are not automatically added in bamboo despite the auto plan branch enabled and manually adding them in bamboo is generating the following error:-

could not execute batch; SQL [insert into VCS_BRANCH (NAME, DETECTED_DELETION_DATE, CHAIN_ID, VCS_BRANCH_ID) values (?, ?, ?, ?)]; constraint [BAMBOOP.SYS_C006420]; nested exception is org.hibernate.exception.ConstraintViolationException: could not execute batch

This is occuring for most of the branches across most of the plans and never happened before. Apart from the upgrade nothing else has changed on Bitbucket or bamboo end.

We are also seeing similar errors at times when a plan build automatically gets triggered (due to triggers) or is run manually, wherein these are again the sql errors indicative of the fact that the db tables are not accepting the new results.

I wonder why the database is behaving so weird now, and does that mean we need a restart of the database or a restart of bamboo server.

Kindly advise as its blcoking our work to a great extent.

Any help here will be greatly appreciated.



1 answer

Possibly due to some issue with the post upgrade re-indexing, the plan branches would update in the database but never show up in UI and hence casuing those error messages.

Suggest an answer

Log in or Sign up to answer
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 ...

251 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