Community
Participate
Working Groups
The following crontab entry for user apache on emft.eclipse.org worked for a long time, but not in the last few weeks: 0 16 * * 2 /home/www-data/build/modeling/scripts/start_cron.sh -sub ocl -buildType I -basebuilderBranch RC2_34 -searchcvs mdt.ocl.releng -a -email "give.a.damus@gmail.com" > $HOME/cron_logs/start_cron.sh.ocl.13I.txt 2>&1 The last few weeks, changes have been released and ready to go in OCL before the 16.00 deadline, but the log file shows that searchcvs found no changes. Hence, no builds. Launching the start_cron script from a command prompt doesn't help. The Validation build is launched in similar fashion, but works. Is this because it is in the org.eclipse.emf module in CVS, instead of org.eclipse.mdt? I have to use the web page to manually build and promo OCL builds :-(
In the words of the great Neil Patrick Harris, of HIMYM fame... "Haaaave... ya met Ted*?" * - The role of Ted in this joke will be played by the following wiki page [1] as understudy [1]http://wiki.eclipse.org/Modeling_Project_Releng/Releasing/Scheduled_Releases Attach a patch to this bug for your ocl.HEAD.options.txt (and/or ocl.R12m.options.txt) and I'll stick it in CVS for you. Meanwhile, you can test it by putting it in this folder on emft.eclipse.org (or modeling.eclipse.org if you don't need UI tests): /home/www-data/build/org.eclipse.releng.tools.tagandrelease ... then editing apache's crontab with a scheduled check of CVS and subsequent build / promote.
(In reply to comment #1) > In the words of the great Neil Patrick Harris, of HIMYM fame... Thanks, Nick. I have met Ted. I just didn't think that the options.*.txt was needed by OCL as EMF Validation seems to do just fine without it.
Back to you pending a patch.
