WIP: Add ostreedev/ostree and projectatomic/rpm-ostree#4880
WIP: Add ostreedev/ostree and projectatomic/rpm-ostree#4880cgwalters wants to merge 1 commit intoopenshift:masterfrom
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: cgwalters The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
I think we need to add the Prow webhooks to the repository as well, will look at that. |
Currently, these projects are using [PAPR](https://github.com/projectatomic/papr/) which today uses RHT-internal OpenStack which has reliability problems. There's no reason not for us to add some usage of Prow as an additional CI context; all we're doing is a build, no tests. I am strongly considering switching to Prow as a "merge bot" too, i.e. using `/lgtm` etc. But this is just a first step.
0cdd83a to
c6c0a2d
Compare
|
Current status is Something in the ci-operator high levle seems to be expecting golang? |
|
@cgwalters: The following test failed, say
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. DetailsInstructions 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. |
|
Oh no wait I see, it's trying to run in the context of cosa but it doesn't have the |
|
OK, I created coreos/coreos-assembler#730 which fixes that. And I built it in a new So the next blocker there is https://github.com/openshift/release/issues/4892 |
Could this script connect to CentOS CI and start the pipeline there instead of running in on api.ci? This way we'll get prow integration and |
https://github.com/openshift/release/issues/4892 |
|
Closing this in favor of #4900 |
Currently, these projects are using PAPR
which today uses RHT-internal OpenStack which has reliability problems.
There's no reason not for us to add some usage of Prow as an additional
CI context; all we're doing is a build, no tests.
I am strongly considering switching to Prow as a "merge bot" too,
i.e. using
/lgtmetc. But this is just a first step.