Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Build and deployment triggers randomly not working correctly

Alexander Reifinger
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 3, 2021

(Bamboo 7.2.4 connected with Bitbucket Server)

 

Since 3 days, our triggers behave more and more erratic. Pushing to branches sometimes causes a build to run, then the next push is ignored. Feature branches tend to work better, the default branch most of the times does not work at all.

Also, deployments that should be triggered by successful builds are unreliable, most of the time they are not triggered. So I think it is not a problem with the bitbucket connection.

Since today, we also have the issue that merging a branch to master in at least one repository causes *all* the feature branches to be triggered, I just had more than 100 queued builds because something was merged into master.

 

The catalina.out showed this many times when the issue was discovered:

30-Nov-2021 16:58:25.211 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [lucene-tracked-searchers-pruner-pool-6-thread-1] but has failed to stop it. This is very likely to create a memory leak.

I am not sure it is related, and since we restarted first bamboo, then even the server completely, the catalina.out is not showing anything that might help.

We tried removing the repository connection and re-adding it, both normal and linked repository show the same issue.

As we have dozens of build plans with the same behaviour, I can rule out a changed setting in the build plan, and also in the global audit log I see nothing that might be related.

I am out of ideas, happy if someone could give me a pointer on where to look!

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events