Hi Justin,
There many different ways to deploy a war and it depends a lot on your configuration.
One of the simplest ways is to do a POST to the tomcat manager app for the deployment.
You could use the built in Bamboo tasks for this, bypassing nexus and rundeck.
Or you can write a simple script which downloads the war on server and moves it to the webapps folder relying on autodeploy in tomcat config.
I often deploy multiple wars, which tend to overload the server if they are deployed serially through the manager app, so I wrote a simple script
which stops tomcat, moves wars from nexus into webapps folder, starts tomcat and tails the output log for successful startup.
This is started trough a Rundeck task in a bamboo deployment project.
On the Bamboo side there are a few gotchas.
Firstly I think the nexus plugin is no longer maintained and it did give me some problems.
I use the maven task to execute nexus-maven-plugin goals.
Secondly the bamboo rundeck plugin hasn't been updated in a long time and won't work with bamboo 5.x.
I forked the plugin and made the minimal adjustments to make it work here:
https://github.com/tadukurow/bamboo-rundeck-pluginAnother fork which I haven't checked out is:
https://github.com/leftathome/bamboo-rundeck-pluginIf you plan on using my fork remember to update your bamboo dom4j lib to 1.6.1.
Op woensdag 6 augustus 2014 22:07:29 UTC+9 schreef Justin Frost: