damccorm opened a new issue, #34084: URL: https://github.com/apache/beam/issues/34084
### What needs to happen? Right now, pushing all Docker containers can take up to 6 hours and timeout the GitHub actions job to run it - https://github.com/apache/beam/actions/runs/13491768096/attempts/1 This has several downsides - obviously, this can fail, but also it slows down RC creation. We should split this up so that it can run faster. My plan to fix is: - [ ] Enable containers to easily be pushed in separate jobs via groups of containers - [ ] Cherry-pick that to the postrelease branch for 2.63 - [ ] Update the republish containers workflow to consume this and prove it works - [ ] Update the main build_release_candidate workflow to do the same ### Issue Priority Priority: 2 (default / most normal work should be filed as P2) ### Issue Components - [ ] Component: Python SDK - [ ] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [ ] Component: IO connector - [ ] Component: Beam YAML - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Infrastructure - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
