Activity Plug-in

Description

Update from Visual Source Safe

This activity takes updates from the VSS file repository and applies them to your workspace, usually at the start of a Workflow before other activities are conducted.  The activity contains a field for the Source Safe directory, which is the only required field.

Execute Meister Incremental Build Audit with VSS Audit

This activity is used to execute a Meister Incremental Build, building only items that are out of date, with Build Audit Reporting, exposing all artifacts used in the build even when they are not managed by VSS.  When files under VSS control are identified, the version information of the source files from the Visual Source Safe repository is reported.  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 VSS Audit.

This activity is used to execute a Meister clean all Build, re-building all items, with Build Audit Reporting, exposing all artifacts used in the build even when they are not managed by VSS.  When files under VSS control are identified, the version information of the source files from the Visual Source Safe repository is reported.  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.

VSS Bill of Material Report

This activity provides a VSS Bill of Materials report.  If the same Workflow has been run against the same source control module before, this activity will also provide a VSS 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.

Run  .Net Solution Build

This activity will invoke the Visual Studio devenv compiler to execute a solution-level build, based upon the .sln file you pass in.  The activity contains fields for the Solution file name, Build Action, Configuration, and options to be passed to devenv.

Checkout from TFS

This activity will invoke the tf command to execute a checkout. The activity contains fields for lock (default /lock:none), recursive (default non-recursive), encoding (default empty), and the itemspec.

Checkin to TFS

This activity will invoke the tf command to execute a checkin. The activity contains fields for author, comment, notes, override, additional options, and the filespec to check in.

Create TFS Workspace

This activity will invoke the tf command to create a new workspace. The activity contains fields for a template, the computer, a comment, the TFS server, and the workspace.

Generate TFS Bill of Material Inspector

This activity provides a TFS Bill of Materials report. If the same Workflow has been run against the same source control module before, this activity will also provide a TFS 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 TFS Audit

This activity is used to execute a Meister Incremental Build, building only items that are out of date, with Build Audit Reporting, exposing all artifacts used in the build even when they are not managed by TFS. When files under TFS control are identified, the version information of the source files from the Team Foundation Server repository is reported. 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 TFS Audit

This activity is used to execute a Meister clean all Build, re-building all items, with Build Audit Reporting, exposing all artifacts used in the build even when they are not managed by TFS. When files under TFS control are identified, the version information of the source files from the Team Foundation Server repository is reported. 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.

Update From TFS

This activity takes updates from the TFS file repository and applies them to your workspace, usually at the start of a Workflow before other activities are conducted. This activity executes a tf get The activity contains fields for itemspec, versionspec, and additional options (such as /all or /recursive).