16f762c2ed
This is similar to how other osbuild packages are testing: everything that's needed for testing is included in the tests package or a dependency of it. The test runner then runs every executable in /usr/libexec/tests/<packagename>. This gives a simple test API to projects depending on this package (notably osbuild-composer). The local development workflow described in HACKING.md is meant to continue to work. To ensure this, all relevant scripts gained a TEST_DATA variable, which defaults to `./test`, but is set from $1 to the installed path from integration.sh.
20 lines
500 B
Text
20 lines
500 B
Text
FROM docker.io/library/fedora:latest
|
|
|
|
RUN dnf -y upgrade \
|
|
&& dnf -y \
|
|
--setopt=fastestmirror=True \
|
|
--setopt=install_weak_deps=False \
|
|
install \
|
|
koji-builder \
|
|
koji-utils \
|
|
createrepo_c \
|
|
postgresql \
|
|
python3-koji \
|
|
python3-requests \
|
|
&& dnf clean all
|
|
|
|
COPY container/builder/kojid.conf /etc/kojid/kojid.conf
|
|
COPY container/builder/run-kojid.sh /app/run-kojid.sh
|
|
COPY container/builder/osbuild.krb5.conf /etc/krb5.conf.d/
|
|
|
|
ENTRYPOINT /app/run-kojid.sh
|