|
NAMEaepstate - aegis project state fileSYNOPSISproject/info/stateDESCRIPTIONThe project/info/state file is used to store state information about a project.This file is maintained by aegis and thus should not be edited by humans. CONTENTS
Almost Obsolete FieldsThe following fields are obsolete. They will persist until the next aenrls(1), and the new project so generated will use them to define its default branching.
Obsolete FieldsThe following fields are obsolete. They are only present in projects which have yet to be converted to the new branch format. When Aegis sees them, they will be moved into the "trunk" transaction.
This command is used to notify a developer that a change
requires developing; it is issued when a project administrator uses an aedb
-User command to force development of a change by a specific user. All of
the substitutions described in aesub(5) are available. This field is
optional.
Executed as: the new developer. Current directory: the development directory of the change for the new developer. Exit status: ignored.
This command is used to notify that a change is ready for
review. It will probably use mail, or it could be an in‐house bulletin
board. This field is optional, if not present no notification will be given.
This command could also be used to notify other management systems, such as
progress and defect tracking. All of the substitutions described by
aesub(5) are available.
Executed as: the developer. Current directory: the development directory of the change. Exit status: ignored.
This command is used to notify that a change had been
withdrawn from review for further development. It will probably use mail, or
it could be an in‐house bulletin board. This field is optional, if not
present no notification will be given. This command could also be used to
notify other management systems, such as progress and defect tracking. All of
the substitutions described by aesub(5) are available.
Executed as: the developer. Current directory: the development directory of the change. Exit status: ignored.
This command is used to notify that a review has passed.
It will probably use mail, or it could be an in‐house bulletin board.
This field is optional, if not present no notification will be given. This
command could also be used to notify other management systems, such as
progress and defect tracking. All of the substitutions described by
aesub(5) are available.
Executed as: the reviewer. Current directory: the development directory of the change. Exit status: ignored.
This command is used to notify that a review has failed.
It will probably use mail, or it could be an in‐house bulletin board.
This field is optional, if not present no notification will be given. This
command could also be used to notify other management systems, such as
progress and defect tracking. All of the substitutions described by
aesub(5) are available.
Executed as: the reviewer. Current directory: the development directory of the change. Exit status: ignored.
This command is used to notify that an integration has
passed. It will probably use mail, or it could be an in‐house bulletin
board. This field is optional, if not present no notification will be given.
This command could also be used to notify other management systems, such as
progress and defect tracking. All of the substitutions described by
aesub(5) are available.
Some compilers bury absolute path names into object files and executables. The renaming of the integration directory to become the new baseline breaks these paths. This command is passed an environment variable called AEGIS_INTEGRATION_DIRECTORY so that the appropriate symlink may be placed, if desired. Executed as: the project owner. Current directory: the new project baseline. Exit status: ignored.
This command is used to notify that an integration has
failed. It will probably use mail, or it could be an in‐house bulletin
board. This field is optional, if not present no notification will be given.
This command could also be used to notify other management systems, such as
progress and defect tracking. All of the substitutions described by
aesub(5) are available.
Executed as: the integrator. Current directory: the development directory of the change. Exit status: ignored.
WRITING REPORT SCRIPTSWhen attempting to access these fields from within the report generator, you need a code fragment similar to the following:auto ps; ps = project[project_name()].state; When you access the branch field, you obtain access to the change state of the branch. Even the trunk has one of these, it just doesn't have a number, and it is perpetually being developed. When you index the branch.change field by a change number, you obtain access to the change state of that change. When you index the branch.src field by a filename string, you may obtain access the the relevant project file state (see aefstate(5) for more information). In addition to the above fields, the report generator inserts a name field containing the project name, and a directory field containing the project directory path. SEE ALSO
COPYRIGHTaegis version 4.25.D510Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012 Peter Miller The aegis program comes with ABSOLUTELY NO WARRANTY; for details
use the 'aegis -VERSion License' command. This is free software and
you are welcome to redistribute it under certain conditions; for details use
the 'aegis -VERSion License' command.
AUTHOR
Visit the GSP FreeBSD Man Page Interface. |