For All of these tasks you need to be logged into the system and also have the required privileges. If you don't you need to ask Navid to set the appropriate permissions in the database.

• Deleting a build
  To delete a build simply click on the Delete link in the top navigation bar. This will take you to a page with details of what to delete. The search criteria can be what type of Checkout Package to delete, a specific version or several version types, certain tags, and which components to delete. Before a deletion occurs, a confirmation page is displayed with a list of all the builds that will be erased. Several aspects of a build can be erased.
  • Build
    This will erase the build itself from the filesystem. It will however leave support files (such as build logs, installer information, source distribution, database entries) intact.
  • Log Files
    This will erase the build logs.
  • Doxygen
    This will erase any doxygen documentation that might have been created for this build
  • Source File
    This will erase the source distribution files.
  • Database Entry
    This will erase all the information about the build from the database including all of the above. Currently the installer information is kept although this will not be the case in the future.

• Triggering a build
  To trigger a build simply click on the Trigger link in the top navigation bar. This will take you to a page that requests which Checkout Package, which version, and which tag you wish to compile. It is important that these fields are filled out correctly otherwise the RM will fail building anything. The Checkout Package field should correspond to the Checkout Packages ( GlastRelease, ScienceTools, and EngineeringModel at the time this was written). The version field should correspond to the verison you wish to compile. There are three different version formats
  • Regular release
    These are of the format v1r2p3. They correspond to the tags given to the Checkout Package requirements file in CVS.
  • HEAD builds
    These are of the format HEAD1.123. The number 1.123 correspond to the revision number of Checkout Package requirements file in CVS. The text HEAD is appended to differentiate it from the LATEST build explained next.
  • LATEST builds
    These are of the format LATEST1.123. The number 1.123 corresponds to the revision number of the file located in CVS under ReleaseManager/src/branches. Each Checkout Package will have their own file in that location in CVS if that Checkout Package is performing LATEST builds (at the time of this writing EngineeringModel does not have such a file).

• Restarting a build
  Restarting a build is simply a matter of erasing the database entry of the build and triggering it again. However, there needs to be a waiting period between deleting a build and restarting it. The reason for this is that LSF scheduling will not erase the build instantly. Should the triggering happen prior to erasing (due to usage of different queues) then the new build will be erased by the delete of the old build. There is currently no notification of when a build has been erased so waiting an hour after erasing a build before starting a new build is recommended.