This JavaScript package library extracts varibale groups, task groups and classic release pipleine as Yaml files.

1. Run below commands to create package.json file and install azdo-classic-to-yaml.

npm init && npm i azdo-classic-to-yaml

2. Add "generate": "node ./node_modules/azdo-classic-to-yaml/generate.js" in package.json file

{
  "name": "demo",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "generate": "node ./node_modules/azdo-classic-to-yaml/generate.js"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "azdo-classic-to-yaml": "^1.0.1"
  }
}

3. Create .env file and update with your ORGANIZATION, PROJECT and PAT. (https://dev.azure.com/ORGANIZATION/PROJECT)

• How to create PAT

ORGANIZATION=
PROJECT=
PAT=

4. Run below command. This will generate yaml file in pipelines folder.

npm run generate

• Variable Groups - ./pipelines/varibalegroups/*.yaml
• Task Groups - ./pipelines/taskgroups/*.yaml
• Release Pipeline - ./pipelines/*.yaml

• This supports only for classic release pipelines and gives you simple template structure.
• Pre and Post approval flows are not covered and recommended to use deployment strategies with approval.
• connectedServiceNameARM: $(az_service_connection) needs to be replaced with azureSubscription: $(az_service_connection) in some places.
• Task groups needs to be updated with parameters - $(az_service_connection) to ${{ parameters.az_service_connection }}
• Needs cleanup and fixes.

name: "Release Pipeline 1"
trigger: none
paremeters: []
variables: []
resources:
  pipelines: []
  repositories: []
stages:
  - stage: Development
    variables: []
    jobs:
      - job: Bundle - DEV
      - job: AKS Deployment - DEV
      - job: DB Migration - DEV
  - stage: Integration
    variables: []
    jobs:
      - job: AKS Deployment  - INT
      - job: DB Migration - INT 
      - job: Post Deploy Testing - INT