Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-2996

If push-latest-container fails to resolve iib, try again in 5 mins

XMLWordPrintable

    • False
    • None
    • False

      Sometimes the IIB build takes longer than we'd like, which means https://main-jenkins-csb-crwqe.apps.ocp-c1.prod.psi.redhat.com/job/CRW_CI/job/push-latest-container-to-quay_3.x/ will fail doing:

      cd /tmp
      curl -sSLO https://raw.githubusercontent.com/redhat-developer/devspaces/devspaces-3-rhel-8/product/getLatestIIBs.sh && chmod +x getLatestIIBs.sh
      results=$(./getLatestIIBs.sh --ds -t 3.1 -i registry-proxy.engineering.redhat.com/rh-osbs/devspaces-operator-bundle:3.1-63)
      echo "$results" | sed -r -e 's#registry-proxy.engineering.redhat.com/rh-osbs/devspaces-operator-bundle:3.1-63\t+##' -e 's#(.+)\t(.+)#\1 (\2)#'
      

      But if you try it 30 mins later, it passes.

      So... we could try this check several times over 30 mins (perhaps every 3 or 5 mins?) and keep trying until the timeout hits (job fails) or we find what we are looking for (job succeeds).

      Job code is here:

      https://gitlab.cee.redhat.com/codeready-workspaces/crw-jenkins/-/blob/master/jobs/CRW_CI/push-latest-container-to-quay_3.x.jenkinsfile#L248-265

      Some failures to demonstrate how often this happens before the fix:

        1. screenshot-1.png
          70 kB
          Nick Boldt
        2. screenshot-2.png
          46 kB
          Nick Boldt

            nickboldt Nick Boldt
            nickboldt Nick Boldt
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: