I'm planning to extend the build plan of my application to include the execution of integration tests. For this, it's necessary to deploy my application to tomcat before running any selenium test.
With some googling I found this manual page: https://confluence.atlassian.com/display/AOD/Using+Tomcat+with+Bamboo+for+continuous+deployment
According to the previous page, bamboo will continuously deploy my application to the same running tomcat instance. The problem is that sooner or later this will cause a permgen problem and tomcat will have to be restarted manualy.
Is there anyway of integrating bamboo with tomcat in a way that the container is tottally started for each deploy and shut down at the finish?
Answering my own question, I followed Alexander's advice and wrote up a bash script for killing a possible running tomcat instance, delete the previous installation, create a new installation from the original zip file, configure tomcat-users.xml, and start tomcat. I used this bash script for creating a new script task within Bamboo. This task is followed by the ordinary tomcat deploy task, and everything is working like a charm now...
Alexander, is there any trick for avoiding permgen issues? Do you have any gotcha in the configurations of tomcat or bamboo? Are you using any JVM different from oracle's hotspot?
I have never seen someone performs thousands of deploys in a same running tomcat without having to restart it due to some problem (normally, permgen issues)...
Hi Community! I’m Elaine, Confluence Product Manager. You may have read my earlier post about page tree in space navigation sidebar. I'm excited to share another improvement that helps you organize ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs