Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GIT-ACTIONS] Automate parts of the release process #3686

Closed
25 of 30 tasks
PaulGregoryBaker opened this issue Dec 11, 2023 · 0 comments
Closed
25 of 30 tasks

[GIT-ACTIONS] Automate parts of the release process #3686

PaulGregoryBaker opened this issue Dec 11, 2023 · 0 comments

Comments

@PaulGregoryBaker
Copy link

PaulGregoryBaker commented Dec 11, 2023

Goal:

As a mojaloop maintainer
I want to make the process of making Mojaloop releases easier by using automation where possible
so that I can facilitate the access of new features as soon as the development is completed, to the adopters.

Note: This story is about automating parts of the release process so that releases are quicker to make, reducing the overhead involved and making maintenance easier.

Acceptance Criteria:

  • Verify that a github actions script for release automation is created
  • Verify that the application versions part of the release is automated
  • Verify that the script creates helm release candidate branch
  • Verify that the script update chart versions
  • Verify that the script deploys and tests the release candidate branch to Moja2
  • Verify that package versions can be overridden in scenarios where the latest version is not to be used in a release Tracked in [GIT-ACTIONS] Implement package version override in Helm release workflow #3738

Complexity: <High|Medium|Low> > A short comment to remind the reason for the rating

Uncertainty: <High|Medium|Low> > A short comment to remind the reason for the rating


Tasks:

  • research tools for the automation
  • develop package update manifest for all charts
  • create PR for prerequisite changes to the helm charts
  • validate pre-requisite update to helm chart in dev env
  • validate automatically updated chart in dev env
  • develop github action config and scripts to:
    • create a release candidate branch from master
    • detect breaking changes
    • generate the release note
    • determine the release version number based on changes
    • create a matching snapshot release of TTK test collections
    • deploy and test the branch in Moja2
  • Test workflow and fix all issues found

Done

  • Acceptance Criteria pass
  • Designs are up-to date
  • Unit Tests pass
  • Integration Tests pass
  • Code Style & Coverage meets standards
  • Changes made to config (default.json) are broadcast to team and follow-up tasks added to update helm charts and other deployment config.
  • TBD

Pull Requests:

Follow-up:

Dependencies:

  • N/A

Accountability:

  • Owner: TBC
  • QA/Review: TBC
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants