Uploaded image for project: 'OpenShift Jenkins'
  1. OpenShift Jenkins
  2. JKNS-260

Remove Jenkins from OCP Payload

XMLWordPrintable

    • Remove Jenkins from OCP Payload
    • True
    • False
    • Yellow
    • Done
    • Impediment
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      OpenShift Container Platform 4.11 moves the "OpenShift Jenkins" and "OpenShift Agent Base" images to the `ocp-tools-4` repository at `registry.redhat.io`. It also removes the "OpenShift Jenkins Maven" and "NodeJS Agent" images from its payload.
      Show
      OpenShift Container Platform 4.11 moves the "OpenShift Jenkins" and "OpenShift Agent Base" images to the `ocp-tools-4` repository at `registry.redhat.io`. It also removes the "OpenShift Jenkins Maven" and "NodeJS Agent" images from its payload.

      Goal

      Remove Jenkins from the OCP Payload.

      Problem

      • Jenkins images are "non-trival in size, impact experience around OCP payloads
      • Security advisories cannot be handled once, but against all actively supported OCP releases, adding to response time for handling said advisories
      • Some customers may now want to upgrade Jenkins as OCP upgrades (making this configurable is more ideal)

      Why is this important

      • This is an engineering motivated item to reduce costs so we have more cycles for strategic work
      • Aside from the team itself, top level OCP architects want this to reduce the image size, improve general OCP upgrade experience
      • Sends a mix message with respect to what is startegic CI/CI when Jenkins is baked into OCP, but Tekton/Pipelines is an add-on, day 2 install sort of thing

      Dependencies (internal and external)

      See epic linking - need alternative non payload image available to provide relatively seamless migration

       

      Also, the EP for this is approved and merged at https://github.com/openshift/enhancements/blob/master/enhancements/builds/remove-jenkins-payload.md

      Estimate (xs, s, m, l, xl, xxl):

      Questions:

             PARTIAL ANSWER ^^:  confirmed with Ben Parees in https://coreos.slack.com/archives/C014MHHKUSF/p1646683621293839 that EP merging is currently sufficient OCP "technical leadership" approval.

       

      Previous work

       

      Customers

      assuming none

            gmontero@redhat.com Gabe Montero
            adkaplan@redhat.com Adam Kaplan
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: