The Jenkins build is set up at https://shared-discovery-platform-jenkins.swg-devops.com:8443.
The following jobs are available:
nodelabel
parameter with value odfbuild
triggers the build on Linux.odftestenv
every night at 10PM EST.The parameter nodelabel
defines the nodes the test env is / should be installed:
odftestenv
for testing your private builds on https://sdp1.rtp.raleigh.ibm.com:58081/odf-web-0.1.0-SNAPSHOT.odfdemo
for the stable demo on https://odfdemo.rtp.raleigh.ibm.com:58081/odf-web-0.1.0-SNAPSHOT.Possible actions selectable through the action
parameter are:
start
: (re)start the test envstop
: stop the test envcleanconfig
: (re)starts with clean configuration and Kafka topicscleanmetadata
: (re)starts with clean metadatacleanall
: (re)starts with cleanconfig plus cleanmetadatainstall
: Installs the build as specified in the jenkinsjob
and buildnumber
parameters.You can find these jobs in Jenkins in the 1-ODF tab.
This Jenkins system currently contains two kinds of slaves which are distinguished by a so called node label.
We currently have these node labels:
odfbuild
: Linux buildodftestenv
: Machine sdp1.rtp.raleigh.ibm.com where test envs can be deployed regularly for internal testing.jenkinsbuild
. This is currently only used in the Bluemix Services and requires that the Bluemix password is not read from the cf.password
system property but rather from the env var CFPASSWORD
. This is only done so that the password doesn't appear in the log.smashlittletonfirewall.sh
(see below). You have to set the env var INTRANETCREDENTIALS
from Jenkins as a combined credential variable (of the form user:password). The reason why this is a script and not put into the command line directly is that the user / password don't appear in the logThe build slave machines are:
sdp1.rtp.raleigh.ibm.com
sdpbuild2.rtp.raleigh.ibm.com
sdpdemo.rtp.raleigh.ibm.com
sdpwin1.rtp.raleigh.ibm.com
Access user: ibmadmin / adm4sdp
These VMs can be managed through vLaunch.
On the windows slaves, install Git from IBM iRAM, e.g., here and make sure that the bin directory of the installation (typically something like C:\Program Files (x86)\Git\bin
) is in the path. This takes care that sh.exe
is in the path and picked up by the Jenkins jobs.
smashlittletonfirewall.sh
Used to smash the Littleton firewall. Put this somewhere in the path, e.g., ~/bin
. The reason why this exists at all is so that the intranet credentials don't appear in the build log. The file consists of this one line:
curl -i -L --user $INTRANETCREDENTIALS --insecure -X GET http://ips-rtc.swg.usma.ibm.com/jazz/web/projects