Pipeline Installation

Introduction

DD-STAT may be run in DevOps environments in a Continuous Integration pipeline. A separate license and installation are required.

These instructions specify how to use the pipeline drop artifacts to create a pipeline in Azure DevOps running DD-STAT.

Pipeline Scripting

There are 3 tasks you have to complete inside your pipeline script to get DD-STAT properly set up.

1. Unzip/extract the "ddstat_pipeline_extract.zip" archive to the "C:" folder of your pipeline VM For Azure DevOps, this might look like:

 - task: ExtractFiles@1
  inputs:
    archiveFilePatterns: '$(System.ArtifactsDirectory)/pipeline_drop/*.zip'
    destinationFolder: 'C:\'
    cleanDestinationFolder: false
    overwriteExistingFiles: false

1. Run the "ddstat_pipeline_setup.bat" script, and ensure it has permissions to modify the shell environment, since it sets up the PATH. For Azure DevOps, this might look like:

- task: BatchScript@1
  inputs:
    filename: '$(System.ArtifactsDirectory)/pipeline_drop/ddstat_pipeline_setup.bat'
    modifyEnvironment: true

1. Run the "fdi_ide.reg" registration key file to get the registry set up properly. For Azure DevOps, this might look like:

- task: CmdLine@2
  inputs:
    script: 'regedit /s $(System.ArtifactsDirectory)/pipeline_drop/fdi_ide.reg'
  displayName: Install the registry components for FDI IDE

The successful completion of these steps should have the PATH, Registry, and VM hard drive set up for DD-STAT execution from a command prompt.

Notes

To verify that folders were copied correctly, you can generally add steps to your pipeline to call the shell "dir" function in the directory you want to check.

The licenses will be copied to "C:\ProgramData\FieldComm", and show up as .lfx files.