Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-1856 Extend CI Framework to support dev/CI/QE use cases
  3. OSPRH-1652

[Content provider] Include operator's depends-on pr merged into account while building meta operator

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • ?
    • ?

      The content provider job running against install_yamls, meta-operator and edpm-ansible builds the meta operator images only.

      If there is a depends-on pr from non-meta operator, in that case it will first builds the non-meta operator image then bump the sha1 of non-meta operator pr in meta operator go.mod file and then builds the meta operator image.

      When the non-meta operator pr is merged, in that case, the meta-operator go.mod file does not get bump with the sha1 of non-meta operator. The non-meta operator fix is ignored. It causes a failure in our CI testing.

      Discussion Thread: https://redhat-internal.slack.com/archives/C04F192QB37/p1688614002598699

      Solution

      If a pr is proposed against install_yamls and meta-operator and there is no depends-on from other projects (existing depends-on got merged).
      Then we can check the meta operator /apis/go.mod file and compare the sha1 of each operator master branch. If it does not matches then update the sha1 in gomod file for each of them and then build the meta operator.

       

      OR

      Add a functionality in build-operators role to build all the operators.

              Unassigned Unassigned
              rhn-engineering-chkumar Chandan Kumar
              rhos-dfg-ci-framework
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: