Managing Jobs/Pipelines
Last updated
Last updated
A job or pipeline's config can be copied to a new job/pipeline. This will create a deep copy of the job or pipeline. Meaning any configuration changes to the new job or pipeline will not affect the original job/pipeline.
To copy a job open the More menu and press the copy button.
When a job is copied all config for the job will be copied to the new job. Meaning all the endpoints and manipulators will be copied to the new job. This is a deep copy so any manipulator config changes to the new job will not affect the original job.
When a pipeline is copied all config for the pipeline will be copied to the new pipeline. Meaning all the steps, with the jobs, and any start transaction options (such as overwrite job config).
Jobs and pipelines can either be active or not. An active job/pipeline is a job or pipeline that can be run. The activity status of a job/pipeline can be toggled to manage jobs and pipelines. The activity status can be used to "archive" older jobs or pipelines that are not longer necessary.
Jobs and pipelines can be filtered for active or inactive status. Simply press the button at the top of the page to change the filter.
A job or pipeline's activity status can be toggled. Open the "More" menu and press the "toggle activity" button.
This button is a toggle and can be used on an active or inactive job/pipeline. If a job or pipeline is currently active, the button will then make the job/pipeline inactive. If the job/pipeline is inactive, the button will then make the job/pipeline active.
