Add jobs to build FCOS forks of MCD and installer

[vrutkovs]

Build installer and MCD from fcos branch and promote these to fcos namespace

Supersedes #5557 and #5589

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vrutkovs
To complete the pull request process, please assign crawford, lorbuschris
You can assign the PR to them by writing /assign @crawford @lorbuschris in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/installer/OWNERS
• ci-operator/config/openshift/machine-config-operator/OWNERS
• ci-operator/jobs/openshift/installer/OWNERS
• ci-operator/jobs/openshift/machine-config-operator/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[LorbusChris]

In openshift-machine-config-operator-fcos.yaml we'll need an RPM build job analogous to #5572, stick that into an fcos-artifacts container and and get the bins from there to layer onto our FCOS ostree content to make an FCOS machine-os-content. Am I missing something?

[LorbusChris]

I was able to create an fcos branch on the MCO repo, but I don't have permissions to do that on the Installer's.

[vrutkovs]

In openshift-machine-config-operator-fcos.yaml we'll need an RPM build job analogous to #5572, stick that into an fcos-artifacts container and and get the bins from there to layer onto our FCOS ostree content to make an FCOS machine-os-content. Am I missing something?

Eventually, yes, however this setup has been tested with el7 binaries so I'd rather stick to those for now so that rehearse tests would pass before we move further

[LorbusChris]

To clarify, what I meant with fcos-artifacts is they come from the fcos branches instead of master. That's why we will need a separate container for those artifacts (regardless of their buildroot).

[openshift-ci-robot]

@vrutkovs: The following tests failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
ci/prow/correctly-sharded-config	6fa903c	link	/test correctly-sharded-config
ci/rehearse/openshift/machine-config-operator/fcos/e2e-aws	6fa903c	link	/test pj-rehearse
ci/rehearse/openshift/installer/fcos/verify-vendor	6fa903c	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/fcos/unit	6fa903c	link	/test pj-rehearse
ci/rehearse/openshift/installer/fcos/govet	6fa903c	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/fcos/images	6fa903c	link	/test pj-rehearse
ci/rehearse/openshift/installer/fcos/e2e-aws	6fa903c	link	/test pj-rehearse
ci/rehearse/openshift/installer/fcos/images	6fa903c	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/fcos/verify	6fa903c	link	/test pj-rehearse
ci/rehearse/openshift/installer/fcos/unit	6fa903c	link	/test pj-rehearse
ci/rehearse/openshift/installer/fcos/gofmt	6fa903c	link	/test pj-rehearse
ci/rehearse/openshift/installer/fcos/golint	6fa903c	link	/test pj-rehearse
ci/prow/pj-rehearse	6fa903c	link	/test pj-rehearse

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.