Skip to content

Publish 'devel' releases of the chart from master

Dmytro Makovey requested to merge 2285-chart-registry-release into master

What does this MR do?

This MR publishes Helm non-production Helm charts to alternate channels:

  • (existing behavior) tagged releases get published to stable channel using version from Chart.yaml
  • (existing behavior) autodeploy releases get published into autodeploy channel
  • intermediate master builds get published to devel channel using combination of version from Chart.yaml and pipelineID to form "devel version": <version>-<pipelineID>. Since according to SemVer that is considered "pre-release" of <version> subsequent attempt to install corresponding release from stable branch will be considered an "upgrade"

Pre-requisites

It has a requirement of enabled need helm chart repo enabled in settings.

Related issues

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • Merge Request Title and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes

  • Documentation created/updated

  • Tests added

    • tests for chart are already in place
  • Integration tests added to GitLab QA

    • tests for chart are already in place
  • Equivalent MR/issue for omnibus-gitlab opened

    • N/A
Edited by Dmytro Makovey

Merge request reports