Configure General and Advanced Job Settings

You can configure several general and advanced job settings, such as name and description, the Java version used in the build, discarding old and running concurrent builds, adding timestamps to the build log, and more:

Note:

If you're trying to access a renamed job by using a link from the activities feed (or from a bookmarked link), you will be unable to do so because that job no longer exists. A page with a message indicating that there was an error loading the Jobs page is displayed, along with some text that says that the job could not be found because it may have been deleted or renamed. Click the Take me back to Jobs button and the Builds page's Jobs tab will be displayed.

Action	How To
Rename the job or update its description	Open the job’s configuration page. Click Settings . Click the General tab. In Name and Description, update the job name and description. Click Save.
Check the software available on the job’s build executor template	Open the job’s configuration page. Click Settings . Click the Software tab. See the software and their versions. You can change versions of some software, such as Java SE. Select the version from the drop-down list. Click Save.
Run concurrent builds	Open the job’s configuration page. Click Settings . Click the General tab. Select the Execute concurrent builds if necessary check box. By default, only one build of a job runs at a time. The next build runs after the running build finishes. Click Save.
Set a quiet period	Open the job’s configuration page. Click Settings . Click the Advanced tab. Select the Quiet period check box and specify the amount of time (in seconds) a new scheduled build of the job will wait before it runs. If the build executor is busy with too many builds, setting a longer quiet period can reduce the number of builds. Click Save.
Set a retry count	Open the job’s configuration page. Click Settings . Click the Advanced tab. Select the Retry Count check box. In Build Retries specify the number of times the build executor tries the build. By default, the build executor tries five times to run a build that fails. You can increase or decrease the count. In SCM Retries specify the number of times the build executor tries the build to checkout files from the Git repository. You can increase or decrease the default count. Click Save.
Abort a build if it’s stuck for some duration	Open the job’s configuration page. Click Settings . Click the Advanced tab. Select the Abort the build if it is stuck check box. In Hours and Minutes, specify the duration. If a build doesn’t complete in the specified amount of time, the build is terminated automatically and marked as aborted. Select the Fail the build on abort check box to mark the build as failed, rather than aborted. Click Save.
Remove timestamps from the build log	Open the job’s configuration page. Click Settings . Click the Advanced tab. Deselect the Add Timestamps to the Console Output check box. By default, build logs are timestamped. This selection configures the job to remove them from the log. Click Save.
Set the maximum size of the console log	Open the job’s configuration page. Click Settings . Click the Advanced tab. In Max Log Size (MB), set the size. The default value is 50 MB and the maximum value is 1000 MB. Click Save.