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

Use CPaaS to build our proxy dependencies

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Obsolete
    • Icon: Undefined Undefined
    • None
    • None
    • Envoy

      We currently have a bunch of build dependencies that we need in order to produce proxy builds and which we have to build and manage ourselves. We should include those builds in CPaaS to make it easier for the team to track them and update their versions as required.

      Relevant packages are (probably incomplete?):

      • bazel
      • ninja-build
      • binaryen
      • emsdk
      • gn

      Acceptance Criteria:

      • add all build deps that we manage to our CPaaS instance, possibly on their own branch, with a separate build pipeline (as they need to be already present when running the main pipeline)
      • update CPaaS setup document

              ovanders@redhat.com Otto van der Schaaf (Inactive)
              dgrimm@redhat.com Daniel Grimm
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: