Skip to main content

Defining Pipeline Conflicts

Abstract

Defining Pipeline Conflicts

This section contains a short guide on how to set pipeline conflicts.

This function is useful to include or exclude concurrent editing or executing pipelines by multiple users that are active in the system.

For each pipeline you can specify a list of conflicting pipelines, including the current pipeline itself.

Example

A user is editing pipeline A and defines pipelines B and C in the conflict list.

  • In that case if the user wants to start pipeline A, it will wait (in running state) till the end of the executions of the pipelines B and C. Only then it will be executed.

  • If a user sets pipeline A to conflict with pipeline A it means that only one instance of the pipeline A is able to run at one given moment.

  • In case of several instances being launched at the same time, they will be executed one after another.

Setting Pipelines Conflicts
  1. Click Conflicts at the bottom of the canvas.

  2. The Pipeline Conflicts dialogue opens.

  3. In the column All Pipelines select one or more pipelines you want to define conflicts with the current one for. Multi-select is possible.

  4. Use the arrows to add or remove the selected pipelines to or from the column on the right: Pipelines conflicting with the current pipeline

    • In the column on the right the pipelines you selected, will be listed.

  5. Click OK to confirm your changes.

    • Click Cancel to abort.

    • Click Clear Conflicts to remove all pipelines from the column on the right.