[jbosstools-issues] [JBoss JIRA] (JBDS-4616) signed rpm fetch job should verify the rpms are signed

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493489#comment-13493489 ] 

Nick Boldt commented on JBDS-4616:
----------------------------------

Destroyed all the rhel7-devstudio-releng and the rhel7 slaves and tried again. Same error -- *NOKEY*.

https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/jbosstools-releng/job/jbosstools-releng-push-to-staging-06-sign-rpm-fetch/19/console

So, it seems the slaves don't have the key installed. :(

> signed rpm fetch job should verify the rpms are signed
> ------------------------------------------------------
>
>                 Key: JBDS-4616
>                 URL: https://issues.jboss.org/browse/JBDS-4616
>             Project: Red Hat JBoss Developer Studio (devstudio)
>          Issue Type: Bug
>          Components: build, rpm
>    Affects Versions: 11.1.0.GA
>            Reporter: Nick Boldt
>            Assignee: Pavol Srna
>             Fix For: 11.2.0.AM2
>
>
> Currently, the job that fetches the signed devstudio rpms can't automatically verify the rpms are signed because the key is not installed on the slaves.
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/jbosstools-releng/job/jbosstools-releng-push-to-staging-06-sign-rpm-fetch/11/console
> So, we need to fix that so that the job can verify signing has occurred and speed up the release process.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)