Automated Artefact Releases

The process of publishing and releasing artefacts is not well or consistently defined.

By standardising and automate the process of publishing artefacts, it will be possible to provide a consistent way for artefact releases to be advertised to stakeholders, with a bread-crumb trail connecting the release to the related features/stories, along with a synopsis of the contents and linkage to find the details.  In turn, this will then allow aggregate releases to be constructed with the ability to drill down to any detail desired.

• Process and documentation for git-chglog implementation in repository projects 
• GitLab CI template for changelog and GitLab release page generation and publishing
• New automated release publishing process implemented in key dependent repositories: ska-tango-(base/images/examples)

Acceptance criteria is met. The following are created:

• changelog generation based on commits, Jira tickets (features, stories and REL project link) supporting the repo's own CHANGELOG file
• pipeline jobs are developed to trigger the above and using the changelog create a release in GitLab
• GitLab release is appended to the Jira ticket's Release Notes
• GitLab release is sociliased in a slack channel

Examples:

• slack channel: https://skao.slack.com/archives/C02MDNMPWKF;
• Test Tab Release: https://gitlab.com/ska-telescope/ska-tango-images/-/tags/0.3.7
• Jira Ticket: REL-11

Future Discussion:

• The current process is fully automated but as a result, it doesn't support manual input into the Changelog. They can be edited after the pipeline is run and the GitLab release is created.