The DebOps project uses an Open Source, distributed development model. The main code repository is located on GitHub, repository forks are used to introduce and test new code which is then later merged into the main monorepo.
This is a basic code flow from the developers, through the DebOps monorepo and to the end users:
The green rectangles represent the DebOps monorepo (on GitHub) and its local clone on the project maintainer's workstation where GPG code signing is performed.
The yellow rectangles represent monorepo forks on GitHub, which are cloned to the local git repositories, shown in blue. Local development is performed there, developers can use the make test command to check if the code passes the tests (code linting; the same tests are performed on all pull requests using GitHub Actions).
A separate test infrastructure based on GitLab and GitLab Runners can be used to test DebOps roles and playbooks directly. This is done locally by the project maintainer during development. Larger PRs from other contributors can also be pulled to check the changes in the roles and for general integration tests. Signed and accepted pull requests are also tested using GitLab, via a mirror of the DebOps monorepo. Contributors can also set up their own local GitLab environment to perform role and playbook tests.
New commits in the DebOps monorepo trigger the automatic rebuild of the official DebOps Docker image and rebuild of the documentation on ReadTheDocs. New project releases are published manually in PyPI using signed Python packages.