Description Michal Ruzicka 2010-08-18 10:49:03 EDT

+++ This bug was initially created as a clone of Bug #309151 +++

Integrate the following text documenting the tagging support (implemented as part of bug #309151) into the Bucky book:

Tagging support in Buckminster is implemented by the "buckminster.tag" actor.
It is used from CSPEC/CSPEX files like this:
<cs:actions>
  <cs:public name="tag" actor="buckminster.tag">
    <cs:actorProperties>
      <cs:property key="tag" value="build_${build.id}" />
      <cs:property key="exclude.0" value="^org\.example\.library(?:\..+)?$" />
      <cs:property key="exclude.1" value="^org\.example\.test(?:\..+)?$" />
      <cs:property key="include.0" value="^org\.example\.library\.extensions(?:\..+)?$" />
    </cs:actorProperties>
  </cs:public>
</cs:actions>

where:
  "tag" property defines the tag to use when tagging the resources
  "exclude.<n>" properties define regular expression patterns denoting components to exclude from tagging (components which names match the pattern won't be tagged unless they also match some of the "include.<n>" pattern)
  "include.<n>" properties define regular expression patterns denoting components to include in the tagging operation regardless of if they are match any number of "exclude.<n>" patterns

The tagging is performed on the current component (the component in which the
CSPEC or CSPEX file containing the tagging action definition - similar to the one above - is found) and all its dependencies (even transitive) which happen to be present in the workspace.

Notes:
- the tagging is currently only supported for components shared in CVS repositories
- the tagging action naturally requires write (commit) privileges in the repositories where the components to be tagged are shared