Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The MettleCI Azure DevOps DataStage repository templates pipeline examples require the setup of Environments Azure ‘Environments’ (some requiring Approval) and Variable Groups to store MettleCI and DataStage installation information.

...

The latter approach requires far less setup and configuration, so that is the approach we will document here.

Guides

Table of Contents
minLevel1
maxLevel7
excludeGuides

...

  • Create the variable group, recording the id (referred to later as <GROUP_ID>). Regular variables (not the secret value variables we use for passwords) can be added at this time (<VARIABLES> is entered as variable=value, each pair separated by a space)

  • Code Block
    az pipelines variable-group create \
      --name <VRAIABLE_GROUP_NAME> \
      --variables <VARIABLES> \
      --authorize true \
      --description <GROUP_DESCRIPTION> \
      --organization <ORGANISATION_URL> \
      --project <PROJECT_NAME>

  • Add secret value variables to the group individually for MCIPASSWORD and IISPASSWORD

    Code Block
    az pipelines variable-group variable create \
      --org <ORGANISATION_URL> \
      --project <PROJECT_NAME> \
      --group-id <GROUP_ID> \
      --name <VARIABLE_NAME> \
      --secret true \
      --value <VARIABLE_VALUE>

Info

Note: I have seen where the secret value variable is created but the value is not assigned. In this case you will need to update the value manually in the Azure DevOps administration console.

...

Info

Note: In the creation of an approval for an Approval for an Environment, the type section ({"id":"8C6F20A7-A545-4486-9777-F762FAFE0D4D","name":"Approval"}) contains a hard-coded id value. This is not project or pipeline specific, rather it is the internal id of the “Approval” class, and does not need to be