Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Signing on hudson

I have it running as a job on hudson.eclipse.org where it builds out
the p2 repos and then does the whole packing/signing/packing/fix
artifacts.xml process.  The with a bit of antrun I publish it to a
development directory on download.eclipse.org which i can rename into
a stable release if it tests out cleanly.  This is working for both
the jetty-bundles-7.x and jetty-wtp p2 repositories.  At one point I
had it working for a local build that would use wagon to move the
payload back and forth for the signing process but I removed all that
functionality or at least don't use it anymore...it just works locally
to the build machine now where that signing shell script is.

I'll note that if you want to call the signing script yourself you
need to talk to the webmasters and get put on a special list...not if
your using the build server to call it though, build server process
has permissions.

cheers,
jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx



On Sun, Dec 12, 2010 at 19:34, Pascal Rapicault <pascal@xxxxxxxxxxxx> wrote:
> Thx for the link Jesse, just to be sure, can this task be executed from hudson and manage the signature on the appropriate server?
>
> On 2010-12-10, at 11:33 AM, Jesse McConnell wrote:
>
>> jetty uses a maven signing plugin that worksfor us...its ugly but lets
>> us generate and deploy signed p2 repositories that are built on the
>> build machines
>>
>> http://svn.codehaus.org/jetty-contrib/jetty/branches/jetty-7/eclipse-signing-maven-plugin/
>>
>> usage is here: http://dev.eclipse.org/viewsvn/viewvc.cgi/jetty-wtp/trunk/org.eclipse.jst.server.jetty.site/pom.xml?view=markup&root=RT_JETTY
>>
>> cheers,
>> jesse
>>
>> --
>> jesse mcconnell
>> jesse.mcconnell@xxxxxxxxx
>>
>>
>>
>> On Fri, Dec 10, 2010 at 10:27, Kim Moir <Kim_Moir@xxxxxxxxxx> wrote:
>>> Pascal,
>>>
>>> We committers never have access to the signing certificates, on hudson or
>>> eclipse.org servers.  Signing is a black box.  We just put the zipped file
>>> of the bundles to be signed in a project specific location and invoke the
>>> signing script.  You can poll the output directory for the signed file and
>>> copy it over to the hudson workspace once it's available.
>>>
>>> For example, you can see how we sign via hudson by looking at the
>>> signMasterFeature target in org.eclipse.releng.eclipsebuilder/buildAll.xml.
>>>
>>> Kim
>>>
>>>
>>>
>>> From:        Pascal Rapicault <pascal@xxxxxxxxxxxx>
>>> To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
>>> Date:        12/09/2010 07:47 PM
>>> Subject:        [cross-project-issues-dev] Signing on hudson
>>> Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx
>>> ________________________________
>>>
>>>
>>> Hi,
>>>
>>> What is the reason for the signing certificates to not be available on
>>> hudson?
>>>
>>> PaScaL
>>> _______________________________________________
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>>
>>>
>>> _______________________________________________
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>>
>>>
>> _______________________________________________
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>


Back to the top