Here are some miscelaneous tips for Jenkins.

suppressing shell debug output [edit section]

Jenkins normally starts the shell to invoke a Fuego script by taking the contents of the "Execute shell" command text box, putting it in a temporary file, and executing it with "/bin/sh -xe /tmp/hudson..." This makes it so that the shell echos every command it sees while it's executing. In order to prevent this, you can specify the shell to run yourself.

If the command text box contents has a first line that starts with #!, then Jenkins will just execute that directly (instead of through its own shell invocation. This means you can get rid of the -x parameter to the shell by prefacing your text box contents with:

#!/bin/sh -e
<rest of contents here>

From Sami Tikka

If the first line of a shell build step starts with hashbang (#!),
then Jenkins will simply drop the script as is into a tmp file and
execute it.

Otherwise Jenkins copies the script into a tmp file and executes it
using /bin/sh -xe /tmp/somefilename

And /bin/sh, is just the shell used by Jenkins by default. You can
change the default under Manage Jenkins -> Configure System.

Jenkins supports matrix jobs [edit section]

Jenkins can run a matrix of jobs (where parameters are changed for each instance of what is essentially the same job). This is called a multi-configuration job.