damccorm opened a new issue, #26767: URL: https://github.com/apache/beam/issues/26767
### What happened? Right now, we don't have the correct secrets loaded to run `build_release_candidate.sh`. There is a ticket open with Infra right now, but for the moment we should either: 1) manually run the steps from https://github.com/apache/beam/blob/4183e747becebd18becee5fff547af365910fc9c/release/src/main/scripts/build_release_candidate.sh#L183 (just the build java artifacts section) OR 2) Fork the apache/beam repo, and do the following: - Add a line below this one https://github.com/apache/beam/blob/bbacd644f8b5c9b2cd8d412c62ed6881f1cc25f4/.github/workflows/build_release_candidate.yml#L40 with a parameter `passphrase: ${{ secrets.PASSPHRASE }}` - Add a `NEXUS_USER` and `NEXUS_PW` secret (see [info on adding secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository)) with your nexus token name and password respectively (same steps to generate as https://beam.apache.org/contribute/release-guide/#access-to-apache-nexus-repository) - Add a `GPG_PRIVATE_KEY` and `PASSPHRASE` entry corresponding to your gpg private key block. https://github.com/crazy-max/ghaction-import-gpg#prerequisites has info on generating the GPG key, PASSPHRASE is the passphrase that you made when you created your GPG key - Run the workflow from your fork This should be resolved soon ### Issue Priority Priority: 2 (default / most bugs should be filed as P2) ### Issue Components - [ ] Component: Python SDK - [ ] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [ ] Component: IO connector - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] 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]
