-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Stefan edited this page Dec 9, 2020
·
1 revision
Each build process produces a single artefacts (zip). This contains the resultant PDFs for each type of build.
CI builds are triggered by any 'push' to the [MASTER] branch. There is an option to trigger this build manually in the event that an automated CI build fails due to issues with the build process.
Release builds are triggered by adding a git tag to a commit. The value of tag will be used as the document identifier on both the cover and in the resulting artefact file name. For example use a tag of 'DRAFT-IP4' or '2.1'. There is also an option to trigger this build manually.