Add a job to promote installer from fcos-master branch

[vrutkovs]

Build installer from fcos-master branch and promote it to fcos namespace

[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
You can assign the PR to them by writing /assign @crawford 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/jobs/openshift/installer/OWNERS

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

[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	863f203	link	/test correctly-sharded-config
ci/rehearse/openshift/installer/fcos-master/verify-vendor	863f203	link	/test pj-rehearse
ci/rehearse/openshift/installer/fcos-master/gofmt	863f203	link	/test pj-rehearse
ci/rehearse/openshift/installer/fcos-master/golint	863f203	link	/test pj-rehearse
ci/rehearse/openshift/installer/fcos-master/govet	863f203	link	/test pj-rehearse
ci/rehearse/openshift/installer/fcos-master/e2e-aws	863f203	link	/test pj-rehearse
ci/rehearse/openshift/installer/fcos-master/unit	863f203	link	/test pj-rehearse
ci/rehearse/openshift/installer/fcos-master/images	863f203	link	/test pj-rehearse
ci/prow/pj-rehearse	863f203	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.

[vrutkovs]

/cc @LorbusChris @smarterclayton

[smarterclayton]

Did you reverse the branch names? I would just use "fcos" instead of "fcos-master", since we have no other branches at this point.

[vrutkovs]

Did you reverse the branch names? I would just use "fcos" instead of "fcos-master", since we have no other branches at this point.

I don't have permissions to create branches there so I asked you to create those a few days ago :) I don't mind renaming these to fcos, that would allow us to drop openshift/ci-tools#237