ff70b269fb
The test package should be self-contained and contain all the configuration necessary for a known-good test run (minus secrets). This moves repo overrides from the test orchestration into the test package. We want all the external sources (including boot isos and repositories) to be pinned by their content hash, and never use anything that is not strictly defined. This moves us in the right direction, but we still have some tests to update to use these shipped repos rather than official mirrors. One remaining challenge is that we must make sure all our test runners have access to the RHEL snapshots, which is not currently the case for the runners in EC2, but a solution is in the works. Signed-off-by: Tom Gundersen <teg@jklm.no>
28 lines
932 B
Bash
Executable file
28 lines
932 B
Bash
Executable file
#!/bin/bash
|
|
set -euxo pipefail
|
|
|
|
sudo mkdir -p /etc/osbuild-composer
|
|
sudo cp -a /usr/share/tests/osbuild-composer/composer/*.toml \
|
|
/etc/osbuild-composer/
|
|
|
|
|
|
# Copy Fedora rpmrepo snapshots for use in weldr tests. RHEL's are usually more
|
|
# stable, and not available publically from rpmrepo.
|
|
sudo mkdir -p /etc/osbuild-composer/repositories
|
|
sudo cp -a /usr/share/tests/osbuild-composer/repositories/fedora-*.json \
|
|
/etc/osbuild-composer/repositories/
|
|
|
|
sudo cp -a /usr/share/tests/osbuild-composer/ca/* \
|
|
/etc/osbuild-composer/
|
|
sudo chown _osbuild-composer /etc/osbuild-composer/composer-*.pem
|
|
|
|
sudo systemctl start osbuild-remote-worker.socket
|
|
sudo systemctl start osbuild-composer.socket
|
|
sudo systemctl start osbuild-composer-api.socket
|
|
|
|
# Basic verification
|
|
sudo composer-cli status show
|
|
sudo composer-cli sources list
|
|
for SOURCE in $(sudo composer-cli sources list); do
|
|
sudo composer-cli sources info "$SOURCE"
|
|
done
|