This document describes the process that should be followed to create a WebLogic Deploy Tooling (WDT) release.
settings.xmlfile, where the GitHub Personal Access Token is stored, as shown below. Note that this token can either be stored in plain text or encrypted using Maven password encryption.
<servers> <server> <id>github</id> <passphrase>store plain text or encrypted token here</passphrase> </server> </servers>
<proxies> <proxy> <active>true</active> <id>my-proxy</id> <protocol>http</protocol> <host>proxy server DNS name</host> <port>proxy server port</port> <nonProxyHosts>list of DNS names/patterns separated by |</nonProxyHosts> </proxy> </proxies>
The best practice is to write the release notes that will be published to GitHub prior to starting the steps below.
<WLS-install-dir>with the full path to the WLS 12.2.1.x installation directory.
weblogic-deploy-toolingproject directory, create a file called
release.propertieswith content similar to the example shown below. Note that the example is configured to cut the 1.9.11 release.
tag=release-1.9.11 releaseVersion=1.9.11 developmentVersion=1.9.12-SNAPSHOT
weblogic-deploy-toolingproject directory, run the
mvn -B release:prepare release:performcommand. If your SSH private key has a passphrase, watch the build closely because it will prompt for your passphrase multiple times. Failure to enter it in a timely manner may result in a failure.
mvn -B release:rollbackcommand to undo it and start over from Step 2., after correcting the issue.
Note that this process relies on the WDT installers being in your local Maven repository. As such, it is critical for the same user to run these steps on the same machine as the steps from the previous section!
mvn -f github-release.xml -DreleaseVersion=<release version number> verifyto create the draft GitHub Release.