I hereby agree to the terms of the GreptimeDB CLA

What's changed and what's your intention?

It's almost the rewrite of release.yml.

Why need to rewrite release.yml

The original release.yml has the following disadvantages:

• All the logic is coupled in one big yaml file, and hard to add the new artifact release;
• Lots of redundant logic, and always copy and paste the same logic;
• Lack of reproducible builds: the original release.yml uses cross-compiling to build the artifacts instead of Dockerfile;
• Don't support AWS EC2 instances to use larger instances;

The new release.yml

actions/

The new release.yml use composite action to decouple the logic in .github/actions/

• Start/Stop EC2 runners

  • .github/actions/start-runner
  • .github/actions/stop-runner

• Binary building

  • .github/actions/build-greptime-binary: Use make build-greptime-by-buildx command to build greptime and upload it;
  • .github/actions/build-linux-artifacts: Use .github/actions/build-greptime-binary to build Linux greptime by different base images and features.
  • .github/actions/build-macos-artifacts: Still use cross-compiling to build macOS artifacts(most of logic is ported from the original implementation);

• Image building

  • .github/actions/build-images/: Use .github/actions/build-greptime-image to build and push docker images that are based on the different base images;
  • .github/actions/build-greptime-image: Build multiple platform docker image by buildx;
  • .github/actions/build-dev-builder-image: Build and push dev-builder image;

• Releasing and distribution

  • .github/actions/release-artifacts: Create GitHub release notes and release artifacts;
  • .github/actions/upload-artifacts: Upload greptime binary and checksum to GitHub Artifacts and S3;

release.yml

The new release.yml split multiple small and clear jobs to handle releasing:

• At first, we need to use the allocate-runners job to create a version(.github/scripts/create-version.sh) tag and allocate runners;

• After all the resources are ready, the pipeline begins to build multiple binary artifacts;

• After all the binary artifacts are ready, the pipeline begins to build and push docker images;

• At last, the release pipeline will create the GitHub Relase;

The new manual inputs panel

The new manual inputs panel maybe looks complicated but integrates multiple building choices:

The Actions variables and secrets

All the variables and secrets are maintained by Greptime.

Variables

Secrets

Checklist

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)