[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| Re: [cbi-dev] Procedure to deploy to download.eclipse.org | 
| Hallo Francois, 
 I changed the rights within the job config, so you should now be able to read it. The answer to your question is that the job is parameterized, i.e. there are job parameters matching the command line parameters: 
  The job forwards the parameters to the shell script: 
 
 The job is also scheduled so we can automatically publish integration builds once a week: 
 
 And it uses the build name plug-in so we can later see what was promoted: 
 
 I apologize the screenshots are in German, but I do not know how to turn of the hudson localization. 
 Cheers Alexander 
 
 _______________________________________________cbi-dev mailing listcbi-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/cbi-devAlexander, Thanks you for sharing your script. I will look at it precisely.   But I do not understand the relationship with the promotion job. I have cliked on the Hudson link. I am not able to see the configuration of the job.   You call it as a shell script? But how do you fill the parameters  in the Hudson job?     Thanks again     Hi Francois,  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.Alexander     Thanks for your quick answer.So if I do understand from your answer and examples that I have find across several projectsI have 3 solutions, I could:1.       Add a shell command task in my Hudson job2.       Add a maven plugin (ant) in the normal build process3.       Add shell command that are deployed as a cron on the download.eclipse.org server; that is in charge to retrieve the build artifactsAny idea what is the best approve between the 3 solutions?It is strange that there is no official shell script that make the job for any eclipse project.This script could define the official process in term of naming convention etc… It seems that every project has its own scripts…Any idea if there is an official Maven/ Tycho plugin that could take all of this in order to standardize the way eclipse projects publish their artifacts?Hi,
 On 10/26/2015 06:38 PM, LE FEVRE FRANCOIS wrote:
Could you give advice / best pratices to deploy directly from the HIPP instance to the download area?Is there any maven plugin? With a dedicated profile ?
  --Dr. Alexander Nyßen
 Dipl.-Inform.
 Principal Engineer
 
 Telefon: +49 (0) 231 / 98 60-202
 Telefax: +49 (0) 231 / 98 60-211
 Mobil: +49 (0) 151 /  17396743
 
 http://www.itemis.de
 alexander.nyssen@xxxxxxxxx
 
 itemis AG
 Am Brambusch 15-24
 44536 Lünen
 
 Rechtlicher Hinweis:
 
 Amtsgericht Dortmund, HRB 20621
 
 Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter, Sebastian Neus
 
 Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer Fiorentino
 
 
 
-- Dr. Alexander Nyßen Dipl.-Inform. Principal Engineer Telefon: +49 (0) 231 / 98 60-202 Telefax: +49 (0) 231 / 98 60-211 Mobil: +49 (0) 151 /  17396743http://www.itemis.de alexander.nyssen@xxxxxxxxx itemis AG Am Brambusch 15-24 44536 Lünen Rechtlicher Hinweis: Amtsgericht Dortmund, HRB 20621 Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter, Sebastian Neus Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer Fiorentino | 
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail