Comments on: A Continuous Integration Tool is not a Build Platform

By: igorbrejc.net » Fresh Catch For January 21st

igorbrejc.net » Fresh Catch For January 21st — Wed, 21 Jan 2009 18:04:35 +0000

[...] A Continuous Integration Tool is not a Build Platform – Renaissance Developer via The Build Doctor [...]

By: Maggie’s Blog » Blog Archive » Sonic Core Xite-1 - Bleepology

Maggie’s Blog » Blog Archive » Sonic Core Xite-1 - Bleepology — Wed, 21 Jan 2009 10:53:10 +0000

[...] A Continuous Integration Tool is not a Build Platform … [...]

By: Joe

Joe — Wed, 21 Jan 2009 08:47:09 +0000

Quite right, sir! In this particular case, the build requires the list of modified files, which can be obtained from perforce. There is a relatively flat file structure, and so we only really want to build the files that have been modifed (and files that are dependant upon those). The CC plugin had that information, which is why it is easy to see why it could be the first place to look. However, I think it is reasonable to obtain the same information from either the perforce tasks in Ant, or use the p4.jar from Perforce.

Cheers,
Joe

By: Jeffrey Fredrick

Jeffrey Fredrick — Wed, 21 Jan 2009 06:56:37 +0000

Hi Joe!

Sounds like in this case maybe you could have a plugin that set properties based on the modifications and then your build script logic could do the right thing based on those properties?

Jtf