Active item revisions prevent situations where the latest revision at a build stage is not the latest revision further along a search path. For example, assume that you have two revisions of the same item, foo.c-2 and foo.c-3. You action both item revisions to the UNIT TEST build stage, and then action foo.c-3 only to the SYSTEM TEST build stage. foo.c-3 is the latest revision of the item and is the active item revision at both the UNIT TEST and SYSTEM TEST build stages. Because foo.c-2 is an earlier revision of the item it is inactive at the UNIT TEST build stage and is not exported to UNIT TEST build areas.
Both item revisions at UNIT TEST (active item shown in bold):
|
Build stages |
Items and revision numbers |
|
|
UNIT TEST |
foo.c-2 |
foo.c-3 |
foo.c-3 actioned to SYSTEM TEST (active item shown in bold)
|
Build stages |
Items and revision numbers |
|
|
UNIT TEST |
foo.c-2 |
|
|
SYSTEM TEST |
|
foo.c-3 |
: