gerlowskija commented on PR #2125: URL: https://github.com/apache/solr/pull/2125#issuecomment-1850287249
> Does anything test this, or must it be manually inspected? I've been validating using the `buildAndPushRelease.py` script, paired with the smoketester. As far as I know we don't have anything else around that validates our build/release automation itself? This is one of the reasons I volunteered to be a possible RM over in `dev@`; I'd hate for something to go wrong and leave someone else on the hook for it. ---- Actually, finding the right invocation of `buildAndPushRelease.py` was a bit of a pain, so I'll share it here just in case it helps anyone that wants to validate or stumbles across a need down the road... ``` $ echo "foo" | gpg --detach-sign --use-agent --pinentry-mode loopback --local-user <keypair-fingerprint> $ python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local <some-output-dir> --rc-num 1 --mf-username gerlowskija --sign <keypair-fingerprint> --gpg-pass-noprompt ``` The first command sets up gpg-agent to delegate your password when buildAndPushRelease.py asks for it. It should prompt you for your password and then you're free to go "get some coffee", as the releaseWizard puts it. -- 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: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
