Skip to content

Release automatically #94

Closed
Closed
@vanyarock01

Description

@vanyarock01

Releases are now hand-made. This is bad...

The release is done like this:

  • Build tarantool-operator docker image (command available in Makefile) and push it to the docker hub.
  • Make a commit with updated version of charts and changelog to master (remember the commit hash).
  • Pack charts to .cr-release-packages:
    $ mkdir -p .cr-release-packages
    $ helm package ci/helm-chart/ && mv tarantool-operator-X.Y.Z.tgz .cr-release-packages/
    $ helm package examples/kv/ && mv cartridge-X.Y.Z.tgz .cr-release-packages/
  • Use chart-releaser for make release on commit.
    $ cr upload -c <TARGET_COMMIT_HASH> -r tarantool-operator -o tarantool -t <ACCESS_TOKEN>
  • Checkout to branch gh-pages
  • Update helm repo index (check the correctness of the diff):
    $ mkdir -p .cr-index/ && cr index -c https://tarantool.github.io/tarantool-operator -r tarantool-operator -o tarantool
    $ diff .cr-index/index.yaml index.yaml
    $ mv .cr-index/index.yaml .
    $ git add index.yaml && git commit ...

It is necessary to automate.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions