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

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
>
>