[jbosstools-issues] [JBoss JIRA] Commented: (JBDS-221) eclipse update manager for JBDS

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBDS-221:
---------------------------------

> This ticket contains two different requests which are handled by 2
> different team.  I cannot split or clone this ticket.

As requested, I split the ticket into 

[redhat.com #1001109] please install rpm-sign on Hudson slaves soavmg2, soavmg3, soavmg6

and

[redhat.com #1001114] please set up kerberos on Hudson slaves soavmg2, soavmg3, soavmg6

... then with perfect comedic timing, I was told:

> Hi Nick - We'll be handling the ticket, so there's no point in splitting
> it up.  I'm merging back into #1000278.

Meanwhile, I've also been told that hudson isn't secure enough, so we're pwned atm:

> For signing, we need to use systems that are secured.  At a minimum this
> means access only by those that will be doing the signing, corp kerberos
> authentication and strictly limited root access.  As you know, the build
> systems aren't up to those standards so we'll need to find an alternative.


> eclipse update manager for JBDS
> -------------------------------
>
>                 Key: JBDS-221
>                 URL: https://jira.jboss.org/jira/browse/JBDS-221
>             Project: Developer Studio
>          Issue Type: Sub-task
>          Components: Build
>    Affects Versions: LATER
>            Reporter: Max Rydahl Andersen
>            Assignee: Nick Boldt
>            Priority: Blocker
>             Fix For: 2.0.1, 2.1.0
>
>         Attachments: tasktop-signup-1.png, tasktop-signup-2.png, tasktop-signup-3.png
>
>
> requires update manager to support password protected content.
> Need to verify that the info in the following thread is correct: http://dev.eclipse.org/newslists/news.eclipse.tools/msg49329.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira