Hi Cloudberry Dev Team,
I'd like to discuss a series of planned Pull Requests aimed at implementing
Continuous Integration (CI) support for Apache Cloudberry. The changes will
be introduced incrementally across multiple repositories to establish a
robust CI pipeline.
The implementation will come in two main phases:
1. Docker Container Infrastructure (cloudberry-devops-release)
- Introducing Docker containers for building and testing Cloudberry
on Rocky Linux 9
- Publishing build artifacts to DockerHub
- Adding GitHub workflows to automate container building process
- Repository: https://github.com/apache/cloudberry-devops-release
2. CI Pipeline Implementation (cloudberry main repository)
- Implementing CI workflows for building and testing on Rocky Linux 9
- Initial focus on unittest-check and installcheck-good (with
Optimizer disabled)
- Adding new GitHub workflow configurations
- Introducing supporting CI scripts from cloudberry-devops-release
- Repository: https://github.com/apache/cloudberry
As part of this effort, we will also:
- Clean up legacy build scripts to reduce technical debt
- Evaluate moving the build scripts back to the main cloudberry
repository
The CI implementation will be actively developed over the next few months
to support our initial release processes. We'll be using simplified CI
scripts initially, with plans to expand functionality as we progress.
The current separation between devops-release and main repository allows us
to:
- Maintain clear separation of concerns
- Iterate on CI infrastructure independently
- Reduce complexity in the main repository
- Enable easier maintenance and updates of CI components
I welcome any feedback or suggestions on this approach before I begin
submitting the PRs.
Best regards,
-=e
--
Ed Espino
Apache Cloudberry (incubating) & MADlib
