Pre-release steps

1. [V] Download the installation RPM nexus-2.7.2-3.el6.x86_64.rpm .

Release steps

1. [V] set up the outage page redirect for the web interface and service unavailable for the repositories. 10.34.2.144 should be an exception.
2. [V] Install the RPM
3. [V] Check, that /services/nexus/nexus symlink exists. It should now point to the latest Nexus version. All puppet files pointing to the current (numbered) directory shall be changed to point to this symlink instead.
4. [V] Check, if /services/nexus/nexus/bin/nexus has following line:\\RUN_AS_USER=jetty
   
5. [V] Check /services/nexus/nexus/conf/nexus.properties . Eloqua URL must be http://www.stage.redhat.com on staging, while http://www.redhat.com on production
6. [V] Update configuration file as described in this ticket https://engineering.redhat.com/rt/Ticket/Display.html?id=290105 (it was for staging). Make sure to modify it in Puppet, if the file is there.
7. [V, H] Turn on Puppet and check the modified files are in place
8. [V] Start the Nexus service
9. [V,H] check the nexus-gc.log for errors
10. [H] Check login using Jboss realm
11. [H] Check the branding logo
12. [H] Check Eloqua tracking plugin
13. [V] remove the redirect to the maintenance page

Rollback

1. [V] stop the new version of nexus
2. [V] ask IT to revert the disk to the last backup
3. [V] start Nexus service
4. [H] check the functionality
5. [V] remove the redirect to the maintenance page