Actions
This step verifies that the server is ready to receive builds.
Check if Builder-CI services are up and running¶
The Builder-CI installation creates two services that should start automatically :
- builder-ci-api: Exposed web API used to trigger pipeline and builds.
- builder-ci-worker: Listens and run builds.
To check the status of both servers, use the following command:
systemctl status builder-ci-api builder-ci-worker
The output should be similar to the below showing "Active: active" and no errors.
● builder-ci-api.service - Builder CI API
Loaded: loaded (/lib/systemd/system/builder-ci-api.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2021-06-21 21:23:59 CEST; 3 days ago
Main PID: 2314 (gunicorn3)
Tasks: 13 (limit: 4698)
Memory: 33.7M
CGroup: /system.slice/builder-ci-api.service
├─2314 /usr/bin/python3 /usr/bin/gunicorn3 --workers 4 --bind 127.0.0.1:5000 wsgi:app
├─2336 /usr/bin/python3 /usr/bin/gunicorn3 --workers 4 --bind 127.0.0.1:5000 wsgi:app
├─2337 /usr/bin/python3 /usr/bin/gunicorn3 --workers 4 --bind 127.0.0.1:5000 wsgi:app
├─2345 /usr/bin/python3 /usr/bin/gunicorn3 --workers 4 --bind 127.0.0.1:5000 wsgi:app
└─2347 /usr/bin/python3 /usr/bin/gunicorn3 --workers 4 --bind 127.0.0.1:5000 wsgi:app
jun 21 21:23:59 builder systemd[1]: Started Builder CI API.
jun 21 21:23:59 builder gunicorn3[2314]: [2021-06-21 21:23:59 +0200] [2314] [INFO] Starting gunicorn 19.9.0
jun 21 21:23:59 builder gunicorn3[2314]: [2021-06-21 21:23:59 +0200] [2314] [INFO] Listening at: http://127.0.0.1:5000 (2314)
jun 21 21:23:59 builder gunicorn3[2314]: [2021-06-21 21:23:59 +0200] [2314] [INFO] Using worker: sync
jun 21 21:23:59 builder gunicorn3[2314]: [2021-06-21 21:23:59 +0200] [2336] [INFO] Booting worker with pid: 2336
jun 21 21:23:59 builder gunicorn3[2314]: [2021-06-21 21:23:59 +0200] [2337] [INFO] Booting worker with pid: 2337
jun 21 21:23:59 builder gunicorn3[2314]: [2021-06-21 21:23:59 +0200] [2345] [INFO] Booting worker with pid: 2345
jun 21 21:23:59 builder gunicorn3[2314]: [2021-06-21 21:23:59 +0200] [2347] [INFO] Booting worker with pid: 2347
● builder-ci-worker.service - Builder CI Worker
Loaded: loaded (/lib/systemd/system/builder-ci-worker.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2021-06-21 21:23:59 CEST; 3 days ago
Main PID: 2343 (python3)
Tasks: 5 (limit: 4698)
Memory: 421.3M
CGroup: /system.slice/builder-ci-worker.service
└─2343 /usr/bin/python3 listener.py
jun 25 01:51:29 builder python3[2343]: 2021-06-25 01:51:29,032:WARNING:### This build already exist into DB with state success, stopping the build
jun 25 01:51:29 builder python3[2343]: 2021-06-25 01:51:29,033:INFO:Removing build folder
jun 25 01:51:29 builder python3[2343]: 2021-06-25 01:51:29,038:INFO:### Running step: notify
jun 25 01:51:29 builder python3[2343]: 2021-06-25 01:51:29,039:DEBUG:builder.yml not present
Check if API port is opened¶
Builder-CI API listens on port 5000 by default(this is hardcoded however it will soon be configured within /etc/builder-ci/builder-ci.conf
).
ss -tnl
Check the presence of port 5000.
LISTEN 0 128 127.0.0.1:5000 0.0.0.0:*
Check docker images¶
Local docker images should be ready to use. They all start with the name "builder-*", you can simply do:
docker images builder-*
REPOSITORY TAG IMAGE ID CREATED SIZE
builder-npm latest a1667696a8a0 6 days ago 567MB
builder-ionic latest 7a5a459be1a0 6 days ago 2.2GB
builder-focal latest 217d0f6b42f0 6 days ago 513MB
builder-flutter latest ea3f0d523cae 6 days ago 4.04GB
builder-f34 latest 8832d10fb18f 6 days ago 890MB
builder-centos8 latest 866bf3f16a04 6 days ago 425MB
builder-centos7 latest 6f2e72ebc74c 6 days ago 446MB
builder-bullseye latest 4a5c04027262 6 days ago 712MB
Updated by Olivier Bitsch over 3 years ago · 2 revisions