eclipselink-promote-2.7

EclipseLink 2.7 promotion job
Artifacts publishing/promotion job. Uploads artifacts into Jakarta OSS Sonatype staging repository https://jakarta.oss.sonatype.org/service/local/staging/deploy/maven2. It updates milestone download directories too.
Jakarta OSS Sonatype server requires binary, source and javadoc archive per artifact.
Job parameters:
GIT_REPOSITORY_URL - location of EclipseLink sources current URL is https://github.com/eclipse-ee4j/eclipselink.git . Job fetch project sources from there.
GIT_BRANCH - which git branch will be released same usually same as MAJOR_VERSION
RELEASE - relase switch. false - promote RC (release candidate) true - promote final version
release candidate is based on some nightly build, final version is usually based on the same nigtly build like latest release candidate
MAJOR_VERSION - EclipseLink major version like 2.6 , 2.7 , 3.0 usually same as git GIT_BRANCH
VERSION - EclipseLink release version. Must match with first part of NIGHTLY_BUILD_ID parameter. Typical value is for example 3.0.0, 2.7.5, 2.6.8.
NIGHTLY_BUILD_ID - nightly build ID in following form ".v-" . For example - 2.7.5.v20190614-4681d7f571
RELEASE_CANDIDATE_ID - typical values are: RC1, RC2....
SIGN - sing content of promoted jar files true - sign false - don't sign Standard gpg signing is allways applied. But this switch means, that content of the promoted/published jar file (any class or resource file) will be signed and result will be stored in META-INF/(ECLIPSE_.RSA, ECLIPSE_.SF, MANIFEST.MF) files. It will increase security, but it could decrease performance. Signed content can leads into troubles with integration into TopLink.
DEBUG - show debug messages in the STDOUT