Ok, I actually got the publishing thing working. I hacked the cbi scripts to work with my buckminster produced build. If you look at the buckminster releng project in the voice tools project:
https://dev.eclipse.org/svnroot/technology/org.eclipse.vtp/Releng/trunk/org. eclipse.vtp.releng.buckminster You can see how I¹ve got that portion set up. I have a cron that runs a command like this: /opt/public/common/apache-ant-1.7.1/bin/ant -f /opt/users/hudsonbuild/.hudson/jobs/buckminster-voicetools-nightly/workspace /org.eclipse.vtp.releng.buckminster/promote.xml -Dpromote.properties=/opt/users/hudsonbuild/.hudson/jobs/buckminster-voiceto ols-nightly/workspace/org.eclipse.vtp.releng.buckminster/promote-N.propertie s -DthirdPartyJarsDir=/opt/public/cbi/build/3rdPartyJars I couldn¹t get the actual command as I can¹t seem to connecto to build.eclipse.org. Is it down right now or am I having issues? I am still using the build.eclipse.org/hudson site so there might be some rework that needs to be done. I got my stuff working and haven¹t paid attention to what¹s happened lately. There is a new dedicated hudson instance? On 9/17/10 12:20 PM, "Miles Parker" <milespar...@gmail.com> wrote: > > Hi Trip, > > This is one of those many cases where despite the advantages of Buckminster I > wish I'd stayed with the Athena approach which is very well documented and > works well using shell scripts. See for example: > http://wiki.eclipse.org/Common_Build_Infrastructure/Publishing > > But the basic issue is that we need to get nightly and interim builds > published automatically to Eclipse download servers and be able to manually do > the same with milestone and release builds. I gather that this isn't quite as > simple as it sounds, as there are issues with what you do with the existing > files, etc.. But the main issue seems to be that you can't push to downloads, > but must instead do that in bud.eclipse.org shell script. Maybe this won't be > an issue inside hudson.eclipse.org.. > > Also, while built-in hudson promote looks easy, I haven't been able to get it > working the way I'd like even on simple homegrown project and it doesn't > appear to be flexible enough to handle complexities of Eclipse style releases. > > On Sep 17, 2010, at 10:14 AM, Trip Gilman wrote: > >> Could you guys outline the promotion process you are looking for. I was >> able to get most of what I wanted for the Voice Tools Project working, but >> I'm not sure I know what you mean by promotion, so I don't know if any of it >> might be applicable to you. >> >> Trip >> >> >> On 9/17/10 12:08 PM, "Miles Parker" <milespar...@gmail.com> wrote: >> >>> >>> Yes, me too. But at this point since my hudson.eclipse.org isn't working I'd >>> like to get it working anywhere.. without this our users aren't able to >>> actually install any of the fixes we've made in last two or three months. >>> Help >>> would be greatly appreciated. >>> >>> On Sep 17, 2010, at 12:54 AM, Stéphane Bouchet wrote: >>> >>>> hi, >>>> >>>> i am facing the same issue, i will be glad to have some info, too :) >>>> >>>> in other hand, i am focusing of getting this done in hudson.eclipse.org, >>>> not >>>> in "old" build.eclipse.org >>>> >>>> >>>> Le 16/09/2010 19:45, Miles Parker a écrit : >>>>> Hi all, >>>>> >>>>> I'm trying to figure out how to get a good promotion going now that I've >>>>> managed to get the transition to Buckminster working. Basically I'd just >>>>> like a one for one swap with the prior CBI functionality, but it isn't >>>>> clear >>>>> how that should happen. I know that XText was experimenting with a >>>>> buckminster based promotion scheme driven from Hudson, but I'm not sure >>>>> that >>>>> that is even possible given that hudson is not inside build firewall. I >>>>> really need to get this working.. >>>>> >>>>> thanks very much >>>>> >>>>> Miles >>>>> _______________________________________________ >>>>> dash-dev mailing list >>>>> dash-dev@eclipse.org >>>>> https://dev.eclipse.org/mailman/listinfo/dash-dev >>>>> >>>> >>>> <stephane_bouchet.vcf>_______________________________________________ >>>> dash-dev mailing list >>>> dash-dev@eclipse.org >>>> https://dev.eclipse.org/mailman/listinfo/dash-dev >>> >>> _______________________________________________ >>> dash-dev mailing list >>> dash-dev@eclipse.org >>> https://dev.eclipse.org/mailman/listinfo/dash-dev >> >> _______________________________________________ >> dash-dev mailing list >> dash-dev@eclipse.org >> https://dev.eclipse.org/mailman/listinfo/dash-dev > > _______________________________________________ > dash-dev mailing list > dash-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/dash-dev
_______________________________________________ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev