Skip to content

Latest commit

 

History

History
31 lines (29 loc) · 1.49 KB

CONTRIBUTING.md

File metadata and controls

31 lines (29 loc) · 1.49 KB
Raw

Contributing

Contribution Rules

  1. No SNAPSHOT dependencies on "develop" and obviously "master" branches

Releasing

  1. From the develop branch, prepare a release (example using a HTTP proxy):

    $ mvn -Dhttps.proxyHost=proxyhostname -Dhttps.proxyPort=8080 jgitflow:release-start
  1. Update the CHANGELOG according to keepachangelog.com.
  2. To perform the release (example using a HTTP proxy):

    $ mvn -Dhttps.proxyHost=proxyhostname -Dhttps.proxyPort=8080 jgitflow:release-finish

If, after deployment, the command does not succeed because of some issue with the branches. Fix the issue, then re-run the same command but with 'noDeploy' option set to true to avoid re-deployment:


    $ mvn -Dhttps.proxyHost=proxyhostname -Dhttps.proxyPort=8080 -DnoDeploy=true jgitflow:release-finish
  1. Connect and log in to the OSS Nexus Repository Manager: https://oss.sonatype.org/
  2. Go to Staging Profiles and select the pending repository authzforce-*... you just uploaded with jgitflow:release-finish
  3. Click the Release button to release to Maven Central.
  4. Build and publish the Docker image to Docker Hub (version is the last release version): 
    $ git checkout release-${version} 
$ cd  pdp-server
$ docker build -t authzforce/authzen-pdp:latest -t authzforce/authzen-pdp:${version} .
$ docker login
$ docker push authzforce/authzen-pdp:${version}

More info on jgitflow: http://jgitflow.bitbucket.org/