...
| Development | Staging | Production |
|---|---|---|
| Code development is done on the Master branch by developers doing fixes on branches from Master and their subsequent code merged to master. | Staging uses the release branch of ukrdc-webapi and the ukrdc-services pinned in the requirements.txt. Say, in this case 10.8.4 | At the start of the cycle, the deployed code of ukrdc-webapi on production has the ukrdc-services module pinned to 10.8.4. |
Once a point is reached where code is to be released, a tag on the Master branch is made and the tag merged the point has come to release, ake sure the ukrdc/services/__init__.py is bumped to a release candidate version - in this case 10.8.5.RC1.This will then be built as the wheel file on the release branch. | ||
| Tag the Master branch and merge the tag to the release branch | ||
When the code is merged from master into the release branch, the wheel file from ukrdc-services[release] is marked asbuild process will build and upload the 10.8.5RC1 , which is built and deployedto the releasedevpi index. | ||
| When the 10.8.5RC1 ukrdc-services wheel has been successfully tested, the wheel file is marked and deployed as the version number on the release branch will be changed to 10.8.5 on the dev-pi release index.The ukrdc-webapi , the requirements.txt entry for on ukrdc-services is updated to webapi[release] updated to 10.8.5; | ||
| The wheel file will be built as 10.8.5 on the dev-pi release index. | ||
| The production server is updated with the new code on the release branch. |
...