Handles GitHub flow, user manual export and file copying needed at validation and deployments.
- release-tools (https://github.com/Molmed/release-tools)
- confluence-tools (https://github.com/withrocks/confluence-tools)
- If a c# application is to be deployed, Visual Studio 2017 must be installed
The GitHub repo of the application must have the branch structure described in https://github.com/Molmed/release-tools.
Input data, e.g. paths, confluence space key, are stored in the release_ccharp.config file.
It have to be .config files in location:
<root_path>/<repo-name>/buildconfig/release-tools.config
<root_path>/<repo-name>/buildconfig/confluence-tools.config
The rest of the folder structure will be created when running the workflow the first time.
I have tried to write the code platform independent, although it has only been tested on C# applications.
Intended workflow:
release-ccharp create-cand <repo-name>
release-ccharp download <repo-name>
release-ccharp generate-user-manual <repo-name> (optional)
release-ccharp accept <repo-name>
(write release notes manually at GitHub)
release-ccharp download-release-history <repo-name>
A new application has to be added to the file repo.config. It should be self explainatory how to fill it in. The changes have to be added to this repo. In addition you have to define a workflow for the new application. Follow the pattern for one of the existing applications under release-ccharp.apps package.
Before running through the deploy workflow the first time, a release has to be added to the repo manually in GitHub. You will be asked to enter a name for the tag associated with the release. This tag has to be in the form v0.0.1 (i.e. v..)
pip install -U git+https://github.com/Molmed/release-ccharp.git#egg=release-ccharp
Ensure that you have the python script path <python installation dir>/Scripts added in your PATH environment variable.