#669: Clean up VC modes
------------------------+---------------------------------------------------
Reporter: dustin | Owner: dustin
Type: enhancement | Status: new
Priority: critical | Milestone: 0.8.0
Version: 0.7.11 | Keywords:
------------------------+---------------------------------------------------
Per an IRC conversation with ddunbar and dsal, there are really only two
things users want to do with VC steps:
* incremental updates/builds
* full, clean builds
Different VC's can implement these options with varying degrees of
reliability. What is now mode=copy works well for every supported VC
*except* CVS, so mode=clobber is only really useful for CVS. Bug #632 was
about a more efficient way to implement clean builds in git, that was
incorrectly filed under mode=update, because it's not really a copy.
So the proposal is to have only *two* modes, common across and supported
on all VCs:
* clean
* incremental
These will be specified with the mode= parameter. VCs can then have extra
options to specify the implementation of that particular method. So Git
might have mode="incremental", incremental_by="clean" *and*
mode="incremental", incremental_by="copy".
Let's get this in the 0.8.0 release, since it's a pretty big behavior
change (although it can be written in a backward-compatible fashion)
--
Ticket URL: <http://buildbot.net/trac/ticket/669>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
