Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 121
Release
These are instructions on the various steps necessary to cut out a new release of the Splunk SDK for Java. Even though the instructions are public, these steps are only meant to be taken by the SDK maintainers.
- Read through all of these release instructions.
- Update the version numbers in this document to the version you're about to release.
- Update any steps if necessary.
- For updates that could apply to other SDKs as well, update the release instructions page for every other SDK.
- Update changelog.
Create release branch off of develop (
release/1.8.0).git checkout developgit pullgit checkout -b release/1.8.0
Update the version number:
- Update the version property in the all
pom.xmlfile in the root directory. - Update the
User-Agentfield of theHttpServiceclass. - Update
README.md. - Update the line
declare -r version="??"in deploy. - Update the version everywhere in
deploy.md.
- Update the version property in the all
Make sure the version number change didn't break anything:
- Push the release/1.8.0 branch.
- Wait for Github Actions to run tests against the release/1.8.0 branch.
Send PR from release/1.8.0 to master; after approval then merge PR
Sanity check that the released version works (clone SDK afresh, build).
git clone git@github.com:splunk/splunk-sdk-java.gitcd splunk-sdk-javagit checkout mastermvn package
Start release using github
releases-> draft a new releaseBuild a new JAR and ZIP of the SDK:
- Make sure the JAR is built with JDK 8.
- Download the ZIP from the GitHub releases page.
- Make sure the file names reflect the current version (for example,
splunk-sdk-java-1.8.0.zip, splunk-1.8.0.jar).
Deploy to ArtifactoryOnline
- This is now automated in Github Actions
- Verify the contents of https://splunk.jfrog.io/artifactory/ext-releases-local/com/splunk/splunk/. See deploy.md for guidance.
Work with Docs team to:
- Post ZIP (download from github release page) and JAR (need to build on your local machine generated at /dist folder) files.
- Create both MD5 and SHA-512 hashes from final ZIP download. Docs will contact the Web team to upload these files.
- Update Readme. For point releases, the version number needs to be updated at a minimum.
- Update Dev Portal and push. For point releases, the "What's new" page and download links need to be updated at the very least.
- Publish the API Reference (docs.splunk.com/Documentation/SDK).
Verify the posted JAR:
- Download the JAR and make sure the checksum matches the original file.
Hand off to marketing to announce. See next section.
Hurrah, the new release is basically done! You can now announce it on the following channels:
- Twitter (@splunkdev, maybe @splunk)
- Google Groups (splunkdev)
- Dev Portal (http://dev.splunk.com)
- Dev Blog (http://blogs.splunk.com/dev)