jenkins console -x JOBNAME or jenkins console --exit-code JOBNAME could return a (non)-zero exit code depending on whether the job failed or not.
This will allow people to include the jenkins tool in their workflow and decide differently based on the job status, e.g.
if jenkins console -i -x myjob; then
echo "Hurray"
else
echo -e "Subject: Something went wrong \n\n with our job. please help" | sendmail problem@example.com
fi
I know this is already kind-of possible by greeping for SUCCESS or FAIL in the console output, but that's not reliable. Moreover a simple CLI switch looks more elegant and is less prone to typos.
The jenkins info subcommand could use the same switch too.
jenkins console -x JOBNAMEorjenkins console --exit-code JOBNAMEcould return a (non)-zero exit code depending on whether the job failed or not.This will allow people to include the jenkins tool in their workflow and decide differently based on the job status, e.g.
I know this is already kind-of possible by greeping for SUCCESS or FAIL in the console output, but that's not reliable. Moreover a simple CLI switch looks more elegant and is less prone to typos.
The
jenkins infosubcommand could use the same switch too.