Red-Dot Summary and Tag Collector

To access the Red-Dot Summary and Tag Collector for a top-level release from the Release Manager's Overview page:

  1. Select an RM-Tracked Checkout Package (EngineeringModel, GlastRelease, or ScienceTools).
  1. Click on any version (e.g., GlastRelease v6r8 or v7r0p3)

The Summary Page for that version will be displayed, and a Red-Dot Summary link will appear on the blue navbar at the top of the page:

  1. Click on the Red-Dot summary link.

Note: Regardless of the version specified in step 2, the Red-Dot Summary always displays the package versions for the current top-level released version, the last or currently running HEAD version, and the last or currently running LATEST version.

Red-Dot Summary

The Red-Dot Summary:

  • Lists all constituent package included in the current top-level Release version, the current Head build, and the Latest build.

  • Flags any error packages with a red:

    C (Checkout error)

    O (Compile error)

    T (Test error)

  • Flags new constituent packages by displaying them in a cell with a lighter-shaded background.

View Hidden and/or Old Tags
  • By default, the New Head Version of each constituent package is displayed on the far right.

These defaults are the only versions available on the pull-down menus unless you click on the View Hidden and/or View Old Tags Yes/No toggles:

 

 

Tag Collector

The web interface for the Tag Collector is disabled. Until it is restored, run the following Perl scripts from the Unix command line.

Scripts are located in: afs/slac.stanford.edu/u/gl/glast/infraBin/ReleaseManager/

buildLocation.pl Usage buildLocation.pl [options]
option:
--tag The tag for the build.
--version The version for the build.
--package The package for the build.
deleteBuild.pl Usage deleteBuild.pl [options]
option:
--tag The tag of packages to delete. For example: rh9_gcc32
--package The packages to be deleted.
--component The components to delete. Default: all
Possible values: build, html, documentation, source, all
--version The versions to delete.
Either a specific version or HEAD, LATEST, Release.
Need --oldest option if specific version isn't specified
--oldest The number of oldest builds to delete from the categories specified in --version
--force Don't ask for confirmation. Just erase the builds
setStatus.pl

Usage setStatus.pl [options]
option:
--tag The tag to apply status to. For example: rh9_gcc32
--status The status to apply. Default: Stopped.
Allowed Values: Stopped, Running
tagCollector.pl Usage tagCollector.pl [options]
option:
--command The action to perform. Default: change
Possible values change, add, remove
--package The package to modify. For example: G4Generator
--version The version for above mentioned package.
--copackage The checkout package to apply changes to.
For example: GlastRelease
--branch The branch to apply changes to. Default: latest
Possible values latest, head, release
trigger.pl Usage trigger.pl [options]
option:
--tag The tag to use for the build. For example: rh9_gcc32
--package The package to build. For example: GlastRelease
--version The version of the package to build. For example HEAD1.123
--build The environment to build on. Default value of "" is linux.
Other values are windows, mac

Tag Collector Web Interface

The basic function of the tag collector is to promote packages to LATEST or HEAD status in a controlled manner.

From the tag collector GUI, you can:

  • Add a new tag into release software
    (Package must already be checked in to CVS)
  • Change a tag
  • Remove a tag
  • Include Comments

After you have entered the information, click on Submit Changes (lower right corner); a request for a new LATEST or HEAD build will be added to the RM queue.

Note: The RM checks for new build requests every 15 minutes (approximately).

 

 

Last updated by: Chuck Patterson 04/06/2007