[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] Procedure to deploy to download.eclipse.org

Ed,

I would be very careful before integrating the signing into this publishing service. As you know, the repack/normalize step required before signing and the pack after is very sensitive.

Also, some projects add the jars they depend on from orbit directly into their p2 repos, and we don't want these jars to be re-signed... 

I am not against the idea, but we have to think thoroughly about the potential issues. 

Cheers,
Mikael

Le 27 oct. 2015 à 14:08, Ed Willink <ed@xxxxxxxxxxxxx> a écrit :

Hi

+1

But is it similar to the jarsigner? Isn't it a replacement?

Project build produces a zipped P2 repo.
EF deployment tool signs it
EF deployment tool makes it available as a .../update/... folder
EF deployment tool makes it available as a .../download/... ZIP
EF deployment tool feeds automated PMI download pages
....
?? feeds the aggregator too ??

    Regards

        Ed Willink

On 27/10/2015 12:53, Mikael Barbero wrote:
A really nice solution would be to provide something similar to what has been done for jarsigner and other signers at Eclipse: a webservice where you can upload a zipped p2 repository along with some metadata and the service will take care of putting it right where it needs to be, create the composite, etc... It could also make some check like whether the mirrorURL is properly set, use any new compression scheme for p2 repo to reduce bandwidth consumption (like zx) etc... It could also write to information about the repo to PMI!

What do you think?

Le 27 oct. 2015 à 13:36, Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx> a écrit :

Hi,

Maybe that gives you a better start. We could also think of
contributing them to CBI, but I am not sure how „generic“ our project
deployment really is.
We're open to ideas and will welcome any contribution that can be made
generic enough for many projects to use.
FWIW, here's Code Recommenders' promotion script [1]. Based on that, I
think it will be hard to standardize on more than

 FROM=${HUDSON_HOME}/jobs/${PROMOTED_JOB_NAME}/configurations/

and

 TO=/home/data/httpd/

In particular, the paths below $FROM vary widely based on project
structure. Below $TO I think at least one level is fixed by convention,
but below that all bets are of.

That being said, I once toyed with the idea to deploy our promotion
script to repo.eclipse.org, so that our incubator projects (which
virtually use the same scripts) can re-use them using exec:exec Maven
goal, but unfortunately exec:exec doesn't search for the executable in
its dependencies (unlike exec:java).

Best wishes,

Andreas

[1]
<https://git.eclipse.org/c/recommenders/org.eclipse.recommenders.git/tree/tools/hudson/publish-repository.sh>

--
Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-170-811-3791
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev

      

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.6173 / Virus Database: 4455/10898 - Release Date: 10/27/15

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail