Bug 141152

Description Nick Boldt 2006-05-10 16:45:42 EDT

Collecting the useful bits out of bug 85485, bug 116912 and bug 124172, here's some of the outstanding ideas 

+ add type of build to feed (milestone, I build, Nightly, Callisto milestone, RC, etc.) to facilitate watching for specific build types

+ Check upstream build's download page for additional platform versions of dependencies so that a Windows-based build can respond to the feed of a project that was built using Linux without some string magic to turn eclipse-SDK-3.2RC3-linux-gtk.tar.gz into eclipse-SDK-3.2RC3-win32.zip -- this would be much easier if instead of index.html or index.php we had index.php+index.xml+index.xsl, so we could just parse index.xml
    
+ support polling concurrent parallel build feeds, eg., EMF + GEF
    
+ support three types of upstream feed types: kick, hold, ignore
   . https://bugs.eclipse.org/bugs/show_bug.cgi?id=116912#c3
   . kick: new upstream build = new project build (eg., Eclipse -> EMF)
   . hold: no new project builds until a new upstream is available (eg., VE would see a new EMF and sit in "hold" until a new GEF was available, since it depends on both)
   . ignore: use new upstream build when it's time for a new project build, but don't use it to decide it's time to kick that new build (eg., UML2 could set Eclipse as an ignore, since it will need it but doesn't need to rebuild until there's a new EMF as well)
        
+ respond to change in downstream feed by:
   . kicking a new project build (must pass <depends> URLs to build
   . checking outcome
   . if pass:
     . update project's feed to reference newer dependencies
     . delete build
     . update project's index.html (later index.xml) dependencies
   . if fail, send email alert
        
+ allow downstream components to "vanity name" their builds using upstream component version numbers, qualifiers, or datestamps, so EMF 2.2.0.v200607081234, if it depends on Eclipse 3.2.0.v200607070000, could be renamed automatically to 
   . EMF 2.2.0.v200607070000-v200607081234

+ add checkbox for "[x] Kick Off Build Cascade When Build Completed?" on Modeling project build.php pages to cause the entire available cascade to run back-to-back?

+ mark current cron/ant thread dormant - update a property file w/ buildInProgress=true to avoid multiple overlapping builds if multiple upstream changes happen?
	
+ respawn new ant/shell task after given sleep interval <exec executable="sleep"><arg line="2"/></exec>, or just use cron with sleep?