rpm-ostree/tests/compose-tests/test-compose2jigdo.sh

#!/bin/bash
# Test rpm-ostree compose tree --ex-rojig-output-rpm

set -xeuo pipefail

dn=$(cd $(dirname $0) && pwd)
. ${dn}/libcomposetest.sh
. ${dn}/../common/libtest.sh

prepare_compose_test "compose2jigdo"
pysetjsonmember "ex-rojig-spec" '"fedora-atomic-host-oirpm.spec"'
mkdir cache
mkdir jigdo-output
runcompose --ex-rojig-output-rpm $(pwd)/jigdo-output --cachedir $(pwd)/cache --add-metadata-string version=42.0
rev=$(ostree --repo=repo-build rev-parse ${treeref})
find jigdo-output -name '*.rpm' | tee rpms.txt
assert_file_has_content rpms.txt 'fedora-atomic-host-42.0.*x86_64'
grep 'fedora-atomic-host.*x86_64\.rpm' rpms.txt | while read p; do
    rpm -qp --provides ${p} >>provides.txt
done
assert_file_has_content_literal provides.txt "rpmostree-jigdo-commit(${rev})"
echo "ok compose2jigdoRPM"

runcompose --force-nocache --ex-rojig-output-set $(pwd)/jigdo-output --cachedir $(pwd)/cache --add-metadata-string version=42.1
rev=$(ostree --repo=repo-build rev-parse ${treeref})
find jigdo-output -name '*.rpm' | tee rpms.txt
assert_file_has_content rpms.txt 'systemd.*x86_64'
assert_file_has_content rpms.txt 'ostree.*x86_64'
assert_file_has_content rpms.txt 'fedora-atomic-host-42.1.*x86_64'
echo "ok compose2jigdoSet"
compose: Add --ex-jigdo-output-rpm Part of the goal of jigdo ♲📦 is to support organizations switching to only providing RPMs. An intermediate step there is to "lock" the repo and jigdo together; we don't want to update the ref if building the jigdoRPM fails. Add an option to perform `rpm-ostree compose tree` and `rpm-ostree ex commit2jigdo` together; notably we generate a commit, but only update the ref once the jigdoRPM is built. Closes: #1165 Approved by: jlebon 2017-12-21 07:11:24 +03:00			`#!/bin/bash`
Initial renaming pass of "jigdo" to "rojig" I noticed that Ubuntu also uses the original "jigdo", so let's start pulling off the band-aid here and do a mass rename. For this first pass I'm focusing on CLI entrypoints and docs, as that's what people are going to see; renaming all of the internal C functions, structure variables etc. can come later. Closes: #1269 Approved by: jlebon 2018-02-22 18:18:24 +03:00			`# Test rpm-ostree compose tree --ex-rojig-output-rpm`
compose: Add --ex-jigdo-output-rpm Part of the goal of jigdo ♲📦 is to support organizations switching to only providing RPMs. An intermediate step there is to "lock" the repo and jigdo together; we don't want to update the ref if building the jigdoRPM fails. Add an option to perform `rpm-ostree compose tree` and `rpm-ostree ex commit2jigdo` together; notably we generate a commit, but only update the ref once the jigdoRPM is built. Closes: #1165 Approved by: jlebon 2017-12-21 07:11:24 +03:00
			`set -xeuo pipefail`

			`dn=$(cd $(dirname $0) && pwd)`
			`. ${dn}/libcomposetest.sh`
			`. ${dn}/../common/libtest.sh`

			`prepare_compose_test "compose2jigdo"`
Initial renaming pass of "jigdo" to "rojig" I noticed that Ubuntu also uses the original "jigdo", so let's start pulling off the band-aid here and do a mass rename. For this first pass I'm focusing on CLI entrypoints and docs, as that's what people are going to see; renaming all of the internal C functions, structure variables etc. can come later. Closes: #1269 Approved by: jlebon 2018-02-22 18:18:24 +03:00			`pysetjsonmember "ex-rojig-spec" '"fedora-atomic-host-oirpm.spec"'`
compose: Add --ex-jigdo-output-rpm Part of the goal of jigdo ♲📦 is to support organizations switching to only providing RPMs. An intermediate step there is to "lock" the repo and jigdo together; we don't want to update the ref if building the jigdoRPM fails. Add an option to perform `rpm-ostree compose tree` and `rpm-ostree ex commit2jigdo` together; notably we generate a commit, but only update the ref once the jigdoRPM is built. Closes: #1165 Approved by: jlebon 2017-12-21 07:11:24 +03:00			`mkdir cache`
			`mkdir jigdo-output`
