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.
28 lines
774 B
Text
28 lines
774 B
Text
FROM registry.access.redhat.com/ubi8/ubi:latest
|
|
|
|
COPY container/rhel.repo /etc/yum.repos.d/
|
|
COPY container/brew.repo /etc/yum.repos.d/
|
|
|
|
# koji db schema is in docs, remove nodocs from from dnf config
|
|
RUN sed -i '/^tsflags=nodocs$/d' /etc/dnf/dnf.conf
|
|
|
|
RUN dnf -y upgrade \
|
|
&& dnf -y \
|
|
--setopt=fastestmirror=True \
|
|
--setopt=install_weak_deps=False \
|
|
install \
|
|
koji-hub \
|
|
postgresql \
|
|
mod_ssl \
|
|
koji-web \
|
|
python3-jsonschema \
|
|
&& dnf clean all
|
|
|
|
COPY container/hub/hub.conf /etc/koji-hub/hub.conf
|
|
COPY container/hub/ssl.conf /etc/httpd/conf.d/ssl.conf
|
|
COPY container/hub/run-hub.sh /app/run-hub.sh
|
|
|
|
COPY container/hub/web.conf /etc/kojiweb/web.conf
|
|
COPY container/hub/kojiweb.conf /etc/httpd/conf.d/kojiweb.conf
|
|
|
|
ENTRYPOINT /app/run-hub.sh
|