Currently, the Camunda BPM Docker images are maintained by the infra team. As discussed with the team, the maintenance will be done by the Platform team from Q1/2021 on.

Todo:

• Add scope and steps to take over maintenance as discussed during kick-off meeting with infra team.

Ideas what we should do/change during the codebase takeover:

• In INFRA-638, some improvement ideas were formulated
• Close github issues (respond to all open tickets; convert as necessary to CAM issues; disable github issues after 1-2 weeks of notice)
• Merge codebase with mono repos for CE and EE, enables
  • Building and releasing the images easily as part of the regular Jenkins CI/release pipelines
  • Building snapshot images of the actual latest snapshot of the codebase
  • Simplified development process, less individual PRs, less potential problems due to snapshot synchronization
  • Clear separation of EE and non-EE aspects; no EE code in publicly available repository
  • Probably also resolves the problem in INFRA-1956, i.e. no longer needed to make an extra manual step after releases
• Investigate and potentially adopt technologies closer to those that the automation platform team is familiar with (e.g. use a Maven plugin to trigger the building of the images: https://github.com/fabric8io/docker-maven-plugin)