JenkinsPipeline

This is a pipeline for build a jobs on command line.

Authentication

By default, this script authenticates with SSH key pair.

SSH key pair

Locating an existing SSH key pair

Before generating a new SSH key check if your system already has one at the default location by opening a shell and running the following command:

GNU/Linux / macOS / PowerShell:

cat ~/.ssh/id_rsa.pub

If you see a string starting with ssh-rsa you already have an SSH key pair and you can skip the next step Generating a new SSH key pair and continue onto Copying your public SSH key to the clipboard. If you don't see the string or would like to generate a SSH key pair with a custom name continue onto the next step.

Generating a new SSH key pair

GNU/Linux / macOS:

ssh-keygen -t rsa

Last step, paste the ssh public key into the SSH keys section at http://YOUR_JENKINS_HOSTNAME/user/YOUR_USERNAME/configure

Now you can go to next step Usage

Credentials

Alternatively you can log in using username and password. Follow the commands:

./jenkins -u USER_NAME -p PASSWORD

Now you can go to next step Usage

Usage

To run the script, the syntax is:

./jenkins

You can specified something parameters

usage: ./jenkins [options...]

valid options are:

-u  Username jenkins. Use with -p
-p  Password of the user jenkins. Use with -u
-h  help :)
-k  Jenkins parameter name. Use with -v
-v  Jenkins parameter value. Use with -k
-s  To specify jenkins URL. (We recommend edit script e change the var JENKINS_SERVER_URL)

When -u or -p is not specified, the script use ssh public key

Troubleshooting

While execution of script, you can received the error below:

Error #1

hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A

This is probably a result of hudson.diyChunking.

Check if diyChunking is enabled via the Script Console (JENKINS_URL/script) by running:

println System.getProperty("hudson.diyChunking")

If Result = true then read on.

You can disable diyChunking on the master by adding the Jenkins startup arg: -Dhudson.diyChunking=false. See How to add Java arguments to Jenkins if you need help.

Edit Jenkins startup arg

vim /etc/rc.d/init.d/jenkins

Edit the line:

JAVA_CMD="$JENKINS_JAVA_CMD $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME -jar -Dhudson.diyChunking=false $JENKINS_WAR"

Restart jenkins service

service jenkins restart

References: https://support.cloudbees.com/hc/en-us/articles/226235268-Jenkins-CLI-returns-invalid-stream-header-

Error #2

ERROR: No such job 'JOBNAME'

I had the same behavior and found out that allowing anonymous read access in the global security section fixed it. It is still mandatory to specify --username and --password to access the resource.

References: https://stackoverflow.com/questions/30066657/jenkins-cant-found-the-job-when-build-job-why

Error #3

[WARN] Failed to authenticate with your SSH keys. Proceeding as anonymous

ERROR: anonymous is missing the Job/ExtendedRead permission

If you have used PuttyGen to generate your keys, you will have to convert them to openssh format. Otherwise Jenkins might silently ignore your keys and you will be Authenticated as: anonymous.
Check if you paste the ssh public key into the SSH keys section at http://YOUR_JENKINS_HOSTNAME/user/YOUR_USERNAME/configure

If you ssh public key section is empty, jenkins you will be Authenticated as: anonymous.

Author

Rondinelli Morais, rondinellimorais@gmail.com

rondinellimorais/JenkinsPipeline