MettleCI for IBM DataStage NextGen

MettleCI's IBM DataStage NextGen DevOps automation toolkit (MCIX) in Azure DevOps pipelines using a deployment and infrastructure-free containerised solution.

This extension provides a set of custom Azure DevOps tasks that wrap the MCIX CLI and run it inside a Docker container, ensuring consistent behaviour across agents and environments.

Requirements

• A Linux build agent with Docker available
  (Microsoft-hosted Ubuntu agents work out of the box)
• All input and output paths must be under the agent working directory:
  • $(System.DefaultWorkingDirectory)
  • $(Build.SourcesDirectory)
  • $(Build.ArtifactStagingDirectory)

Quick start

Note that these tasks provide a graphical user interface in Azure DevOps pipelines which will enable you to author CI/CD pipelines for IBM Cloud Pak without needing to be an expert in YAML. The following snippet demonstrates how a task is used in a pipeline.

pool:
  vmImage: 'ubuntu-latest'

stages:
  - stage: Use_MCIX_Tasks
    jobs:
    - job: Demonstrate_MCIX_Tasks
      displayName: "Demonstrate MCIX Tasks"
      steps:
      - checkout: self
      - task: mcixDataStageImport@1
        inputs:
          containerRegistry: 'my-container-service-connection'
          url: 'http://my-cpd.my-organization.com'
          user: 'MyUserName'
          apiKey: '${MySecureApiKey}'
          project: 'MyProject'
          assetsPath: 'datastage'

Tasks

• MCIX Asset Analysis Test
• MCIX DataStage Compile
• MCIX DataStage Deploy
• MCIX DataStage Import
• MCIX Overlay Apply
• MCIX System Version
• MCIX Unit Test Execute

MCIX Asset Analysis Test

Static code analysis of Cloud Pak assets with optional publication of JUnit results.

YAML example

- task: mcixAssetAnalysisTest@1
  displayName: "MCIX Asset Analysis Test"
  inputs:
    imageName: "imageName-value"
    imageTag: "imageTag-value"
    rules: "$(RULES)"
    report: "$(REPORT)"

Inputs

MCIX DataStage Compile

Compilation of DataStage assets in a specified Cloud Pak project

YAML example

- task: mcixDataStageCompile@1
  displayName: "MCIX DataStage Compile"
  inputs:
    imageName: "imageName-value"
    imageTag: "imageTag-value"
    url: "url-value"
    user: "user-value"
    apiKey: "apiKey-value"
    report: "$(REPORT)"

Inputs

MCIX DataStage Deploy

Deployment of DataStage assets to a Cloud Pak project

YAML example

- task: mcixDataStageDeploy@1
  displayName: "MCIX DataStage Deploy"
  inputs:
    imageName: "imageName-value"
    imageTag: "imageTag-value"
    assets: "$(ASSETS)"
    overlays: |
            path/one
            path/two
    output: "$(OUTPUT)"
    url: "url-value"
    user: "user-value"
    apiKey: "apiKey-value"
    report: "$(REPORT)"

Inputs

MCIX DataStage Import

Import of DataStage assets into a specified Cloud Pak project

YAML example

- task: mcixDataStageImport@1
  displayName: "MCIX DataStage Import"
  inputs:
    imageName: "imageName-value"
    imageTag: "imageTag-value"
    url: "url-value"
    user: "user-value"
    apiKey: "apiKey-value"
    assetsPath: "$(ASSETSPATH)"

Inputs

MCIX Overlay Apply

Modification of file assets to apply environment-specific values

YAML example

- task: mcixOverlayApply@1
  displayName: "MCIX Overlay Apply"
  inputs:
    imageName: "imageName-value"
    imageTag: "imageTag-value"
    assets: "$(ASSETS)"
    output: "$(OUTPUT)"
    overlays: |
            path/one
            path/two

Inputs

MCIX System Version

Retrieve details on the MCIX container providing DataStage CI/CD capabilities for IBM Software Hub (Cloud Pak)

YAML example

- task: mcixSystemVersion@1
  displayName: "MCIX System Version"
  inputs:
    imageName: "imageName-value"
    imageTag: "imageTag-value"

Inputs

MCIX Unit Test Execute

Unit testing of DataStage assets in a specified Cloud Pak project

YAML example

- task: mcixUnitTestExecute@1
  displayName: "MCIX Unit Test Execute"
  inputs:
    imageName: "imageName-value"
    imageTag: "imageTag-value"
    url: "url-value"
    user: "user-value"
    apiKey: "apiKey-value"
    report: "$(REPORT)"

Inputs

Troubleshooting

Docker image pull fails (401 / 403) If using a private container registry, authenticate earlier in the job (for example with the built-in Docker@2 login task).

© 2025-2026 Data Migrators Pty Ltd. All rights reserved.

Data Migrators policy documents