Uploaded image for project: 'OpenShift BuildConfig'
  1. OpenShift BuildConfig
  2. OCPBUILD-32

Disable Jenkins Pipeline by Default

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • Disable Jenkins Pipeline by Default
    • False
    • False
    • Done
    • 0
    • 0% 0%

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • Disable the JenkinsPipeline build strategy buy default
      • Ensure clusters that rely on the JenkinsPipeline build strategy can continue to do so.

      Why is this important?

      With the GA release of OpenShift Pipelines, we would like to decouple Jenkins from OpenShift. Requiring additional configuration to enable the JenkinsPipeline build strategy is a step in this direction. In the future this configuration option can be deprecated, thereby disabling the JenkinsPipeline build strategy for all clusters. Full deprecation and removal should be addressed in a separate enhancement proposal.

      Scenarios

      1. New clusters - JenkinsPipeline build is disabled by default.
      2. Existing clusters - on upgrade JenkinsPipeline builds are enabled if the cluster has an existing JenkinsPipeline BuildConfig or Build.
      3. Cluster admins can enable or disable the JenkinsPipeline build strategy manually.

      Acceptance Criteria

      • CI
        • On a default cluster, JenkinsPipeline builds fail to run
        • The existing Jenkins build suite is modified to enable the Jenkins pipeline build strategy before starting.
      • Telemetry indicates if the cluster has enabled the JenkinsPipeline build strategy
      • oc new-build/start-build issues a warning of the JenkinsPipeline strategy is referenced
      • Enablement - documentation updated related to JenkinsPipeline builds.

      Dependencies (internal and external)

      1. None

      Previous Work (Optional):

      1. None

      Open questions::

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

            Unassigned Unassigned
            adkaplan@redhat.com Adam Kaplan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: