Changes for testing 'upgrade' from develop branch

[niladrih]

Upgrade e2e tests are run as a part of release/x.y branches, but not develop or main. This change modifies the chart that is posted to the 'main' branch, and this chart should qualify as a valid target helm chart for upgrade, thus allowing testing code from develop (main branch uses code from develop at a set frequency).

The intention is to be able to upgrade from a released version to develop or main.

Description

Changes to upgrade code:

• Adds support for parsing repotags in the upgrade-job::helm::chart module
• Adds default set options for setting repotags along with image tags. This is required because the main branch chart uses image.repoTags instead of image.tag.

Changes to publish_chart_yaml.sh script:

• Changes appVersion and version set when generating main branch chart (using the --develop-to-main flag) from 0.0.0-main to the likes of 2.5.0-0-develop-unstable-2023-09-24-19-55-15-0, where 2.5.0 is semver minor bump from the latest possible release (based on existing release/x.y branches on openebs/mayastor-extensions), and 2023-09-24-19-55-15 is a timestamp generated from the commanddate +%Y-%m-%d-%H-%M-%S.
• Latest release branch name can be input to the script using the --latest-release-branch <branch_name> option. The default value is generated from git remote refs from the git repo. To use the default branch-name generation, all refs from the remote repo openebs/mayastor-extensions must be pulled in (e.g. git fetch origin where origin is the remote entry for the openebs/mayastor-extensions repo)
• Bump to the latest is set to minor version by-default. The --bump-major-for-main bumps the major version instead, if and when the version bump needs to be a major one.

GitHub Actions changes:

• Remove the publish step for the main branch helm chart workflow. This is no longer required as helm charts on the main branch will be versioned (the -main suffix will no longer have any use) and the charts will be hosted on the https://github.com/openebs/mayastor-chart-donotuse repo.
• Use --check-chart to run a basic sanity test, like the one for the develop-chart actions workflow.

This change adds two major use cases for the publish_chart_yaml.sh script:

1. Generate the main branch helm chart from the develop branch helm chart (used in CI) using

./scripts/helm/publish_chart_yaml.sh \
        --check-chart main \
        --develop-to-main \
        --date-time $(date +%Y-%m-%d-%H-%M-%S)

2. Use it to sanitize changes to the chart using ./scripts/helm/publish_chart_yaml.sh --check-chart main. This is minor use-case, This does not do a good job of validating the chart version/appVersion, etc.

Tested manually.

[niladrih]

bors try

[bors]

try

Build failed:

• continuous-integration/jenkins/branch

[niladrih]

bors try

[bors]

try

Build failed:

• continuous-integration/jenkins/branch

[niladrih]

bors try

[bors]

try

Build failed:

• continuous-integration/jenkins/branch

[niladrih]

bors cancel

[niladrih]

bors try

[bors]

try

Build failed:

• continuous-integration/jenkins/branch

[niladrih]

bors cancel

[niladrih]

bors try

[niladrih]

bors cancel

[niladrih]

bors try

[bors]

try

Build succeeded!

The publicly hosted instance of bors-ng is deprecated and will go away soon.

If you want to self-host your own instance, instructions are here.
For more help, visit the forum.

If you want to switch to GitHub's built-in merge queue, visit their help page.

• continuous-integration/jenkins/branch

[r1jt]

Reviewed the github action, and publish helm chart sections of the PR

[niladrih]

bors merge

[bors]

Canceled.

[niladrih]

bors merge

[bors]

🕐 Waiting for PR status (GitHub check) to be set, probably by CI. Bors will automatically try to run when all required PR statuses are set.

[bors]

Build succeeded!

The publicly hosted instance of bors-ng is deprecated and will go away soon.

If you want to self-host your own instance, instructions are here.
For more help, visit the forum.

If you want to switch to GitHub's built-in merge queue, visit their help page.

• continuous-integration/jenkins/branch