keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
1dc7503838
rpm-ostree/ci/prow/Dockerfile

20 lines
771 B
Docker
Raw Normal View History

ci/prow: Install in target cosa, also install and run our tests This is a major downside of reworking and generating new CI flows, it's super easy to lose testing what you intend to. Also, we clearly need to figure out a flow where this is shared across repos, since I don't want to copy-paste this into e.g. ostree too. That's https://github.com/coreos/fedora-coreos-tracker/issues/263
2021-02-25 20:33:14 +03:00
FROM registry.ci.openshift.org/coreos/cosa-buildroot:latest as builder
ci: Add prow Dockerfile This is an exact copy of https://github.com/ostreedev/ostree/pull/1906 for now. From that commit message: I'd like to add OpenShift's prow to this repository. Let's start by adding a Dockerfile - it doesn't really do anything besides build. However...I've lately been thinking about e.g. shipping the ostree tests as an image, and then e.g. we could test FCOS by running that container (which would orchestrate the host's ostree). Anyways, not doing that right now but this is a start.
2019-08-28 23:07:30 +03:00
WORKDIR /src
COPY . .
ci: Add Prow e2e testing Our "CoreOS CI Jenkins" flow is great, but the reliability/debuggabilty of the system isn't the best. This is an experient to *add* another CI flow that can be run in Prow too. I'd like to at least have a basic e2e (compose tree, run client tests) flow that can operate in Prow so that if CoreOS CI Jenkins is down or flaky, we at least have some confidence in our commits. Longer term I think we can figure out how to better share CI flows across these: https://github.com/coreos/fedora-coreos-tracker/issues/263#issuecomment-772903759
2021-02-17 17:54:21 +03:00
RUN ./ci/build.sh && make install DESTDIR=/cosa/component-install
ci/prow: Install in target cosa, also install and run our tests This is a major downside of reworking and generating new CI flows, it's super easy to lose testing what you intend to. Also, we clearly need to figure out a flow where this is shared across repos, since I don't want to copy-paste this into e.g. ostree too. That's https://github.com/coreos/fedora-coreos-tracker/issues/263
2021-02-25 20:33:14 +03:00
RUN make -C tests/kolainst install DESTDIR=/cosa/component-tests
ci: Add Prow e2e testing Our "CoreOS CI Jenkins" flow is great, but the reliability/debuggabilty of the system isn't the best. This is an experient to *add* another CI flow that can be run in Prow too. I'd like to at least have a basic e2e (compose tree, run client tests) flow that can operate in Prow so that if CoreOS CI Jenkins is down or flaky, we at least have some confidence in our commits. Longer term I think we can figure out how to better share CI flows across these: https://github.com/coreos/fedora-coreos-tracker/issues/263#issuecomment-772903759
2021-02-17 17:54:21 +03:00
# Uncomment this to fake a build to test the code below
# RUN mkdir -p /cosa/component-install/usr/bin && echo foo > /cosa/component-install/usr/bin/foo
ci/prow: Install in target cosa, also install and run our tests This is a major downside of reworking and generating new CI flows, it's super easy to lose testing what you intend to. Also, we clearly need to figure out a flow where this is shared across repos, since I don't want to copy-paste this into e.g. ostree too. That's https://github.com/coreos/fedora-coreos-tracker/issues/263
2021-02-25 20:33:14 +03:00
FROM registry.ci.openshift.org/coreos/coreos-assembler:latest
ci: Add Prow e2e testing Our "CoreOS CI Jenkins" flow is great, but the reliability/debuggabilty of the system isn't the best. This is an experient to *add* another CI flow that can be run in Prow too. I'd like to at least have a basic e2e (compose tree, run client tests) flow that can operate in Prow so that if CoreOS CI Jenkins is down or flaky, we at least have some confidence in our commits. Longer term I think we can figure out how to better share CI flows across these: https://github.com/coreos/fedora-coreos-tracker/issues/263#issuecomment-772903759
2021-02-17 17:54:21 +03:00
WORKDIR /srv
ci/prow: Install in target cosa, also install and run our tests This is a major downside of reworking and generating new CI flows, it's super easy to lose testing what you intend to. Also, we clearly need to figure out a flow where this is shared across repos, since I don't want to copy-paste this into e.g. ostree too. That's https://github.com/coreos/fedora-coreos-tracker/issues/263
2021-02-25 20:33:14 +03:00
USER root
# Copy binaries from the build
COPY --from=builder /cosa /cosa
# Merge them to the real root since we're used at compose time
RUN rsync -rlv /cosa/component-install/ /
# Merge installed tests
RUN rsync -rlv /cosa/component-tests/ /
ci: Add Prow e2e testing Our "CoreOS CI Jenkins" flow is great, but the reliability/debuggabilty of the system isn't the best. This is an experient to *add* another CI flow that can be run in Prow too. I'd like to at least have a basic e2e (compose tree, run client tests) flow that can operate in Prow so that if CoreOS CI Jenkins is down or flaky, we at least have some confidence in our commits. Longer term I think we can figure out how to better share CI flows across these: https://github.com/coreos/fedora-coreos-tracker/issues/263#issuecomment-772903759
2021-02-17 17:54:21 +03:00
COPY --from=builder /src/ci/prow/fcos-e2e.sh /usr/bin/fcos-e2e
ci/prow: Install in target cosa, also install and run our tests This is a major downside of reworking and generating new CI flows, it's super easy to lose testing what you intend to. Also, we clearly need to figure out a flow where this is shared across repos, since I don't want to copy-paste this into e.g. ostree too. That's https://github.com/coreos/fedora-coreos-tracker/issues/263
2021-02-25 20:33:14 +03:00
USER builder
Reference in New Issue Copy Permalink