Skip to content
[Jenkins]Jenkins
log in
Status
Changes

californium-release

Create a new release from a given branch for Californium project.
  • Checks out ${BRANCH}
  • bumps POMs to ${RELEASE_VERSION}
  • builds and tests it
  • tags it with ${RELEASE_VERSION}
  • bumps POMs to ${NEXT_VERSION}
  • pushes POMs and newly created tag to GitHub
In order to deploy the release version, you need to trigger any or both of the following build jobs:
  • parent-deploy-eclipse
  • parent-deploy-maven-central
To deploy a 2.7 release version, you need to trigger any or both of the following build jobs:
  • parent-deploy-eclipse-2.7
  • parent-deploy-maven-central-2.7

Note:
This job creates commits and pushs them to the github repository.
Therefore "Git -> Additional Behaviours -> Check out to specific local branch" is required!

Note:
After releasing Californium usually Californium.Actinium and Californium.Tools are released.
In order to be able to set the version of these projects after the release also to the next SNAPSHOT,
it's required to build the next Californium SNAPSHOT running "californium-main-nightly".
In some cases, if this is executed "too fast" after the release, revapi seems to fail to load that
last release and so reports quite a lot "external API changes". Therefore it's a good idea to edit
the READMEs and other textfile and commit them before starting the "californium-main-nightly" job.
With that pause, the next SNAPSHOT should build without errors. And afterwards, Californium.Actinium
and Californium.Tools may be released.

Permalinks