 -Integrate_Pass(1)

NAME
-Integrate_Pass - pass a change integration

SYNOPSIS
-Integrate_Pass [ option... ]
-Integrate_Pass -List [ option... ]
-Integrate_Pass -Help

DESCRIPTION
The -Integrate_Pass command is used to notify that a change has passed integration. The change is advanced from the being integrated state to the completed state.

This command updates the file histories, so that future aecp(1) commands may extract previous file versions from history, and so that future aed(1) commands may merge out-of-date files. The history is updated using the history_create_command and history_put_command fields of the project config file (see aepconf(5) for more information). The integrate pass will abort with an error if one of these history commands should fail, e.g. by running out of disk space. If this should happen, the change will remain in the being integrated state, and the integration directory is unaltered.

Once the history has been updated, the integration directory is renamed as the baseline directory, and the old baseline directory is deleted.

Once integrate pass is complete the change is no longer assigned to the current user.

  History Tools Modify Files
Many history tools (e.g. RCS and SCCS) can modify the contents of the file when it is committed. This usually requires the use of specific ``keyword'' strings, and there are usually options to turn this behavior off, but users familiar with version control tools (as opposed to configuration management systems) will often use these features. The problem is that if the commit changes the file, the source file in the repository now no longer matches the object file in the repository. I.e. the history tool has compromised the referential integrity of the repository. By default, a fatal error is emitted if the file is changed by the check-in, however this can be modified to a be warning or even ignored completely; see the history_put_trashes_file field of aepconf(5) for more information.

  File Modification Times
The modification times of all files modified since the beginning of integration (see aeib(1) for more information) are updated to be since the beginning of integrate pass. The order of modification times will be preserved, however the time range will be compressed to the greatest extent possible. This ensures that subsequent development builds will notice that baseline files have changed.

Note that if there are many new files with all different timestamps in the integration directory, and if the number of files with different timestamps exceeds the number of seconds since the start of the integrate-pass command, Aegis may have to set file modification times into the future.

The build_time_adjust field of the project config file controls Aegis' behavior in this case. (See aepconf(5) for more information.) There are three settings:

adjust_and_sleep
    This setting, which is the default, causes Aegis to sleep until the file modification times would no longer be in the future. This avoids both development build problems and integration build problems, both of which which can arise as a result "interesting" file modification times.

adjust_only
    Aegis will issue a warning that the file modification times extend into the future, but will not sleep. This may cause integration build problems, particularly if you are using aeintegratq(1). Development builds may perform redundant builds, however aet -reg should not produce false negatives.

dont_adjust
    This is highly inadvisable. It is provided solely for some very rare circumstances. This setting causes Aegis not to adjust the file modification times at all. This can have very unhappy side-effects, especially of the integration build was before one or more development builds; the commonest symptom being that development builds do not always cause a relink of the necessary executables, and aet -reg may give false negatives. It is strongly recommended that you do not use this setting.

If you use cook(1), see the time-adjust-back flag for how to compress the time range even further. This usually makes the sleep (or the warning period) significantly shorter.

  Notification
On successful completion of this command, after the directory rename has ocurred and after the database has been updated, the integration_pass_notify_command field of the project attributes is run, if set. See aepattr(5) and aepa(1) for more information. This command is run as the project owner.

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. The above command is passed an environment variable called AEGIS_INTEGRATION_DIRECTORY so that the appropriate symlink may be placed, if desired.

Other commands run by this command include the history_create_command, history_put_command and history_query_command fields of the project config file. See aepconf(5) for more information.

  The History Lock
Where a project has a number of branches active simultaneously, it is possible for independent integrate pass commands for different branches to be issued very close together. The is an exclusive history lock taken by integrate pass to ensure that only one branch is updating the file history at a time, thus preventing history file corruption.

OPTIONS
The following options are understood:

RECOMMENDED ALIAS
The recommended alias for this command is
csh%	alias aeipass ' -ipass \!* -v'
sh$	aeipass(){ -ipass "$@" -v}

ERRORS
It is an error if the change is not assigned to the current user.
It is an error if The change is not in the being integrated state.
It is an error if there has been no successful ' -Build' command for the integration.
It is an error if there has been no successful ' -Test' command for the integration.
It is an error if there has been no successful ' -Test -BaseLine' command for the integration.

SEE ALSO

aeib(1)
    begin integration of a change

aeifail(1)
    fail integration of a change

aemeasure(1)
    simple file metrics

aemetrics(5)
    metrics values file format

aeuconf(5)
    user configuration file format