home / skills / ntaksh42 / agents / azure-devops-migration

azure-devops-migration skill

safe

This skill helps plan and execute Azure DevOps migrations, converting GitHub Actions, Jenkins, and GitLab CI to Azure Pipelines.

npx playbooks add skill ntaksh42/agents --skill azure-devops-migration

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.6 KB

---
name: azure-devops-migration
description: Plan and execute Azure DevOps migrations between organizations or projects. Use when migrating Azure DevOps resources or consolidating projects.
---

# Azure DevOps Migration Skill

他のCI/CDツールからAzure DevOpsへの移行を支援するスキルです。

## 主な機能

- **GitHub Actions → Azure Pipelines**: YAML変換
- **Jenkins → Azure Pipelines**: Jenkinsfile変換
- **GitLab CI → Azure Pipelines**: .gitlab-ci.yml変換

## GitHub Actions → Azure Pipelines

### GitHub Actions

```yaml
name: CI
on: [push]
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: '18'
      - run: npm install
      - run: npm test
```

### Azure Pipelines

```yaml
trigger:
  - '*'

pool:
  vmImage: 'ubuntu-latest'

steps:
  - checkout: self
  - task: NodeTool@0
    inputs:
      versionSpec: '18'
  - script: npm install
  - script: npm test
```

## Jenkins → Azure Pipelines

### Jenkinsfile

```groovy
pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                sh 'npm install'
                sh 'npm run build'
            }
        }
        stage('Test') {
            steps {
                sh 'npm test'
            }
        }
    }
}
```

### Azure Pipelines

```yaml
stages:
  - stage: Build
    jobs:
      - job: BuildJob
        steps:
          - script: npm install
          - script: npm run build

  - stage: Test
    jobs:
      - job: TestJob
        steps:
          - script: npm test
```

## バージョン情報
- Version: 1.0.0

Overview

This skill helps plan and execute migrations into Azure DevOps across organizations or projects. It converts common CI/CD configurations from GitHub Actions, Jenkins, and GitLab CI into Azure Pipelines YAML and provides migration patterns for stages, jobs, and tasks. Use it to standardize pipelines, consolidate projects, and reduce manual translation effort.

How this skill works

The skill parses source CI definitions (GitHub Actions YAML, Jenkinsfiles, GitLab CI YAML) and maps equivalent concepts to Azure Pipelines constructs such as triggers, pools, stages, jobs, steps, and tasks. It outputs example Azure Pipelines YAML, highlights manual steps that need attention (secrets, service connections, marketplace tasks), and provides version notes for compatibility. The focus is on straightforward, repeatable translations rather than a fully automated, one-size-fits-all conversion.

When to use it

Migrating a single repository or many repositories into Azure DevOps
Consolidating CI/CD across teams into a common Azure Pipelines standard
Rewriting pipelines when retiring GitHub Actions, Jenkins, or GitLab CI runners
Planning an organization- or project-level reorganization in Azure DevOps

Best practices

Review and validate converted YAML in a feature branch before merging to main
Map secrets and service connections to Azure DevOps service connections rather than inlining credentials
Convert jobs and stages conservatively: keep test/build separation and preserve run order
Use hosted agent VM images consistent with original runners to avoid environment drift
Document any manual post-conversion steps such as custom tasks, marketplace extensions, or workspace path changes

Example use cases

Convert a GitHub Actions workflow that installs Node and runs tests into an Azure Pipelines YAML with NodeTool and script steps
Transform a Jenkins declarative pipeline (Jenkinsfile) into multi-stage Azure Pipelines with separate Build and Test stages
Migrate GitLab CI pipelines with job artifacts and stages into Azure Pipelines while preserving artifacts and triggers
Plan an org-wide migration plan: inventory pipelines, convert examples, test on a pilot project, then scale across repos

FAQ

Will the skill produce a drop-in replacement pipeline?

No. It produces a practical, tested translation for common constructs, but you must validate and adjust items such as service connections, secrets, and custom tasks before using in production.

Does it handle advanced or proprietary plugins and custom tasks?

It provides guidance and highlights where proprietary plugins or marketplace tasks require manual mapping; fully custom or binary plugins typically need a manual implementation or replacement in Azure DevOps.