Activity Plug-in

Description

Update from CA SCM

This activity takes updates from the CA SCM file repository and applies them to the file system. This activity usually occurs at the start of a Workflow before other activities are conducted.  The activity contains fields for broker name, user name, password, view path, project, state, and client path.

CA SCM Bill of Material Report

This activity provides a CA SCM Bill of Materials report.  If the same Workflow has been run against the same source control module before, this activity will also provide a CA SCM Differences report. This activity should be one of the first activities defined in a Workflow because it takes a “snapshot” of the Build Directory for analysis and comparison with other iterations of a Workflow.  The activity contains fields for many Workflow-specific parameters that are set by default to the corresponding activity macros. The only parameter that will typically require attention is the field that indicates whether the Workflow is public or private.  Public Workflows need the “–lp” flag; private Workflows take no flag.

Execute Meister Incremental Build with CA SCM Audit

This activity runs an incremental build while auditing all files used in the build, exposing artifacts that are not stored in CA SCM.  When items are found in the CA SCM repository, they are reported on with the version history.   The activity contains fields for the Audit Report name, options, targets, and variable settings. Note: You must execute a Meister Build Control File activity before this step.

Execute Meister Clean All Build with CA SCM Audit

This activity runs a re-build of all objects while auditing all files used in the build, exposing artifacts that are not stored in CA SCM.  When items are found in the CA SCM repository, they are reported on with the version history.   The activity contains fields for the Audit Report name, options, targets, and variable settings. Note: You must execute a Meister Build Control File activity before this step.

Unicenter DSM Package Register

Registers what binaries are to be deployed.  The Item Name, version and Directory Path are required.

Unicenter Deploy Package

Deploys a Unicenter Package.