You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Goal:
As a
mojaloop maintainerI want to
make the process of making Mojaloop releases easier by using automation where possibleso 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 package versions can be overridden in scenarios where the latest version is not to be used in a releaseTracked in [GIT-ACTIONS] Implement package version override in Helm release workflow #3738Complexity: <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:
Done
Pull Requests:
Follow-up:
Dependencies:
Accountability:
The text was updated successfully, but these errors were encountered: