+1

Clicking re-run on the c3i-jenkins build, it passed: https://jenkins-waiverdb-test.cloud.paas.upshift.redhat.com/blue/organizations/jenkins/waiverdb-test%2Fwaiverdb-test-waiverdb-dev/detail/waiverdb-test-waiverdb-dev/42/pipeline That's good. It was just a temporary failure before.

This changes the standard workflow for how images will get to the :latest tag and therefore how they will get to the internal dev and staging environments. @gnaponie, @lholecek - do you two know how that's going to work after this is merged? It's important to know so we can debug it while trying to get a fix to production.

This changes the standard workflow for how images will get to the :latest tag and therefore how they will get to the internal dev and staging environments. @gnaponie, @lholecek - do you two know how that's going to work after this is merged? It's important to know so we can debug it while trying to get a fix to production.

Yes, it's awesome. On Friday I can just click Start Pipeline next to "stage-waiverdb-promoting-to-prod" and go home.

+1

I'll also be watching the pipeline builds to see if they are stable enough.

Is Pagure outage again? https://jenkins-waiverdb-test.cloud.paas.upshift.redhat.com/job/waiverdb-test/job/waiverdb-test-waiverdb-dev/59/console failed with doc push error fatal: protocol error: bad line length character: No s. I checked rcm-tools-jenkins, the same error message there (https://rcm-tools-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/waiverdb/538/console). It seems to me the deploy key doesn't work again.

Commit 950d9fb4 fixes this pull-request