...
As part of the Travis CI build, Javadocs are published to the gh-pages of the repository, available on the web here, once a successful builds. This is handled via the javadocsthe javadocs-ghpages.sh script that runs after the build. The script will attempt to collect all project javadocs and push them to the appropriate branch. In order for the push to succeed, an OAUTH token is made available to the script to do the job. The OAUTH token must be generated by a developer with push rights to the repo, and must be encrypted and placed inside the .travis.yml file under a "secure" heading.
...
As part of the Travis CI build, SNAPSHOT artifacts for all grouper modules listed in the settings.gradle file are published to the Sonatype snapshot repositories for Grouper once a successful builds. This is handled via the deploythe deploy-to-sonatype.sh script that runs after the build. The script will attempt will collect all JAR artifacts produced by the build and will attempt to publish them. The command that used by the script is:
...
| Info | ||
|---|---|---|
| ||
The script file must be massaged for every branch to tell Travis to limit the build to that branch only. |
Sonatype credentials can be encrypted for Travis via the following command:
| Code Block | ||
|---|---|---|
| ||
gem install travis
travis login --github-token <TOKEN>
travis encrypt SONATYPE_USER=yourUsername -r Internet2/groupertravis encrypt SONATYPE_PWD=yourPassword -r Internet2/Grouper |
- The TOKEN must be generated by you inside your Github profile settings.
- When the values are encrypted, they are printed back on the screen. Copy/paste them to the .travis.yml file under env/secure entry.