rpm-ostree/ci/prow/fcos-e2e.sh

#!/bin/bash
set -xeuo pipefail

# Prow jobs don't support adding emptydir today
export COSA_SKIP_OVERLAY=1
# And suppress depcheck since we didn't install via RPM
export COSA_SUPPRESS_DEPCHECK=1
ls -al /usr/bin/rpm-ostree
rpm-ostree --version
cd $(mktemp -d)
cosa init https://github.com/coreos/fedora-coreos-config/
rsync -rlv /cosa/component-install/ overrides/rootfs/
cosa fetch
cosa build
cosa kola run 'ext.rpm-ostree.*'
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			`#!/bin/bash`
			`set -xeuo pipefail`

			`# Prow jobs don't support adding emptydir today`
			`export COSA_SKIP_OVERLAY=1`
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			`# And suppress depcheck since we didn't install via RPM`
			`export COSA_SUPPRESS_DEPCHECK=1`
			`ls -al /usr/bin/rpm-ostree`
			`rpm-ostree --version`
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			`cd $(mktemp -d)`
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			`cosa init https://github.com/coreos/fedora-coreos-config/`
			`rsync -rlv /cosa/component-install/ overrides/rootfs/`
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			`cosa fetch`
			`cosa build`
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			`cosa kola run 'ext.rpm-ostree.*'`