From dc01a4db73d39c33babcb576e5517b7666288830 Mon Sep 17 00:00:00 2001 From: "Dustin J. Mitchell" Date: Fri, 1 Jul 2011 18:22:38 -0500 Subject: [PATCH] Describe property precedence explicitly Fixes #2030. --- master/docs/concepts.texinfo | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/master/docs/concepts.texinfo b/master/docs/concepts.texinfo index 3dd37bbbcae..c9680a50bce 100644 --- a/master/docs/concepts.texinfo +++ b/master/docs/concepts.texinfo @@ -718,7 +718,8 @@ BuildSteps to modify their actions. These properties, in the form of key-value pairs, provide a general framework for dynamically altering the behavior of a build based on its circumstances. -Properties come from a number of places: +Properties come from a number of places, as follows. + @itemize @item global configuration -- These properties apply to all builds. @@ -739,6 +740,10 @@ The steps of a build can set properties that are available to subsequent steps. In particular, source steps set a number of properties. @end itemize +If the same property is supplied in multiple places, the final appearance takes +precedence. For example, a property set in a builder configuration will +override one supplied by a scheduler. + Properties are very flexible, and can be used to implement all manner of functionality. Here are some examples: