[Epic] Automated Release Pipelines

[grischperl]

Automated Release Pipelines for the Eventing Manager

The goal is to have completely automated release pipelines for the NATS Manager and the Eventing Manager.

Current flow:

• Create a branch Patch: Branch already exists Minor: Create new branch
• PR to bump sec-scanners-config.yaml
• Github action: Create release with version input
  • version number validated by format and singularity
  • Create changelog
  • Create draft release
  • Build binaries
  • Run checks on the image
  • Upload created manifests to draft release
  • Check for successful image build job
  • Check for successful manager build job
  • Change draft release to release
• Release completed

Goal:

• Create a branch
• [x] #360
  • Reusable for all repositories
  • Check that branch name follows release-x.y naming
  • Version input created by branch name (x.y from branch name, z from existing version +1)
• [x] #361
  • Automatically create PR
  • Trigger linting, unit test on this PR
  • Further flow only upon approval & merging of the PR
• [x] #370
• [x] #363
  • Do not tag image yet
• [x] #364
  • needs following tests:
  • [x] #381
  • [x] #389
  • [x] #390
  • [x] #131
  • Wait for the tests to succeed
• Create changelog
• Create draft release
• Upload created manifests to draft release
• Tag image with release version
• Change draft release to release
• [x] #362
• [ ] Cleanup if necessary
• [ ] Update documentation

⚠️ Release Pipelines ⚠️

Once every task for release pipeline of the Eventing Manager is completed, create issues to replicate the same flow on NATS Manager.

[github-actions[bot]]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically closed due to the lack of recent activity. /lifecycle rotten