THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
This section describes the naming scheme and location for publication of the containers.
Proposed repository
...
We propose to use gcr.io/beam, created under apache-beam-testing project, artifacts accessible publicly. SDK Harness containers go to sdk folder.
Things to know about gcr.io:
- Quotas:
- ?
- Permissions:
- download access - public
- publish - limited to authorized accounts that have correct permissions under apache-beam-testing:
- publishing the snapshots nightly might be feasible similar to how we currently publish nightly maven snapshots, by creating a Jenkins job;
- publishing at release time can be another Jenkins job that is triggered manually by the release owner;
- what's the process of triggering a job in such case?
- GCP Project:
- apache-beam-testing
- Troubleshooting:
- If something goes wrong with the release process:
- ping dev@ ?
- If something goes wrong with a customer pipeline from using the prebuilt images:
- ping dev@ ?
- If something goes wrong with the release process:
Proposed naming and tagging scheme
...
| Naming | Tagging | Example | |
|---|---|---|---|
| Snapshot imageimages | language + language_version | yyyymmdd_{status} in UTC | gcr.io/apache-beam-testing/beam/sdk/snapshot/2019/08/20/java:20190820_verified |
| Release images | language + language_version (Java and Go go without language version until we support multi versions.) | Beam release version | gcr.io/apache-beam-testing/beam/sdk/release/python2.7:2.10.1 gcr.io/apache-beam-testing/beam/sdk/release/java:2.10.1 |
...