Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: vrutkovs 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 |
d5bda27 to
d515a96
Compare
I think we should use coreos/coreos-assembler#730 The workaround for the fedora-release bug is here btw coreos/rpm-ostree@0d841b2#diff-4347e55ee672a63c1ae3a89e57fa78eeR14 |
Good idea, added as TODO |
|
It's built in the Anyways |
0b3dc2b to
6899cf0
Compare
|
@vrutkovs Are you still working on this? |
|
@cgwalters I am, I've got a few ideas to try tomorrow. Hopefully at least |
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.
…tall in sanity test
…master: use f30 in rpmostree for now
aac1176 to
b0b5db6
Compare
… install in raw_steps
3026840 to
609a5f9
Compare
6bbe86e to
90cd010
Compare
d2c82e6 to
ca92ba0
Compare
6f0c3be to
6545b3d
Compare
…master: build Dockerfile, then buildroot and run tests there
db48066 to
9304292
Compare
9304292 to
d9fe7fa
Compare
|
@vrutkovs: The following tests 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. |
|
I took the rpm-ostree part of this to #5263 |
|
@cgwalters: Closed this PR. DetailsIn response to this:
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. |
Experiment with building ostree in api.ci
build_rootimage (centos7 w/ golang installed) is used to clone the project as it has necessary user setostree-ciis using F30 imagestream as a base for the dockerfile, which builds the code and runs minimal checkssanitytest runs a simple command to verify the binary has been builtTODO:
ownerstest fails as it doesn't have OWNERS filled inconfigtest fails as the repos are not configured to have Prow triggersrpm-ostreebuild fails - wrong WORKDIR maybe?sanitytest fails duringmake installas its not running as rootmake cleanto rebuild the packageRequires: