This repository aims to show up some basic CI/CD.
To do so, we'll use GitHub Actions, a tool that allows to implement workflows for different branches and with different jobs;
For those unfamiliar with the terms, we'll talk a little bit about them and their practical implications:
CI stands for continuous integration, which means the continual improvement of the code base, with appropriate TESTING and integration to a shared source;
Regarding test automatisation, using Actions allows you to setup the launching of lint and tests for each developer branch, making sure that the integrity of that codebase is maintained.
To be able to launch those tests, you'll need the proper base.
Quickly saying, a basic python project structure would look like this:
Once this structure is set, you can move to the .github/workflows/workflow.yml and see the different steps
involved in launching automated tests on the code base. We prepare the environment by doing installation and eventual
updates to packages; then we check for syntax errors etc. using lint and finally we launch our unit tests with
pytest.
The result you obtain when clicking over the Actions button is like the following:
CD stands for continual delivery/deployment. It means that the deployment to production and to other developers/users should be automated as well.
This is also possible with GitHub Actions, where you can publish your packages, images etc. when a version is tagged for instance.
The example for this is in .github/workflows/deploy.yml, where we only stored the generated wheel as an artifact in Git,
but you can deploy it to any Artifactory you desire; we also deploy a docker image to Docker Hub;