keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
94ee42b03b
rpm-ostree/tests/compose-tests/test-mutate-os-release.sh

61 lines
2.1 KiB
Bash
Raw Normal View History

compose-tests: add more tests Add a few more tests to exercise some of the treefile options. We do need to also expand test-basic.sh itself to sanity-check the structure of a normal ostree compose. That's up next on the list. Closes: #548 Approved by: cgwalters
2016-12-09 01:31:20 +03:00
#!/bin/bash
set -xeuo pipefail
dn=$(cd $(dirname $0) && pwd)
. ${dn}/libcomposetest.sh
ci: Bump to F28 Closes: #1358 Approved by: cgwalters
2018-05-19 17:48:18 +03:00
releasever=28
compose-tests: add more tests Add a few more tests to exercise some of the treefile options. We do need to also expand test-basic.sh itself to sanity-check the structure of a normal ostree compose. That's up next on the list. Closes: #548 Approved by: cgwalters
2016-12-09 01:31:20 +03:00
compose-tests: add more mutate-os-release cases Check that the logic added in the previous commit is respected. Closes: #603 Approved by: cgwalters
2017-02-01 20:16:09 +03:00
# specifying the key but neither automatic_version_prefix nor
# --add-metadata-string should cause no mutation
prepare_compose_test "mutate-os-release-none"
Fix "releasever" option, test it by default In #875 AKA b46fc35901acb18a3cbf01fd10bce16acd727650 we added support for the `releasever` option in treefiles. I am pretty sure it worked at the time...but I didn't add tests. Either it never worked or some refactoring broke it. The whole chain of `GKeyFile` → `GVariant` is so confusing. Anyways fix it by copying the string. Now let's use it by default in the compose tests, and while we're here bump those to F27. I'm doing this patch now as I was playing with doing a compose from the `/usr/share/rpm-ostree/treefile.json` and wanted to use the stock `.repo` files. Closes: #1220 Approved by: jlebon
2018-01-20 00:20:12 +03:00
pysetjsonmember "mutate-os-release" '"'${releasever}'"'
compose-tests: add more mutate-os-release cases Check that the logic added in the previous commit is respected. Closes: #603 Approved by: cgwalters
2017-02-01 20:16:09 +03:00
runcompose
echo "ok compose (none)"
ostree --repo=${repobuild} cat ${treeref} \
/usr/lib/os.release.d/os-release-fedora > os-release.prop
Fix "releasever" option, test it by default In #875 AKA b46fc35901acb18a3cbf01fd10bce16acd727650 we added support for the `releasever` option in treefiles. I am pretty sure it worked at the time...but I didn't add tests. Either it never worked or some refactoring broke it. The whole chain of `GKeyFile` → `GVariant` is so confusing. Anyways fix it by copying the string. Now let's use it by default in the compose tests, and while we're here bump those to F27. I'm doing this patch now as I was playing with doing a compose from the `/usr/share/rpm-ostree/treefile.json` and wanted to use the stock `.repo` files. Closes: #1220 Approved by: jlebon
2018-01-20 00:20:12 +03:00
assert_file_has_content os-release.prop VERSION_ID=${releasever}
compose-tests: add more mutate-os-release cases Check that the logic added in the previous commit is respected. Closes: #603 Approved by: cgwalters
2017-02-01 20:16:09 +03:00
assert_not_file_has_content os-release.prop OSTREE_VERSION=
Fix "releasever" option, test it by default In #875 AKA b46fc35901acb18a3cbf01fd10bce16acd727650 we added support for the `releasever` option in treefiles. I am pretty sure it worked at the time...but I didn't add tests. Either it never worked or some refactoring broke it. The whole chain of `GKeyFile` → `GVariant` is so confusing. Anyways fix it by copying the string. Now let's use it by default in the compose tests, and while we're here bump those to F27. I'm doing this patch now as I was playing with doing a compose from the `/usr/share/rpm-ostree/treefile.json` and wanted to use the stock `.repo` files. Closes: #1220 Approved by: jlebon
2018-01-20 00:20:12 +03:00
assert_file_has_content os-release.prop 'VERSION="'${releasever}' (Twenty '
compose-tests: add more mutate-os-release cases Check that the logic added in the previous commit is respected. Closes: #603 Approved by: cgwalters
2017-02-01 20:16:09 +03:00
echo "ok mutate-os-release-none"
# make sure --add-metadata-string has precedence and works with
# mutate-os-release
prepare_compose_test "mutate-os-release-cli"
Fix "releasever" option, test it by default In #875 AKA b46fc35901acb18a3cbf01fd10bce16acd727650 we added support for the `releasever` option in treefiles. I am pretty sure it worked at the time...but I didn't add tests. Either it never worked or some refactoring broke it. The whole chain of `GKeyFile` → `GVariant` is so confusing. Anyways fix it by copying the string. Now let's use it by default in the compose tests, and while we're here bump those to F27. I'm doing this patch now as I was playing with doing a compose from the `/usr/share/rpm-ostree/treefile.json` and wanted to use the stock `.repo` files. Closes: #1220 Approved by: jlebon
2018-01-20 00:20:12 +03:00
pysetjsonmember "automatic_version_prefix" '"'${releasever}'.555"'
pysetjsonmember "mutate-os-release" '"'${releasever}'"'
runcompose --add-metadata-string=version=${releasever}.444
compose-tests: add more mutate-os-release cases Check that the logic added in the previous commit is respected. Closes: #603 Approved by: cgwalters
2017-02-01 20:16:09 +03:00
echo "ok compose (cli)"
ostree --repo=${repobuild} cat ${treeref} \
/usr/lib/os.release.d/os-release-fedora > os-release.prop
# VERSION_ID *shouldn't* change
# (https://github.com/projectatomic/rpm-ostree/pull/433)
Fix "releasever" option, test it by default In #875 AKA b46fc35901acb18a3cbf01fd10bce16acd727650 we added support for the `releasever` option in treefiles. I am pretty sure it worked at the time...but I didn't add tests. Either it never worked or some refactoring broke it. The whole chain of `GKeyFile` → `GVariant` is so confusing. Anyways fix it by copying the string. Now let's use it by default in the compose tests, and while we're here bump those to F27. I'm doing this patch now as I was playing with doing a compose from the `/usr/share/rpm-ostree/treefile.json` and wanted to use the stock `.repo` files. Closes: #1220 Approved by: jlebon
2018-01-20 00:20:12 +03:00
assert_file_has_content os-release.prop VERSION_ID=${releasever}
assert_file_has_content os-release.prop OSTREE_VERSION=${releasever}.444
assert_file_has_content os-release.prop 'VERSION="'${releasever}'\.444 (Twenty '
compose-tests: add more mutate-os-release cases Check that the logic added in the previous commit is respected. Closes: #603 Approved by: cgwalters
2017-02-01 20:16:09 +03:00
echo "ok mutate-os-release-cli"
# make sure automatic_version_prefix works
prepare_compose_test "mutate-os-release-auto"
Fix "releasever" option, test it by default In #875 AKA b46fc35901acb18a3cbf01fd10bce16acd727650 we added support for the `releasever` option in treefiles. I am pretty sure it worked at the time...but I didn't add tests. Either it never worked or some refactoring broke it. The whole chain of `GKeyFile` → `GVariant` is so confusing. Anyways fix it by copying the string. Now let's use it by default in the compose tests, and while we're here bump those to F27. I'm doing this patch now as I was playing with doing a compose from the `/usr/share/rpm-ostree/treefile.json` and wanted to use the stock `.repo` files. Closes: #1220 Approved by: jlebon
2018-01-20 00:20:12 +03:00
pysetjsonmember "automatic_version_prefix" '"'${releasever}'.555"'
pysetjsonmember "mutate-os-release" '"'${releasever}'"'
compose-tests: add more tests Add a few more tests to exercise some of the treefile options. We do need to also expand test-basic.sh itself to sanity-check the structure of a normal ostree compose. That's up next on the list. Closes: #548 Approved by: cgwalters
2016-12-09 01:31:20 +03:00
runcompose
compose-tests: add more mutate-os-release cases Check that the logic added in the previous commit is respected. Closes: #603 Approved by: cgwalters
2017-02-01 20:16:09 +03:00
echo "ok compose (auto)"
compose-tests: add more tests Add a few more tests to exercise some of the treefile options. We do need to also expand test-basic.sh itself to sanity-check the structure of a normal ostree compose. That's up next on the list. Closes: #548 Approved by: cgwalters
2016-12-09 01:31:20 +03:00
ostree --repo=${repobuild} cat ${treeref} \
/usr/lib/os.release.d/os-release-fedora > os-release.prop
# VERSION_ID *shouldn't* change
# (https://github.com/projectatomic/rpm-ostree/pull/433)
Fix "releasever" option, test it by default In #875 AKA b46fc35901acb18a3cbf01fd10bce16acd727650 we added support for the `releasever` option in treefiles. I am pretty sure it worked at the time...but I didn't add tests. Either it never worked or some refactoring broke it. The whole chain of `GKeyFile` → `GVariant` is so confusing. Anyways fix it by copying the string. Now let's use it by default in the compose tests, and while we're here bump those to F27. I'm doing this patch now as I was playing with doing a compose from the `/usr/share/rpm-ostree/treefile.json` and wanted to use the stock `.repo` files. Closes: #1220 Approved by: jlebon
2018-01-20 00:20:12 +03:00
assert_file_has_content os-release.prop VERSION_ID=${releasever}
assert_file_has_content os-release.prop OSTREE_VERSION=${releasever}.555
assert_file_has_content os-release.prop 'VERSION="'${releasever}'\.555 (Twenty '
compose-tests: add more mutate-os-release cases Check that the logic added in the previous commit is respected. Closes: #603 Approved by: cgwalters
2017-02-01 20:16:09 +03:00
echo "ok mutate-os-release (auto)"
Reference in New Issue Copy Permalink