[ 
https://issues.apache.org/jira/browse/HBASE-22852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913490#comment-16913490
 ] 

Rushabh S Shah commented on HBASE-22852:
----------------------------------------

{quote}

{{gpg --verify}} is supposed to default to checking for an artifact with the 
same name as the signature minus the "asc". are we not naming things correctly?

I *thought* that script was configured to exit on any bash expression failure, 
which should mean we exit if gpg exists with a non-success code. What's the 
exit code for that gpg failure?

{quote}

[~busbey] I think you are right on both these fronts. I was testing partial 
script. I just copied the section from cache-apache-project-artifact.sh script  
which was verifying the gpg signatures into a separate script. Sorry for the 
noise.

>  I agree on how to go about stopping the agent.

I will create a PR shortly for this. Could you guide me on how should I test 
the changes. Can I just run JenkinsFile script on my local machine and expect 
it to function properly ?

> hbase nightlies leaking gpg-agents
> ----------------------------------
>
>                 Key: HBASE-22852
>                 URL: https://issues.apache.org/jira/browse/HBASE-22852
>             Project: HBase
>          Issue Type: Bug
>          Components: build
>            Reporter: Allen Wittenauer
>            Priority: Major
>
> FYI, just triggered yetus master, which includes code to find and kill 
> long-running processes still attached to the Jenkins workspace directory.  It 
> came up with this:
> https://builds.apache.org/view/S-Z/view/Yetus/job/yetus-github-multibranch/job/master/134/console
> {code}
> USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
>  jenkins    752  0.0  0.0  93612   584 ?        Ss   Aug12   0:00 gpg-agent 
> --homedir 
> /home/jenkins/jenkins-slave/workspace/HBase_Nightly_HBASE-20952/downloads-hadoop-2/.gpg
>  --use-standard-socket --daemon
>  Killing 752 ***
> {code}
> (repeat 10s of times, which slightly different dates, pids, versions, etc)
> Also, be aware that any other process running on the node (such as the other 
> executor) has extremely easy access to whatever gpg creds you are using...



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to