micro
develop
develop
  • Micro Starter Kit
  • Features
  • Getting Started
    • Why
    • Prerequisites
    • Installation
    • Makefile
  • Concepts
    • Introduction
    • Configuration
    • State
    • Select
  • Advanced
    • Dependency Injection
    • Logging
    • Error Handling
    • Life-cycle
    • Git Flow
    • Git Ops
    • mTLS
    • Release
    • Release Process
    • Pub Sub
    • Troubleshooting
  • Modules
    • Commands
      • Demo
    • Services
      • Account
      • Emailer
      • Greeter
      • Recorder
  • DevOps
    • Docker
    • KinD
    • Istio
  • Testing
    • Intro
    • Mock
    • Bloom RPC
  • Recipes
    • Authentication
    • Caching
    • Health Checks
    • Performance Testing
    • Dynamic Plugins
    • Immutability Helpers
    • Style Guide
    • Unit Testing
  • Community
    • Resources
    • Contributors
    • Contributing
  • Change Log
  • FAQ
Powered by GitBook
On this page

Was this helpful?

  1. Advanced

Release Process

  • Draft a release

  • Upload release assets

  • Publish a release

Flow:

  1. Manually tag with make release/draft VERSION=v0.1.1

  2. Release Management Pipeline create draft release, upload assets, build and publish docker images.

  3. On release success event, Deploy Pipeline get triggered and applications get deployed to QA k8s cluster.

  4. On deployment success event, E2E Pipeline get triggered and E2E tests will be executed

Before beginning, you will need your Github personal access token.

make release/draft VERSION=v0.1.1

At this point, you should inspect the release in the Github web UI. If it looks reasonable, proceed:

export GITHUB_TOKEN=$YOUR_TOKEN
make release/publish
PreviousReleaseNextPub Sub

Last updated 5 years ago

Was this helpful?