Initial renaming pass of "jigdo" to "rojig" I noticed that Ubuntu also uses the original "jigdo", so let's start pulling off the band-aid here and do a mass rename. For this first pass I'm focusing on CLI entrypoints and docs, as that's what people are going to see; renaming all of the internal C functions, structure variables etc. can come later. Closes: #1269 Approved by: jlebon 2018-02-22 18:18:24 +03:00			`runcompose --ex-rojig-output-rpm $(pwd)/jigdo-output --cachedir $(pwd)/cache --add-metadata-string version=42.0`
compose: Add --ex-jigdo-output-rpm Part of the goal of jigdo ♲📦 is to support organizations switching to only providing RPMs. An intermediate step there is to "lock" the repo and jigdo together; we don't want to update the ref if building the jigdoRPM fails. Add an option to perform `rpm-ostree compose tree` and `rpm-ostree ex commit2jigdo` together; notably we generate a commit, but only update the ref once the jigdoRPM is built. Closes: #1165 Approved by: jlebon 2017-12-21 07:11:24 +03:00			`rev=$(ostree --repo=repo-build rev-parse ${treeref})`
			`find jigdo-output -name '*.rpm' \| tee rpms.txt`
			`assert_file_has_content rpms.txt 'fedora-atomic-host-42.0.*x86_64'`
			`grep 'fedora-atomic-host.*x86_64\.rpm' rpms.txt \| while read p; do`
			`rpm -qp --provides ${p} >>provides.txt`
			`done`
			`assert_file_has_content_literal provides.txt "rpmostree-jigdo-commit(${rev})"`
compose: Add --ex-jigdo-output-set Following up on `--ex-jigdo-output-rpm`, add support for writing the entire set to an output directory. This is intended for use cases like FAHC, where we're generating data outside of the upstream Fedora infrastructure. Further, we want to support having our own history stored reliably, even if upstream prunes RPMs. Now, this can be interesting even for upstreams like Fedora, as it naturally captures just the subset of RPMs; doing full history support for that would likely be a lot more palatable than for Everything. Closes: #1165 Approved by: jlebon 2017-12-21 08:27:54 +03:00			`echo "ok compose2jigdoRPM"`

Initial renaming pass of "jigdo" to "rojig" I noticed that Ubuntu also uses the original "jigdo", so let's start pulling off the band-aid here and do a mass rename. For this first pass I'm focusing on CLI entrypoints and docs, as that's what people are going to see; renaming all of the internal C functions, structure variables etc. can come later. Closes: #1269 Approved by: jlebon 2018-02-22 18:18:24 +03:00			`runcompose --force-nocache --ex-rojig-output-set $(pwd)/jigdo-output --cachedir $(pwd)/cache --add-metadata-string version=42.1`
compose: Add --ex-jigdo-output-set Following up on `--ex-jigdo-output-rpm`, add support for writing the entire set to an output directory. This is intended for use cases like FAHC, where we're generating data outside of the upstream Fedora infrastructure. Further, we want to support having our own history stored reliably, even if upstream prunes RPMs. Now, this can be interesting even for upstreams like Fedora, as it naturally captures just the subset of RPMs; doing full history support for that would likely be a lot more palatable than for Everything. Closes: #1165 Approved by: jlebon 2017-12-21 08:27:54 +03:00			`rev=$(ostree --repo=repo-build rev-parse ${treeref})`
			`find jigdo-output -name '*.rpm' \| tee rpms.txt`
			`assert_file_has_content rpms.txt 'systemd.*x86_64'`
			`assert_file_has_content rpms.txt 'ostree.*x86_64'`
			`assert_file_has_content rpms.txt 'fedora-atomic-host-42.1.*x86_64'`
			`echo "ok compose2jigdoSet"`