Q: Why “automation server” and not “continuous integration …“?
A: Because Jenkins’ business is no longer just “continuous integration” but the very wide field of automation in general. Whatever you started before through a crontab entry, is so much more comfortable to start through a Jenkins job. Log files are being preserved (and purged automatically, if you want so), artefact as well, …
Jenkins starts all shell build steps using “-xe”, that’s like “set -x” and “set -e” within a shell script. “-xe” gets passed on to shell scripts called from within a shell build step — but you usually don’t want to show its internals and get the commands within your shell script displayed command by command — and there is a way to revert this effect: insert “/bin/bash +xe” before the call to the shell script!
Leave a Reply