Differences

This shows you the differences between two versions of the page.

--- versioncontrol:tinderbox [2006/10/08 12:56] – add monotone section LapoLuchini
+++ versioncontrol:tinderbox [2022/10/07 01:30] (current) – Move bakeoff stuff under a single namespace KubilayKocak
@@ Line 4: / Line 4: @@
 ===== SVN Implementation =====
+The hook system should be quite sufficient to do whatever tinderbox needs.
 ===== Hg Implementation =====
+The hook system in Hg should be enough to interface it with the tinderbox.  Hooks can be plain shell scripts, python scripts (with access to internal data as Hg is in Python).
 ===== Git Implementation =====
@@ Line 12: / Line 14: @@
 ===== Monotone Implementation =====
 **Supported**
-(also see [http://venge.net/monotone/wiki/FeatureBuildIntegration monotone:[[/FeatureBuildIntegration|FeatureBuildIntegration]]])
+(also see [[http://venge.net/monotone/wiki/FeatureBuildIntegration|monotone:FeatureBuildIntegration]])
-["Monotone"] has extensive hook and trigger facilities using lua.  Monotone uses [http://venge.net/monotone/wiki/BuildBot monotone:[[/BuildBot|BuildBot]]] for its own build-testing infrastructure, integration of other systems like Tinderbox should be quite simple.
+[[/Monotone|Monotone]] has extensive hook and trigger facilities using lua.  Monotone uses [[http://venge.net/monotone/wiki/BuildBot|monotone:BuildBot]] for its own build-testing infrastructure, integration of other systems like Tinderbox should be quite simple.
-[http://venge.net/monotone/wiki/UsingCerts monotone:[[/UsingCerts|UsingCerts]]], in particular ''%%testresult%%'' certs, such QA tools can publish their results for each revision back to the distributed development community, who can then depend on these results when choosing suitable code to work with.
+[[http://venge.net/monotone/wiki/UsingCerts|monotone:UsingCerts]], in particular ''%%testresult%%'' certs, such QA tools can publish their results for each revision back to the distributed development community, who can then depend on these results when choosing suitable code to work with.