[
https://issues.apache.org/jira/browse/BEAM-6726?focusedWorklogId=211132&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-211132
]
ASF GitHub Bot logged work on BEAM-6726:
----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Mar/19 17:05
Start Date: 11/Mar/19 17:05
Worklog Time Spent: 10m
Work Description: adude3141 commented on pull request #8026: [BEAM-6726]
explicitly specify signing key
URL: https://github.com/apache/beam/pull/8026#discussion_r264334366
##########
File path: release/src/main/scripts/build_release_candidate.sh
##########
@@ -98,7 +105,8 @@ if [[ $confirmation = "y" ]]; then
echo "2. new rc tag has created in github."
echo "-------------Staging Java Artifacts into Maven---------------"
- ./gradlew publish -PisRelease --no-daemon
+ gpg --local-user ${SIGNING_KEY} --output /dev/null --sign ~/.bashrc
Review comment:
No. It is to ensure the key is unlocked so gpg-agent will just provide
access to the key without requesting for user input within gradle call. As
gradle is configured to shell out to gpg cli, streams get broken and no input
is possible.
And yes, this will break, if .bashrc does not exist. But the same pattern
was used before [1], so I just reused that.
Of course, we might reconsider that.
[1]
https://github.com/apache/beam/blob/master/release/src/main/scripts/verify_release_build.sh#L140
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 211132)
Time Spent: 2h 50m (was: 2h 40m)
> Gradle Publish fails with Gradle 5
> ----------------------------------
>
> Key: BEAM-6726
> URL: https://issues.apache.org/jira/browse/BEAM-6726
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Affects Versions: 2.11.0
> Reporter: Ahmet Altay
> Assignee: Michael Luckey
> Priority: Blocker
> Fix For: 2.12.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> cc: [~alanmyrvold] [~kenn]
> :beam-sdks-java-bom:signMavenJavaPublication task fails with an obscure
> error:
> (https://scans.gradle.com/s/mcbb4axlx6agy/failure?openFailures=WzBd&openStackTraces=WzFd#top=0):
> Duplicate key pom-default.xml.asc:xml.asc:asc:null (attempted merging values
> Signature pom-default.xml.asc:xml.asc:asc:null and Signature
> pom-default.xml.asc:xml.asc:asc:null)
> Downgrading to Gradle 4 by reverting
> https://github.com/apache/beam/commit/cadb6f7fabc6faedc6037104338306688f17652f
> works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
