[Buildbot-commits] [Buildbot] #669: Clean up VC modes
Buildbot
buildbot-devel at lists.sourceforge.net
Mon Aug 9 16:57:03 UTC 2010
#669: Clean up VC modes
------------------------+---------------------------------------------------
Reporter: dustin | Owner: dustin
Type: enhancement | Status: new
Priority: major | Milestone: 0.8.2
Version: 0.7.12 | Keywords: svn hg git cvs p4 bk darcs monotone arch, ship-this
------------------------+---------------------------------------------------
Comment(by zooko):
Okay, I propose that for darcs {{{mode=clean}}} is:
1. a mode which deletes the build directory and creates a new one before
doing darcs get --lazy. This is equivalent to the current mode=clobber and
is nice and fast and clean. This mode should be the default.
and {{{mode=incremental}}} is:
3. a mode which leaves the build directory in place, equivalent to the
current mode=update. This would be a little bit faster, but not a lot, and
of course it is a lot messier. I would hope that people would not use this
mode, but I'm sure somebody will want it for good or bad reasons and we
should provide it.
The darcs-specific third option would still be very useful for people who
are debugging and wondering why their mode-1 {{{clean}}} build isn't doing
what they think it should:
2. a mode like 1. but which also passes the --no-cache option to darcs.
This would be useful only for working-around filesystem corruption or
darcs bugs. It would be ideal if it were triggerable through the web
interface so that people could try it just to check if the problem they
are seeing is due to filesystem corruption or darcs bugs. (99% of the time
this super-ultra-clean mode would yield the same results as the normal
mode 1. so then they would know to look elsewhere for the explanation of
their problems.)
I suppose it could be implemented just by coding in a darcs-specific
{{{--no-cache}}} flag to be added to the {{{darcs get}}} command.
--
Ticket URL: <http://buildbot.net/trac/ticket/669#comment:14>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
More information about the Commits
mailing list