yudaike/openSUSE-release-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
openSUSE-release-tools/dist/ci/docker-compose.yml

47 lines
1.2 KiB
YAML
Raw Normal View History

Run the nosetests in a tumbleweed container instead of travis environment The docker-compose file starts an OBS instance (on 15.0 atm) and runs the test suite in a test container (tumbleweed), so all tests run in an isolated environment accessing OBS at api:3000
2019-05-03 11:04:19 +02:00
version: "3.4"
Add small OBS instance without data The default user is Admin:opensuse and the docker compose opens only one port at 3737 running the api/webui This can be used for CI on sources or to build against it with osc (if you add interconnect project), but it won't build packages
2019-04-20 12:15:37 +02:00
x-obs: &obs
image: registry.opensuse.org/opensuse/tools/images/containers/osrt_miniobs:latest
Run flake8 from Tumbleweed
2019-05-06 22:52:22 +02:00
x-testenv: &testenv
image: registry.opensuse.org/opensuse/tools/images/containers_tumbleweed/osrt_testenv_tumbleweed:latest
volumes:
- "../..:/code"
Add small OBS instance without data The default user is Admin:opensuse and the docker compose opens only one port at 3737 running the api/webui This can be used for CI on sources or to build against it with osc (if you add interconnect project), but it won't build packages
2019-04-20 12:15:37 +02:00
services:
db:
<<: *obs
command: /usr/lib/mysql/mysql-systemd-helper start
cache:
<<: *obs
command: /usr/sbin/memcached -u memcached
api:
<<: *obs
command: chroot --userspec=wwwrun / /bin/bash -c "cd /srv/www/obs/api && /usr/bin/bundle exec rails s -e production"
depends_on:
- db
- cache
- srcserver
- repserver
- servicedispatch
srcserver:
<<: *obs
command: chroot --userspec=obsrun / /usr/lib/obs/server/bs_srcserver
repserver:
<<: *obs
command: chroot --userspec=obsrun / /usr/lib/obs/server/bs_repserver
servicedispatch:
<<: *obs
command: chroot --userspec=obsrun / /usr/lib/obs/server/bs_servicedispatch
Run the nosetests in a tumbleweed container instead of travis environment The docker-compose file starts an OBS instance (on 15.0 atm) and runs the test suite in a test container (tumbleweed), so all tests run in an isolated environment accessing OBS at api:3000
2019-05-03 11:04:19 +02:00
test:
Run flake8 from Tumbleweed
2019-05-06 22:52:22 +02:00
<<: *testenv
Run the nosetests in a tumbleweed container instead of travis environment The docker-compose file starts an OBS instance (on 15.0 atm) and runs the test suite in a test container (tumbleweed), so all tests run in an isolated environment accessing OBS at api:3000
2019-05-03 11:04:19 +02:00
depends_on:
- api
command: /code/dist/ci/docker-compose-test.sh
cap_add:
- SYS_PTRACE
Run flake8 from Tumbleweed
2019-05-06 22:52:22 +02:00
flaker:
<<: *testenv
command: /code/dist/ci/docker-compose-flaker.sh
Run the nosetests in a tumbleweed container instead of travis environment The docker-compose file starts an OBS instance (on 15.0 atm) and runs the test suite in a test container (tumbleweed), so all tests run in an isolated environment accessing OBS at api:3000
2019-05-03 11:04:19 +02:00
Reference in New Issue Copy Permalink