Skip to content

Latest commit

 

History

History
29 lines (28 loc) · 1.91 KB

RELEASING.md

File metadata and controls

29 lines (28 loc) · 1.91 KB
Raw

These are the steps to release a gradle-based Jenkins plugin, assuming the release plugin isn't being used.

  • Ensure you have the latest code from origin: git pull origin
  • Make sure tests still run: ./gradlew test
  • Run locally to perform santity check: ./gradlew :job-dsl-plugin:server
  • Edit gradle.properties to strip -SNAPSHOT from version: vi gradle.properties
  • Set compatibleSinceVersion to the new version if deprecated features have been removed
  • Update the release notes, set the release date: * 1.14 (Mar 31 2013)
  • Update any references to the version in the documentation, e.g. in IDE-Support.md and Extending-the-DSL.md
  • Update any references to the version in the API viewer, e.g. in index.html
  • Ensure everything is checked in: git commit -am "Releasing 1.14"
  • Ensure you have your Jenkins credentials in ~/.jenkins-ci.org: cat ~/.jenkins-ci.org
userName=yourUsername
password=IHeartJenkins
  • Deploy: _./gradlew publish
  • Publish the docs: ./gradlew publishDocs
  • Tag the source as it is: git tag -a job-dsl-1.14 -m "Staging 1.14"
  • Increment the version in gradle.properties and append "-SNAPSHOT": echo "version=1.15-SNAPSHOT">gradle.properties
  • Update the release notes, add the next version: * 1.15 (unreleased)
  • Add the new snapshot version to the API viewer, e.g. in index.html
  • Commit the updated version number: git commit -am "Bumping to next rev"
  • Push the two new commit and the tag back to GitHub: git push --tags && git push
  • Close all resolved issues in JIRA
  • Open a pull request to update the Job DSL Playground
  • Open a pull request to update the Job DSL Gradle Example
  • Wait up to twelve hours for it show up in the Update Center
  • Follow the @jenkins_release twitter account and retweet the release!