Subject: Re: [cross-project-issues-dev] signing question |
From: Denis Roy <denis.roy@eclipse.org> |
Date: 01/04/2013 10:13 AM |
To: cross-project-issues-dev@eclipse.org |
Scott Lewis <slewis@composent.com> wrote:
Hi Folks,
Until recently, (ECF) has been signing our plugins by 'pushing' our
plugins to eclipse.org (built on our own builder machine...which is
*not* running at eclipse.org). Apparently this is not the appropriate
way now...rather what Denis indicated was appropriate was to have an
eclipse.org machine 'pull' our unsigned plugins, sign them, and then put
the signed versions somewhere.
I assume that other projects do some/all of their build on non-eclipse
systems...and need to do this as well. Are there ant scripts and/or
documentation on this 'pull' approach for signing?
I'm puzzled by the idea of a machine at eclipse.org pulling from a build machine running, for example, behind a corporate firewall. Maybe someone could clarify what Denis might have been meaning.
Thanksinadvance,
Scott
fyi Virgo milestones and releases are built on non-eclipse systems. Virgo's signing scripts, which are using the "push" model, were added recently in this commit:
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev