-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fletcher,
On 1/23/2010 11:17 AM, Fletcher Cocquyt wrote:
This process is not perfectly defined and slow - the developer's check all the
code into SVN and tag the release - ops checks it all out and builds it on the
tomcat nodes with the dev
Fletcher Cocquyt fcocquyt at stanford.edu writes:
Hi, this question is coming from the operations team perspective.
Currently our (small 3 member) ops team is responsible for deploying java apps
weekly from a set of dozens in a less than great 4am-6am window on Wednesdays.
..snip..
So
Continous Integration sounds like a better solution for you. Your apps will
be built and tested as soon as the developer checks in their code in SVN.
Have a look at http://cruisecontrol.sourceforge.net
Using CruiseControl will ensure that the developers wont check-in anything
with errors on it.
Hi, this question is coming from the operations team perspective.
Currently our (small 3 member) ops team is responsible for deploying java apps
weekly from a set of dozens in a less than great 4am-6am window on Wednesdays.
This process is not perfectly defined and slow - the developer's check
Hello,
Maven can for sure cover all these needs. But be aware that it has a steep
learning curve and that if someone uses it, everybody should do so.
Depending upon your role on the project the required level of knowledge will
vary, though. For an operationnal guy it may reduce to launch 2 or 3
How about CI - continious integration server that builds, tests, and
deploys the apps if the tests are successful?
There are a few great CI servers out there. I happen to use Bamboo
from atlassian. All CI use a build tool like ant or maven.
CI would make your small ops team superstars.
On
