Details

      Description

      Pre-release steps

      1. [V] Download the installation RPM nexus-2.2.1-1.el5.x86_64.rpm.

      Release steps

      1. [V] set up the outage page redirect for the web interface and service unavailable for the repositories
      2. [V] Wait till the sheduled disk backup is complete
      3. [V] Turn off puppet
      4. [V] Install the RPM
      5. [V] Check, if /services/nexus/nexus-professional-2.2.1/bin/nexus has following line:\\RUN_AS_USER=jetty
        If it is not the case, it would be great, if you can find why. I always suspected Puppet.
      6. [V] Resolve puppet files (nexus.properties and nexus.), that are in the new directory (version number has changed to 2.2.1)
      7. [V] If possible, apply the variable improvement we discussed today (single template for nexus.properties, that uses Puppet variables)
      8. [V] Check the existence of tmp folder. Its owner must be jetty. (It shall be in /services/nexus/nexus-professional-2.2.1)
      9. [V, H] Turn on Puppet and check the modified files are in place
      10. [V] Start the Nexus service
      11. [V,H] check the nexus-gc.log for errors
      12. [H] check the functionality
      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

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                dhladky David Hladky
                Reporter:
                dhladky David Hladky
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: