Currently, when a job is configured to check a particular AccuRev stream, every stream above that stream in the stream hierarchy is also checked for changes, all the way up to the root stream of the depot. This is to detect changes promoted into a parent stream of the build stream.

However, there are cases where checking could be stopped past a certain point. Multiple sets of streams could be placed within a single depot. In this scenario, the root stream never gets anything promoted to it, and only serves to allow sets of stream below it. An organization may choose to provide additional levels of organization below the root level (e.g. passthrough streams), which don't necessarily need to be checked for changes when determining a build.

A configuration option should be added at the job level, where the user can specify the "root" stream of the particular job. When the root stream is set, the check stream for changes process will stop at the stream with the same name when moving up the stream hierarchy checking for changes.

This will definitely be a use-at-your-own-risk feature. If a root stream is configured and legitimate changes are promoted to a stream above this stream, then these changes will not be picked up at that time. They would get picked up if other changes triggered a downstream build, assuming a merge is not needed.

Also, if the stream name specified as the root does not exist, the checking process will continue up to the actual root stream of the depot. It would be of value to put in a check when the root stream is specified to validate that it exists in the hierarchy above the job's stream.