Versions Compared

Old Version 22

changes.mady.by.user Andrew Woods

Saved on

compared with

New Version 23

changes.mady.by.user Ralph O'Flinn

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Go to https://oss.sonatype.org/index.html  and log in (Nexus Repository Manager)
  • Click on Log In (Top Right Corner) and use your ossrh id from your settings.xml file

  • Click Staging Repositories in left navigation under Build Promotion which will open a new tab

  • Search for "vivoweb" in upper right search box (project will not have $REPO in title)

  • Select repository and verify that $REPO is present in the Content tab
    • Click Close, then Refresh, then Release

    This will publish the artifacts to the Sonatype releases repository and start the process of syncing them with Maven Central, which may take several hours. When finished, they'll be available at http://repo1.maven.org/maven2/org/vivoweb.

    Push Release Branch to develop and Maintenance

    The release branch has changes made since code freeze. It also contains the update to the version numbers for future development.

    Code Block
    git checkout rel-${CURR}-RC # this is your local copy of the release branch 
git log

    Ensure that your commit history matches the release branch's commit history, except for the two additional commits. 

    1. Changing from SNAPSHOT version to release version. Something like [maven-release-plugin] prepare release $REPO-$CURR
    2. Changing from release version to next development version. Something like [maven-release-plugin] prepare for next development iteration

    If this appears correct, you can push your release branch on to the maintenance branch.

    Push to Maintenance branch

    Code Block
    git push origin rel-${CURR}-RC:rel-${CURR[major.minor]}-maint

    Merge into 'develop' branch

      • Look for the correct types as well - war, pom, jar, md5, asc, etc.
        • Note there is sometimes a delay on larger files showing in the Repo.
    • Click Close, then Refresh, then Release
    • After a few moments click into the search under Artifact Search in the left navigation and type "vivoweb"
    • A new Search tab will appear with all of the org.vivoweb Release artifacts
    • Verify that the new release versions are now listed
      • Note there is sometimes a delay on larger files showing in the Repo.

    This will publish the artifacts to the Sonatype releases repository and start the process of syncing them with Maven Central, which may take several hours. When finished, they'll be available at http://repo1.maven.org/maven2/org/vivoweb.

    Push Release Branch to develop and Maintenance

    The release branch has changes made since code freeze. It also contains the update to the version numbers for future development.

    Code Block
    # this is to checkout your local copy of the release branch 
git checkout rel-${CURR}-RC
git log

    Ensure that your commit history matches the release branch's commit history, except for the two additional commits. 

    1. Changing from SNAPSHOT version to release version. Something like [maven-release-plugin] prepare release $REPO-$CURR
    2. Changing from release version to next development version. Something like [maven-release-plugin] prepare for next development iteration

    If this appears correct, you can push your release branch on to the maintenance branch.

    Push to Maintenance branch

    Code Block
    #For vivo, vitro, vivo languages, vitro languages, jenatools, and orcid-api-client
#Needs to be completed for each project in release
#Example orcid-api-client-0.6.3 would become rel-0.6-maint


git push origin rel-${CURR}-RC:rel-${CURR[major.minor]}-maint

    Merge into 'develop' branch

    Code Block
    #For vivo, vitro, vivo languages, vitro languages, jenatools, and orcid-api-client
#Needs to be completed for each project in release


git checkout develop
git pull
git checkout rel-${CURR}-RC
git rebase -i develop
git push origin develop

    Clean-up RC Tags

    Code Block
    git tag #view list of tags to verify it exists
git tag -d
    Code Block
    git checkout develop
git pull
git checkout rel-${CURR}-RC
git rebase -i develop-${RCNUM}
git push origin develop

    Clean-up RC Tags

    Code Block
    :refs/tags/rel-${CURR}-RC-${RCNUM}


#Examples

#For vivo, vitro, vivo languages, vitro languages
git tag #view list of tags to verify it exists
git tag -d rel-1.10.0-RC-1
git push origin :refs/tags/rel-1.10.0-RC-1

#For jenatools
git tag #view list of tags to verify it exists
git tag -d rel-1.2.0-RC-1
git push origin :refs/tags/rel-1.2.0-RC-1

#For orcid-api-client-0.6.3
git tag #view list of tags to verify
git tag -d rel-0.6.3-RC-1
git push origin :refs/tags/rel-0.6.3-RC-1

    ...