Currently we've broken master container but we're not aware about it as
current tests are very lame, so lets improve it a bit with some more
reliable, extensible solution.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
run: |
docker run --detach ${{ matrix.container_test_command }} --name test-${{ matrix.container_flavor }} local/${{ matrix.container_flavor }}
sleep 5
- docker logs test-${{ matrix.container_flavor }} | tee ${{ matrix.container_flavor }}.log
- grep "${{ matrix.container_verify_string }}" ${{ matrix.container_flavor }}.log
+ pip install cram
+ cram --verbose "tests/cram/${{ matrix.container_flavor }}"
deploy:
name: Push Container
!.github/**/*
!requirements-dev.txt
!.ruff.toml
+!tests
+!tests/**/*
+cram==0.7
black==23.3.0
ruff==0.0.267
--- /dev/null
+Check that logs have expected content after container startup:
+
+ $ docker logs test-master
+ updating existing installation
+ creating /master/master.cfg.sample
+ creating database (sqlite:///state.sqlite)
+ buildmaster configured in /master
--- /dev/null
+Check that logs have expected content after container startup:
+
+ $ docker logs test-worker
+ updating existing installation
+ mkdir /builder/info
+ Creating info/admin, you need to edit it appropriately.
+ Creating info/host, you need to edit it appropriately.
+ Not creating info/access_uri - add it if you wish
+ Please edit the files in /builder/info appropriately.
+ worker configured in /builder