Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-2690

Build: Automate updating quay-operator operator manifests in dist-git from upstream github

XMLWordPrintable

    • Upstream
    • False
    • False

      OSBS provides certain capabilities to support updating operator manifests. Explore some of these options:

      1. Using render_templates - https://cpaas.pages.redhat.com/documentation/schema/product/builds/brew_operator.html
      2. Pinning operator - https://osbs.readthedocs.io/en/latest/admins.html#operator-manifests
      3. https://osbs.readthedocs.io/en/latest/users.html#pullspec-locations

      Acceptance criteria

      • No manual steps are needed for building a z or y-stream for the first time (see related gchat for context)
        • this relates to related to dist-git or gerrit repos, AFAIK we'll still need to manually update the product.yaml in gitlab with the correct product version
      • All version pointers in the operator manifests in dist-git are updated to the next product version (based on CPaaS env vars, see related docs for details) after build-pipeline jenkins build runs.
        • note: gerrit distgit directory is unaffected
      • All operator CSVs related images (in gerrit distgit dir) use the "latest" tag. The render_templates (or other similar solution) updates the tag according to the version being built. This is needed for the check-patch job, see the related CPaaS issue for details

            doconnor@redhat.com Dave O'Connor
            hgovinda Harish Govindarajulu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: