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 YAML snippet demonstrates usage in a pipeline.

pool:
  vmImage: 'ubuntu-latest'

stages:
  - stage: Use_MCIX_Tasks

    jobs:
    - job: Demonstrate_MCIX_Tasks
      displayName: "Demonstrate MCIX Tasks"
      steps:

      - checkout: self

      # This is requried in every stage of a Azure DevOps pipeline using Microsoft-hosted agents 
      # to provide access to a Docker container registery via a secure service connections.  
      - task: Docker@2
        displayName: "Login to container registry"
        inputs:
          command: login
          containerRegistry: 'my-container-service-connection'

      # This first task is optional, but useful to verify the MCIX container is accessible 
      # and also has the side-effect of pulling the container image (used by subsequent mcix
      # tasks) early in the job.
      - task: mcixSystemVersion@1
        displayName: "Verify container version"
        inputs: {}

      - task: mcixDatastageImport@1
        inputs:
          url: 'http://my-cpd.my-organization.com'
          user: 'MyUserName'
          apiKey: '${MySecureApiKey}'
          project: 'MyProject'
          assetsPath: '$(Build.SourcesDirectory)/datastage'

      - task: mcixDatastageCompile@1
        inputs:
          url: 'http://my-cpd.my-organization.com'
          user: 'MyUserName'
          apiKey: '${MySecureApiKey}'
          project: 'MyProject'
          report: 'report.xml'
          includeAssetInTestName: true

Tasks

• MCIX Asset Analysis Test
• MCIX DataStage Compile Task
• MCIX DataStage Import Task
• MCIX Ovelay Apply Task
• MCIX System Version Task
• MCIX Unit Test Execute

MCIX Asset Analysis Test

Runs mcix asset-analysis test inside the MCIX container image and optionally publishes JUnit results.

YAML example

- task: mcixAssetAnalysisTest@1
  displayName: "MCIX Asset Analysis Test"
  inputs:
    imageName: datamigrators.azurecr.io/datamigrators/mcix
    imageTag: latest
    rules: "$(RULES)"
    report: "$(REPORT)"

Inputs

MCIX DataStage Compile Task

Runs MCIX DataStage Compile using the official MettleCI container image

YAML example

- task: mcixDatastageCompile@1
  displayName: "MCIX DataStage Compile Task"
  inputs:
    imageName: datamigrators.azurecr.io/datamigrators/mcix
    imageTag: latest
    url: "url-value"
    user: "user-value"
    apiKey: "apiKey-value"
    report: "$(REPORT)"

Inputs

MCIX DataStage Import Task

Runs MCIX DataStage Import using the official MettleCI container image

YAML example

- task: mcixDatastageImport@1
  displayName: "MCIX DataStage Import Task"
  inputs:
    imageName: datamigrators.azurecr.io/datamigrators/mcix
    imageTag: latest
    url: "url-value"
    user: "user-value"
    apiKey: "apiKey-value"
    assetsPath: "$(ASSETSPATH)"

Inputs

MCIX Ovelay Apply Task

Runs MCIX Ovelay Apply using the official MettleCI container image

YAML example

- task: mcixDatastageImport@1
  displayName: "MCIX Ovelay Apply Task"
  inputs:
    imageName: datamigrators.azurecr.io/datamigrators/mcix
    imageTag: latest
    assets: "$(ASSETS)"
    output: "$(OUTPUT)"
    overlays: |
            path/one
            path/two

Inputs

MCIX System Version Task

Runs MCIX System Version using the official MettleCI container image

YAML example

- task: mcixSystemVersion@1
  displayName: "MCIX System Version Task"
  inputs:
    imageName: datamigrators.azurecr.io/datamigrators/mcix
    imageTag: latest

Inputs

MCIX Unit Test Execute

Runs mcix unit-test execute inside the MCIX container image and publishes JUnit results.

YAML example

- task: mcixUnitTestExecute@1
  displayName: "MCIX Unit Test Execute"
  inputs:
    imageName: datamigrators.azurecr.io/datamigrators/mcix
    imageTag: latest
    url: "url-value"
    user: "user-value"
    apiKey: "apiKey-value"
    report: "$(REPORT)"

Inputs

Troubleshooting

“Path must be under the agent working directory” Ensure all input and output paths resolve under one of:

• $(System.DefaultWorkingDirectory)
• $(Build.SourcesDirectory)
• $(Build.ArtifactStagingDirectory)

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