[ 
https://issues.apache.org/jira/browse/SOLR-13582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Rowe updated SOLR-13582:
------------------------------
    Summary: Ref guide build script: always check for and download public keys 
used to verify RVM distribution signature  (was: Ref guide build script: always 
check for and download public keys used to verify RVM distributiion signature)

> Ref guide build script: always check for and download public keys used to 
> verify RVM distribution signature
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-13582
>                 URL: https://issues.apache.org/jira/browse/SOLR-13582
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Steve Rowe
>            Assignee: Steve Rowe
>            Priority: Minor
>
> The 8.x ref guide builds are running on a Jenkins node they've never run on 
> before: "websites2". As a result, the public keys used to verify the RVM 
> distribution are not on the machine, and when the RVM bootstrap encounters 
> this problem, it fails the build.
> In the past I've modified the Jenkins job config to download the public keys, 
> triggered a run to download the keys, and then commented out the key download 
> lines in the job config's build script.
> This issue is intended to permanently solve the problem by adding the 
> following to our build script 
> ({{dev-tools/scripts/jenkins.build.ref.guide.sh}}), to avoid manual 
> intervention when new nodes are added in the future:
>  * If {{gpg}} is installed:
>  ** If the keys needed to verify RVM distribution signature are not available:
>  *** Download the keys



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to