You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 40 Next »

Archiva Release Process

  1. Post to the dev list a few days before you plan to do an Archiva release
  2. Recreate the staging repository on VMBuild - make sure that it is not scanned (so that .index* is not created)
  3. If there are changes in the parent pom, release parent pom – https://svn.apache.org/repos/asf/archiva/parent
    • mvn release:prepare (verify that it has been properly tagged)
    • mvn release:perform (verify that it has been deployed correctly in the staging repo)
  4. Update the parent pom version of archiva – https://svn.apache.org/repos/asf/archiva/trunk
    • change the parent pom version to the archiva-parent version that has just been released
    • commit the changes made
  5. Update the release notes and the site.xml for version changes in archiva-docs
  6. Verify that the webapp-tests are building successfully. Since it is in a separate profile but inside the Archiva source tree, it will not be released but will still be included in the release tag. If some tests are failing, comment it out first so that only the passing tests are executed when the webapp-tests module are built from the tag.
  7. Release archiva
    • You should have a GPG agent running (preferred), and confirm it works by running "gpg -ab" (type some text and press Ctrl-D).
    • If you do not have a GPG agent running, make sure that you have the "apache-release" profile set in your settings.xml as shown below. 
      <profile>
  <id>apache-release</id>
  <properties>
    <gpg.passphrase>[GPG_PASSWORD]</gpg.passphrase>
  </properties>
</profile>
    • Set your user credentials for the stage repo in the <servers> section of your settings.xml for vmbuild.staging

    • Execute mvn release:prepare (check that it has been properly tagged. the tag name must be.. archiva-[VERSION])

    • Then execute mvn release:perform
  8. Download the uploaded files via wget: 
    ex.
wget http://vmbuild.apache.org/archiva/repository/staged-releases/org/apache/archiva/archiva-jetty/1.3/archiva-jetty-1.3-bin.tar.gz
  9. Verify the signatures: 
    ex.
gpg -v archiva-jetty-1.3-bin.zip.asc
  10. The documentation is deployed as part of the process to the final location for review in the vote: http://archiva.apache.org/docs/1.3/. If the vote doesn't pass, the documentation will need to be removed from the server for redeployment.
  11. Copy the sources and binaries from org/apache/archiva/archiva-jetty and org/apache/archiva/archiva to /www/people.apache.org/builds/archiva. They will need to be renamed to match conventions of previous releases. This can be done with the following script: 
    cd /www/people.apache.org/builds
svn cat http://svn.apache.org/repos/asf/archiva/project/release-script.sh > release-script.sh
sh release-script.sh VERSION STAGING_URL
  12. Call for a vote in the dev list and wait for 72 hrs. for the vote results. 3 binding votes are necessary for the release to be finalized. example
  13. If the vote fails or needs to be canceled, the version number should not be re-used if the version was made available for public download.
  14. After the vote has passed, copy the files from /www/people.apache.org/builds/archiva/ to /www/www.apache.org/dist/archiva
  15. Make sure the previous version was archived to /www/archive.apache.org/dist/archiva/ and then remove it from /www/www.apache.org/dist/archiva (the latter is synchronized with the mirrors and should only contain the last version).
  16. To sync the jars to ibiblio, execute: 
    mvn stage:copy -Dsource="http://vmbuild.apache.org/archiva/repository/staged-archiva"
     -Dtarget="scp://[APACHE_USERNAME]@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository" 
     -Dversion=1.3 -DrepositoryId=apache.releases
  17. mark the appropriate release version in JIRA as complete
  18. Update the archiva site (https://svn.apache.org/repos/asf/archiva/site/) for the versions and release notes URL and run mvn site-deploy. The 3 properties to change are at the bottom of pom.xml before generating the site.
  19. Remove old versions from /www/www.apache.org/dist/archiva
  20. Publish the reference docs (mvn site-deploy in the archiva-modules directory) from the release tag. You may have to exclude the archiva-webapp module to do this, and will require MAVEN_OPTS=-Xmx256m. You may need to use Maven 2.2.1 instead of Maven 3.x for this.
  21. Send out an announcement of the release to:
    • users@archiva.apache.org
    • users@maven.apache.org
    • announce@apache.org
  • No labels