Skip to content

Latest commit

 

History

History
42 lines (25 loc) · 1.49 KB

RELEASE.md

File metadata and controls

42 lines (25 loc) · 1.49 KB
Raw

Release the project and generate go release

The easy way

Simply create a release using the script ./scripts/tag_release_manually.sh where you pass as parameter your GITHUB_API_TOKEN and ID of the release to be created :

./scripts/tag_release_manually.sh GITHUB_API_TOKEN VERSION

where VERSION corresponds to a string starting with the prefix release- and next by the number of the release (e.g release-0.0.1, release-0.0.2, .... release-0.0.n)

Example

./scripts/tag_release_manually.sh  aaaabbbbcccccdddddeeeeeffff release-0.0.1

This will cause CircleCI to perform a build/release and will create a GitHub release named 0.0.x that will contain the built binaries for both MacOS and Linux.

Note: This assumes that the GITHUB_API_TOKEN has been set in the CircleCI UI for the job !

When performing a CircleCI release, a new docker image will also be created under this name snowdrop/spring-boot-generator which is published on quay.io.

Note: This assumes that the QUAY_ROBOT_USER and QUAY_ROBOT_TOKEN has been set in the CircleCI UI for the job

When the process terminates, the temporary release and tag created under GitHub (release-0.0.1 in the example above) are automatically deleted using

./scripts/delete_release_manually.sh GITHUB_API_TOKEN VERSION

If for whatever reason you want to delete a tag/release manually, here is an example:

Example

./scripts/delete_release_manually.sh aaaabbbbcccccdddddeeeeeffff release-0.0.1