| Re: [incubation] Release Update Sites |
Thanks everyone, that helped a lot. I ended up configuring a Hudson job to promote an update site build to the download servers and add it to the composite update site. If someone finds this email thread again, here's a link to documentation about the Ant build file Ed mentioned: https://wiki.eclipse.org/Modeling_Project_Builds/Utilities Thanks and cheers, Christoph Daniel On 09/06/16 15:22, Ed Willink wrote: > Hi > > Automated overwriting, or rather accumulating, works fine for interim > and nightly that will get thrown away after the release is out. > > Milestones deserve better treatment so a composite of per-build repos is > good. Since milestones are only every six weeks and I want to double > check before publishing, I prefer manual addition to the composite. I > login to build.eclipse.org and use e.g. > > ant -f /shared/modeling/tools/promotion/manage-composite.xml add > -Dchild.repository=S201408191307 > > First time round you append e.g. -Dcomposite.name="OCL 6.2.0 milestones" > to define a repo title. > > Since I'm still using Buckminster, I won't recommend emulating my other > working practices. > > Regards > > Ed Willink > > > > On 09/06/2016 13:22, Christoph Daniel Schulze wrote: >> Hi everyone, >> >> the ELK project is about to push out its first release since we've >> become an Eclipse project, which I am mighty excited about. However, >> this causes me a bit of a headache as far as the proper structuring of >> our downloads area is concerned. >> >> So far, we have only pushed a single nightly built update sites to the >> build.eclipse.org servers, each night overwriting last night's update >> site. That's easy. >> >> With our proper releases, I would of course like to put each release >> update site in a separate folder (which is easy) and integrate all >> existing update sites into a compound update site (which is less easy). >> >> I already talked to Eike Stepper, one of our mentors, about this some >> months ago and he mentioned that there may already be solutions for this >> problem. I guess it shouldn't be much of a problem to write a simple >> script to generate compound update sites myself, but since each project >> runs into this I thought there may already be good implementations around? >> >> Cheers, >> Christoph Daniel >> >> >> >> _______________________________________________ >> incubation mailing list >> incubation@xxxxxxxxxxx >> To change your delivery options, retrieve your password, or unsubscribe from this list, visit >> https://dev.eclipse.org/mailman/listinfo/incubation > > > > _______________________________________________ > incubation mailing list > incubation@xxxxxxxxxxx > To change your delivery options, retrieve your password, or unsubscribe from this list, visit > https://dev.eclipse.org/mailman/listinfo/incubation >
Attachment:
signature.asc
Description: OpenPGP digital signature