Skip to main content

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

Hi,

The main issue with Maven builds on HIPP is that, by default, HIPP doesn't have write-access to the download server for security reasons. So, some HIPP instances might not be able to use a Maven builder, whereas they could use a shell script/web service (Started from a Cron task or manually via SSH, with different permissions)

Of course, having a Maven build step that delegates to the Web service is fine, as long as we can also use the service without Maven.

There might be alternatives (e.g. specific Hudson permissions that are only enabled for identified jobs, i.e. not Gerrit ones). Not sure if this could work.

Camille

-----Message d'origine-----
De : cbi-dev-bounces@xxxxxxxxxxx [mailto:cbi-dev-bounces@xxxxxxxxxxx] De la part de Andreas Sewe
Envoyé : mardi 27 octobre 2015 14:12
À : cbi-dev@xxxxxxxxxxx
Objet : Re: [cbi-dev] Procedure to deploy to download.eclipse.org

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!

I think much of this can be tackled by Maven plugins during the build already. I can very well imagine tycho-p2-repository:archive-repository
learning to compress the update site with zx as well.

Same thing goes for mirror and stats URIs.

There is one common resource, however, which I would really like to be offered by CBI: a common index.html for update sites that adheres to eclipse.org's current theme.

At Code Recommenders we use [2] and the maven-remote-resource-plugin to copy it into place during out builds [3]. As you can see, [2] can even interpolate information from the POM, like ${project.name} or ${project.description}.

Is there any interest in picking this up at CBI? I can certainly help with the Maven-side of things (e.g., the Velocity template), but would probably need some assistance bringing this into proper corporate-design shape.

Best wishes,

Andreas

[1]
<https://eclipse.org/tycho/sitedocs/tycho-p2/tycho-p2-repository-plugin/archive-repository-mojo.html>
[2]
<https://git.eclipse.org/c/recommenders/org.eclipse.recommenders.git/tree/releng/repository-resources/resources/index.php.vm>
[3]
<https://git.eclipse.org/c/recommenders/org.eclipse.recommenders.git/tree/repositories/pom.xml#n106>

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


Back to the top