If you are interested in running Nexus and Hudson on Amazon's Elastic Computing (EC2) service, there is now a public image that contains Maven, Nexus, Hudson, and the OpenJDK. If you use Amazon's easy-to-use AWS Console, running a state-of-the-art build service with Nexus and Hudson is one click away. Here are the details for those of you interested in running Nexus and Hudson on the cloud:
Launch it. In minutes, you will have a capable build server. Read more to find out about some suggested next steps to secure your new build server.
What's Installed? This instance is simply the latest installation of Hudson 1.309, Nexus 1.3.4 Open Source, OpenJDK 1.6.0, and Maven 2.1.0. Nexus is installed in /usr/local/nexus and Hudson is installed on Tomcat 6.0.20 in /usr/local/hudson. Both Nexus and Hudson are configured to startup in /etc/init.d/nexus and /etc/init.d/hudson.
Post Launch Instructions: Since Nexus and Hudson are both running with the default authentication configuration, it is imperative that you change the default administrative password of Nexus after installation (the default is "admin123"). To change the Nexus password:
Also, it is imperative that you turn on security for your Hudson instance. To do this:
While you are at it, you will need to configure Hudson's JDK and Maven installation. To do this:
If you are planning on running this instance as a long-running build server, you will likely want to configure the sonatype-work directory to run on an EBS volume. If you do end up running Hudson and Nexus on this instance for a long time, and you are planning on depending on it: invest in an EBS volume and move /usr/local/nexus and /usr/local/hudson to run on that persistent volume. This way, you'll have the peace of mind that your build and repository data will persistent in the event of unforeseen downtime.
Happy Nexusing