Continuous integration and deployment guide
We aim to have as much as possible uniform Continuous integration / deployment (CI/CD) process between modules and code organisation.
Every module has its own repository, which is provided from the template repository.
Here is a list of the tools used for CI/CD.
Precommit is deployed on every repository as a github app. It requires a .pre-commit-config.yaml at the root of the repository.
We use GitHub Actions to test and deploy new releases of TEKSI modules.
GitHub actions are running on every pull request to :
- Assess no regression occurred on current unit tests
- Provide useful artefacts for testing purposes
When a new release is set, GitHub actions are providing dumps and necessary assets to ease the deployment of any TEKSI module.
Any merged pull request on the documentation will provided an updated version of the online documentation.
Scheduled and triggered GitHub actions are updating the translations strings.
