I use a shell script to auto-regen composite*.xml files in folder with N or more children in that folder.
It's a bit confusing to set up (even with inline examples) but I'd like to port it to work on eclipse.org infra so it can be run in a Jenkins job. Here's the shell script: https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/cleanup/jbosstools-cleanup.sh#L265 There's also the WTP approach, for explicitly listing children to be included in a composite site: https://wiki.eclipse.org/WTP/Releng/Processes#Release_latest_stable_build_to_.2Fwebtools.2Frepository Or for copying the latest I build into a latest/ folder, so no symlinks or composite*.xml are needed: http://git.eclipse.org/c/webtools/webtools.releng.git/tree/releng.control/promote.sh#n354 Anyway, if one of those approaches is helpful to anyone, there's the sample code. On Wed, Mar 14, 2018 at 1:22 PM, Denis Roy <[email protected] > wrote: > > IIRC for people looking to adopt this within their own project, you > can't have links in download.eclipse.org because they don't mirror > properly, so you need composite xmls/jars in the latest directory (as > Ed's EMF example does). > > > +1 thank you for understanding and working around the (unfortunate) > constraint. > > Denis > > > > > > > Jonah > ~~~ > Jonah Graham > Kichwa Coders Ltd.www.kichwacoders.com > > > On 14 March 2018 at 14:14, Ed Merks <[email protected]> <[email protected]> > wrote: > > Hi, > > I wanted to make a suggestion to the folks maintaining update sites > ondownload.eclipse.org. Of course almost all projects provide various > composite p2 repositories for different "build qualities" such as releases, > milestones, integration, stable, and nightly builds. Even when well managed > though, these repositories can grow to include a significantly large number > of child repositories. We often use such composite repository URLs in our > builds, target platforms, and Oomph's targlets, but in most cases, we're > really only interested in the latest version of each installable unit for > some specific build quality. I.e., in most cases we'd be better off if each > of such composite had a corresponding "latest" composite that pointed to a > single simple repository containing the latest release, milestone, > integration, stable, or nightly build. Not only would this make builds and > target platforms resolution faster, download.eclipse.org would be better > utilized by serving only content and artifact metadata for the composite and > for the single simple repo, rather serving n + 1 of these where n can tend > toward umpteen, e.g., as > inhttps://bugs.eclipse.org/bugs/show_bug.cgi?id=532213 where the composite > contains 211 repos. As an existing > example,http://download.eclipse.org/releases/latest points to the latest > release, > although it currently points to a composite that in turn contain 3 releases > (which is kind of fishy because there are more releases of Oxygen than are > included in the composite). > > Please consider providing such a convenience to your consumers and please > consider using them if/when available; the download.eclipse.org server will > thank you by providing better performance. If you're depending on EMF, EMF > is already provides a "latest" for each of its > composites:http://download.eclipse.org/modeling/emf/emf/builds/index.html > > Regards, > Ed > _______________________________________________ > cross-project-issues-dev mailing [email protected] > To change your delivery options, retrieve your password, or unsubscribe from > this list, > visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > _______________________________________________ > cross-project-issues-dev mailing [email protected] > To change your delivery options, retrieve your password, or unsubscribe from > this list, > visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > -- > *Denis Roy* > Director, IT Services > Eclipse Foundation, Inc. -- http://www.eclipse.org/ > Office: 613.224.9461 x224 <(613)%20224-9461> (Eastern time) > [email protected] > @droy_eclipse > > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > -- Nick Boldt Senior Software Engineer, RHCSA Productization Lead :: JBoss Tools & Dev Studio IM: @nickboldt / @nboldt / http://nick.divbyzero.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @ @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.facebook.com/RedHatInc> <https://www.facebook.com/RedHatInc> “The Only Thing That Is Constant Is Change” - Heraclitus
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
