Quick start

For a normal commit: Just push to the master branch, wait about 10 minutes and check Travis (https://travis-ci.com/Internet2/grouper) for a successful build

...

• Tag the desired commit with string GROUPER_RELEASE_a.b.c (a, b, c are numbers)
• Check Travis (https://travis-ci.com/Internet2/grouper) in about 20 minutes to check for successful build and upload to Sonatype
• Log into Sonatype (https://oss.sonatype.org/) (as of Feb 2020 this is a shared password), find the current artifact set among the staging repositories
• Promote the directory from closed to release
• Confirm current version of artifacts appear in Sonatype releases (https://oss.sonatype.org/#nexus-search;quick~grouper-parent)
• wait a few hours, then confirm they were propagated to the Maven repositories (e.g. https://search.maven.org/artifact/edu.internet2.middleware.grouper/grouper-parentand release the artifacts from holding (see this page for details)

Detailed Description

Grouper is configured against Travis CI to execute the full build on every commit. For tags matching a specific pattern of "GROUPER_RELEASE_a.b.c(rc#)" it will also build release artifacts using that version from the tag, and publish those artifacts to the Maven Sonatype repository. There is an Internet2/Grouper account in Travis connected to the Grouper Github repository, and you (?) should have access to view the Travis build status if you have developer access in Github (CR Feb/2020 not sure about this). .

...

If successful, the artifacts will appear in a new folder in our Sonatype staging repository (https://oss.sonatype.org/), Currently (Feb 2020), there is a shared account to access this repository. A subfolder will appear with a name such as "eduinternet2middlewaregrouper-####". The status should be "closed", indicating that Travis was able to finalize its upload of the artifacts. In this state, the repository can be tested as a private repository, by adding it as a profile in maven settings.xml (see below), or it can be promoted to "release" which will publish it in the public repository. After being released, the artifacts will eventually be propagated to other Maven repository sites, such as https://search.maven.org/ and https://mvnrepository.com/.

Testing the staging repository before release

This step will not be needed often, but can be useful when verifying jar files before they are irrevocably published. For this, add to ~/.m2/settings.xml

...

...

/

...

Then, when running maven commands, include parameter `-P grouper-stage` to activate the profile. Maven downloads will then use this location as an additional download source.

Notes on encrypting values for Travis

...