Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-11342

Decrease the length of Proxy build time

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Envoy
    • Decrease the length of Proxy build time
    • False
    • Hide

      None

      Show
      None
    • False
    • In Progress
    • 50% To Do, 50% In Progress, 0% Done

      The goal of this EPIC is to decrease the build time of downstream Proxy product. Envoy (community) build itself takes too long. Addressing length of upstream build process is not a primary goal of this one, we would like to focus on the product build.
      This epic should serve also as a place to group all the issues that we are working on already towards this goal and should make our efforts more focused.

      Entire process looks like this:

      1. on PR build in envoy-openssl repo (could be 2 hours?)
      2. on PR build in ossm/proxy repo (2-4 hours, based on prow availability)
      3. on PR build pipeline of proxy-debug in Konflux (2h, but 10h for ossm 3.2)
      4. on push build pipeline of proxy-debug in Konflux (5h, 11h for ossm 3.2)
      5. on PR build for proxy in Konflux (up to 1h)
      6. on push build for proxy in Konlfux ( up to 1h)

      This summed up is from 13h to 29h. Steps 3 and 4 seem to be obvious candidates.

      Proxy builds make the process of the OSSM longer and builds sometimes tend to timeout which prolongs the whole process even more.

      One of the steps that this should include is describing the process as it is right now, in a document for example. This should give an overview to everybody, space to brainstorm and a good starting point.
      I'd say that from this we will identify areas that are worth investigating and figuring out if/how we can decrease the time.

      It seem like regarding proxy pipeline, we already hit the Konflux limits. If we want to speed thing up even more we would need to do it mostly on proxy engineering side. Also, proxy hits different Konflux bugs/issues than any other OSSM components, because of the build time. So what is relevant for proxy is often not relevant for other components.

              Unassigned Unassigned
              mmakovy@redhat.com Matus Makovy
              Zuzana Miklánková
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: