I'm in a ISO meeting so I don't have much time,
...and then goes on to propose a new algorithm that causes the integration to try to "back-off" until something builds ;)
get latest B build it if successful { get latest A build it against latest B if successful { // do nothing since everything is cool } else { send email... } } else { get B that A says it depends on (out of timestamp) build it if successful { get latest A build it against dependent B if successful { send email... ) } else { send email... ) } else { send email... ) } }
[snip]
Comments?
Kinda off-topic, but it occurs to me that Depot Version could use essentially the same algorithm to handle versioning.
Project A says it needs Project B version 1.5 or better. So try with the latest B... follow the algorithm above - the algorithm is the same but the actions are different. Version would just get the Jar, not try building from scratch and instead of sending emails, would simply back-off to older versions (but always 1.5 or better) and try again. The question is, is there a way that Depot and Gump could share an implementation of the algorithm, given that at the moment Depot uses exclusively Java and Gump is moving to exclusively Python?
I ask here and don't copy the Depot list because It seems to make sense for Gump to take the lead if code were to be shared and because I know that some of the Depot coders hang out here.
-- Michael
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
