Since we have succeed in using GH Actions for kogito-cloud project, to maintain cohesion across forks and projects, we should migrate the Operator CI to Github Actions as well:
1. PR CI (from circle to GH as is)
2. Each time we merge into master, a new CR should be uploaded to Quay. This means a new application (https://quay.io/application/kiegroup/kogitocloud-operator?tab=releases) and operator image tag (https://quay.io/repository/kiegroup/kogito-cloud-operator?tab=tags). The dev-preview channel will be updated automatically by OLM, so users that choose this channel will receive devs updates right away!
- is blocked by
-
KOGITO-857 Upgrade Operator SDK to 0.15.1 and Go to 1.13
- Closed
- is incorporated by
-
KOGITO-818 Automate Kogito Cloud projects CI/CD pipelines
- Closed
- is related to
-
KOGITO-100 Integrate Kogito Operator with SonarCloud for PRs
- Closed
- relates to
-
KOGITO-682 Add integration with a CI to run the Kgito Images bats tests
- Resolved
-
KOGITO-316 Researching to look for "multibranch pipeline" on GitHub Actions
- Closed