EPIC - SonataFlow Operator and Kogito Images migration to kie-tools

[ricardozanini]

Migration of the incubator-kie-kogito-images and incubator-kie-kogito-serverless-operator repositories into the incubator-kie-tools. The objective is to unify the codebases to simplify maintenance and improve CI processes. The migration will occur in two phases, starting with kogito-images, followed by the kogito-serverless-operator.

Tasks Overview

Create Migration Branch in incubator-kie-tools

• Create a new branch from the main in the incubator-kie-tools repository.
• Delete unnecessary packages from the new branch.
• Commit the changes to the incubator-kie-tools repo.

Prepare kogito-images for Migration

• Checkout the kogito-images repository on main.
• Delete the existing content but do not commit the changes.
• Copy relevant packages from kie-tools@main (POC) to kogito-images.

Merge Histories and Repositories

• Commit the copied packages in kogito-images.
• Add kogito-images as a remote in the kie-tools repository (local directory is sufficient).
• Merge with --allow-unrelated-histories to integrate kogito-images into kie-tools.
• Open Pull Request for kogito-images Migration

Open a PR in incubator-kie-tools for the merged changes.

• Ensure proper documentation and review notes are included.
• CI Integration and Testing for kogito-images

Review the CI configuration in incubator-kie-tools.

• Ensure the newly integrated packages are correctly tested and validated in the CI pipeline.
• Close PRs and Fix End-to-End Tests for kogito-serverless-operator
• Review and close all open PRs in the kogito-serverless-operator repository.
• Investigate and fix any issues in the end-to-end tests to ensure complete test coverage.

Migrate kogito-serverless-operator

• Repeat the migration steps (branch creation, package deletion, copying, and merging) for the kogito-serverless-operator repository.
• Follow the same process as used for kogito-images.

Final CI Validation and Cleanup

• Evaluate the entire CI pipeline after both migrations.
• Identify and fix any CI issues, ensuring all workflows are functional.
• Review the migration and validate the final setup, ensuring all packages and history are successfully transferred.

Kogito Images and Operator Sunset

• Properly communicate with the Apache community about the upcoming changes in those repositories
• Ask Apache Infra to archive the repositories

Related tasks

• Kogito Images migration to kie-tools #2604
• Remove kogito-images from Jenkins automations for main (10.1 and beyond) #2618
• Adapt Jenkins release automations to include all kogito-*-image packages from kie-tools #2620
• SonataFlow Operator migration to kie-tools #2605
• Remove kogito-serverless-operator from Jenkins automations for main (10.1 and beyond) #2619
• Stop cloning and building kogito-apps during kogito-*-image packages build scripts on kie-tools #2621
• Archive kogito-images and kogito-serverless-operator repos #2622
• Parameterize Quarkus version with $(build-env quarkus.version) on all kogito-*-image packages on kie-tools #2623
• Publish an initial version of the KIE Tools user manual #2624
• Run E2E tests that do not use network on macOS for CEKit-based images on kie-tools #2631
• [SonataFlow] Migrate DBMigration Image from SonataFlow operator repository to kie-tools #2659