Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-6910

Enable Cluster-Wide Cancel-In-Progress Configuration

XMLWordPrintable

    • 8
    • False
    • None
    • False
    • KONFLUX-134 - Cancel PipelineRuns on PR update
    • Hide
      Administrators can now enable cancel-in-progress functionality cluster-wide using the Pipelines-as-Code ConfigMap. This enhancement allows global control of the cancel-in-progress behavior, ensuring consistent pipeline management across the cluster while reducing the need for individual annotations.
      Show
      Administrators can now enable cancel-in-progress functionality cluster-wide using the Pipelines-as-Code ConfigMap. This enhancement allows global control of the cancel-in-progress behavior, ensuring consistent pipeline management across the cluster while reducing the need for individual annotations.

      Description: Building on the existing pipelinesascode.tekton.dev/cancel-in-progress: "true" annotation functionality, this feature introduces a cluster-wide configuration option for cancel-in-progress. Administrators can now configure the cancel-in-progress behavior globally through the Pipelines-as-Code ConfigMap.

      Proposed Functionality:

      1. Global Configuration: Add a field in the Pipelines-as-Code ConfigMap to enable cancel-in-progress globally across all PipelineRuns by default.
      1. Annotation Override: Allow individual PipelineRuns to override the global setting by explicitly setting the pipelinesascode.tekton.dev/cancel-in-progress annotation to "false" or "true".
      1. Backward Compatibility: Ensure that existing behavior is preserved for clusters that do not enable this global configuration.

      Benefits:

      • Provides administrators with centralized control over cancel-in-progress settings.
      • Reduces the need for individual developers to manually add the annotation.
      • Ensures consistent resource management policies across the cluster.

      Acceptance Criteria:

      1. A new field in the Pipelines-as-Code ConfigMap allows enabling global cancel-in-progress by default.
      1. Users can disable the global setting on specific PipelineRuns using annotations.
      1. Comprehensive testing to validate both global and local behaviors.
      1. Backward compatibility is maintained for clusters without global configuration.

      Dependencies:

      • Pipelines-as-Code ConfigMap.
      • Existing cancel-in-progress annotation functionality.

              cboudjna@redhat.com Chmouel Boudjnah
              cboudjna@redhat.com Chmouel Boudjnah
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: