clayburn opened a new pull request, #28212: URL: https://github.com/apache/beam/pull/28212
The Beam project uses a remote cache node at [beam-cache.apache.org/cache](https://beam-cache.apache.org/cache/) to reduce build time. Only builds on [ci-beam.apache.org](https://ci-beam.apache.org/) are currently able to write to the cache. As requested [here](https://github.com/apache/beam/pull/27015#issuecomment-1667925540), this PR allows the same level of access to the cache for GitHub Actions as is currently in place for Jenkins builds. This will require using a few GitHub Actions secrets in GitHub Actions workflows: - GE_ACCESS_TOKEN - An Apache organization secret that allows publishing build scans - GE_CACHE_USERNAME / GE_CACHE_PASSWORD - A Beam project secret that allows authenticating to the remote cache as a user with read/write permissions A few caveats to this PR: - GitHub Actions does not allow accessing secrets from PRs issued from forks. While a crucial security feature, it makes this PR difficult to test. It would be nice to validate against a feature branch within Beam before being merged. - The nature of authoring GitHub Actions requires quite a lot of repetition in this PR. While I do not see a better way to do this, I am certainly open to suggestions. - Future versions of Gradle Enterprise should allow us to do this in a way where we do not have to use the username/password secrets. When that day comes, we can make that update. fixes #28211 ------------------------ Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily: - [x] Mention the appropriate issue in your description (for example: `addresses #123`), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment `fixes #<ISSUE NUMBER>` instead. - [x] Update `CHANGES.md` with noteworthy changes. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). See the [Contributor Guide](https://beam.apache.org/contribute) for more tips on [how to make review process smoother](https://github.com/apache/beam/blob/master/CONTRIBUTING.md#make-the-reviewers-job-easier). To check the build health, please visit [https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md) GitHub Actions Tests Status (on master branch) ------------------------------------------------------------------------------------------------ [](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule) [](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule) [](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule) [](https://github.com/apache/beam/actions?query=workflow%3A%22Go+tests%22+branch%3Amaster+event%3Aschedule) See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more information about GitHub Actions CI or the [workflows README](https://github.com/apache/beam/blob/master/.github/workflows/README.md) to see a list of phrases to trigger workflows. -- 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]
