Pipelines

Pipelines

A pipeline is a definition of jobs that should be run in a particular order. Use the Configure | Pipelines menu to configure pipelines.

Field	Description
ID	An auto-generated ID used to identify the pipeline
Name	A name for the pipeline
Description	A description for the pipeline
Active	Whether the pipeline can run or not
Serial Jobs	A comma separated list of job ids that should be run in the order given. You can use all to specify that all jobs should be run. You can also specify jobs that use a given schedule by using the syntax schedule:<schedule name or id> e.g. schedule: daily. You can specify multiple schedules by separating them with ; e.g. schedule: daily;5. You can also use + after a job id to indicate running of all jobs from that id to the last e.g. 13+. You can also use - to specify job ranges e.g. 1-5. You can specify jobs whose report belongs to a certain report group by using the syntax reportGroup:<report group name or id> e.g. reportGroup: test. You can specify multiple report groups by separating them with ; e.g. reportGroup: test;admin. You can also use - before the job id or definition to identify jobs that should be excluded e.g. -5.
Continue On Error	For Serial jobs, whether the next jobs should be run if the current one encounters an error
Parallel Jobs	A comma separated list of job ids that can be run in parallel. The definition is similar to that for the serial jobs field.
Duration (Mins)	For Parallel jobs, the duration in minutes in which the jobs should run
End Time	For Parallel jobs, the time that the job runs should end. Will be applied if Duration is not set.
Per Minute	For Parallel jobs, the number of jobs to be run per minute. Will be applied if Duration and End Time fields are not set.
Schedule	A schedule on which the pipeline will run
Error Notification Email	An email address that should be notified if an error occurs while running the pipeline. Multiple email addresses can be specified separated by commas. The SMTP server used is that configured in the Settings page. Only a single email will be sent at the end of the pipeline containing all the errors of different jobs in the pipeline.