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,298,446
Community Members
 
Community Events
165
Community Groups

Bamboo planbranch setting to prevent deletion pendant in database Part 2

Hello @Eduardo Alvarenga,
I have already accepted the answer to my previous question (Bamboo planbranch setting to prevent deletion pendant in database ), because I was able to find the setting in the column you have described.
Unfortunately, after changing the setting "Clean up plan branch automatically" of a specific planbranch, it has no effect on the XML_DEFINITION_DATA column. Even after creating a new plan branch having a different setting, the element <disabled> always has the value "false".
So, this column seems to be deprecated, and there has to be another field/file, where this information is getting stored.
Could you please reevaluate the information?

2 answers

0 votes

Hey @HeWi, Good to help you again!

The XML_DEFINITION_DATA column is updated on the BUILD_DEFINITION table whenever you enable or disable the "Clean up plan branch automatically" setting on a Plan Branch. That column is not deprecated.

Examples

When enabled:

<branchConfiguration>
  <cleanup><disabled>false</disabled></cleanup>
(...)
</branchConfiguration>

When disabled:

<branchConfiguration>
  <cleanup><disabled>true</disabled></cleanup>
(...)
</branchConfiguration>

I recommend you reach out to Atlassian Support and open a ticket if your issue still persists.

Regards,

Eduardo Alvarenga
Atlassian Support APAC

Yes, okay, correct, @Eduardo Alvarenga,

the XML_DEFINITION_DATA gets changed after saving the planbranch settings, BUT:

There has to be another value/table effecting the checkbox, because when the value of planbranch A (disabled: false) gets updated via SQL statement in the column XML_DEFINITION_DATA with the value of planbranch B (disabled: true), Bamboo still shows the checkbox of planbranch A being enabled, even after reloading the buildplan page.

Can you explain, why that is happening and which other value is being responsible for the checkbox in Bamboo showing the effect of updating the database value? Only after restarting the bamboo service, the setting takes effect. Why does it work when initiated via the buildplan settings in the Bamboo GUI (without restarting the bamboo service).

Why is not Bamboo applying the updated database values after reloading the buildplan page? What has to be done? Is Bamboo using some kind of cache?

Suggest an answer

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

Bamboo Data Center on Kubernetes

Hi, If you are running self-managed environments and looking to adopt modern infrastructure, Bamboo Data Center can now be deployed in a Kubernetes cluster. By leveraging Kubernetes, you can easily...

961 views 3 8
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