Continuous Integration (CI)

Continuous Integration (CI)

General

We use GitHub actions as the most popular pipelines for continuous integration. It enables us for every pull request and every change or release to create necessary assets (datamodel dumps, qgs project, documentation, ...)

Create dumps

docker compose up -d --build

The command docker compose up -d --build does the following:

• docker compose up: Builds, (re)creates, starts, and attaches to containers for a service.
• -d: Runs the containers in detached mode (in the background).
• --build: Forces the rebuild of the images before starting the containers.

docker compose exec db init_db.sh wait

The command docker compose exec db init_db.sh wait executes the init_db.sh script inside the db container and waits for the script to complete. Here is a detailed explanation:

• docker compose exec: This command allows you to run commands inside running containers defined in a docker-compose.yml file.
• db: This is the name of the service in the docker-compose.yml file where the command should be executed.
• init_db.sh: This is the script being executed inside the db container.
• wait: This part of the command indicates that Docker will wait for the init_db.sh script to finish executing before returning control.

To resolve any issues with this command, ensure that:

1. The init_db.sh script is present inside the db container.
2. The script has the correct execution permissions.
3. The db service is properly defined and running in the docker-compose.yml file.

If the script is not found or there are access issues, you may need to adjust the path or check the container's configuration.