部署到环境中的 Linux VM

此外，对于 JavaScript 或 Node.js 应用：

• Azure 上至少有两个使用 Nginx 设置的 Linux VM。
• 你自己的 GitHub 示例代码存储库分支。https://github.com/MicrosoftDocs/pipelines-javascript 如果 GitHub 中有一个要部署的应用，则可以改用代码。

此外，对于基于 Java Spring Boot 和 Spring Cloud 的应用：

• 至少安装了 Java 17+ SDK 的两个 Linux VM。 可以通过在 VM 上运行以下命令来安装 Java SDK：

  sudo apt update
  sudo apt install openjdk-17-jdk
  sudo update-alternatives --config java
  sudo update-alternatives --config javac
  java -version 
  

• 你自己的 GitHub 示例代码存储库分支。https://github.com/spring-projects/spring-petclinic 如果 GitHub 中有一个要部署的应用，则可以改用代码。

  注意

  Petclinic是使用 Maven 生成的 Spring Boot 应用程序。

以下管道使用 npm 生成并测试 Node.js 项目，然后打包输出并将其上传到放置位置。

trigger:
- main

pool:
  vmImage: ubuntu-latest

jobs:  
- job: Build
  displayName: Build
  steps:
  - task: UseNode@1
    inputs:
      version: '16.x'
    displayName: 'Install Node.js'
  - script: |
      npm install
      npm run build --if-present
      npm run test --if-present
    displayName: 'npm install, build and test'
  - task: ArchiveFiles@2
    displayName: 'Archive files'
    inputs:
      rootFolderOrFile: '$(System.DefaultWorkingDirectory)'
      includeRootFolder: false
      archiveType: tar
      tarCompression: gz
      archiveFile: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).gz
      replaceExistingArchive: true
  - upload: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).gz
    artifact: drop

有关详细信息，请查看使用 gulp 构建 Node.js 应用中的构建步骤。

以下管道生成 Java 项目并使用 Apache Maven 运行测试，然后打包输出并将其上传到放置位置。

trigger:
- main

pool:
  vmImage: ubuntu-latest

jobs:  
- job: Build
  displayName: Build Maven Project
  steps:
  - task: Maven@4
    displayName: 'Maven Package'
    inputs:
      mavenPomFile: 'pom.xml'
  - task: CopyFiles@2
    displayName: 'Copy Files to artifact staging directory'
    inputs:
      SourceFolder: '$(System.DefaultWorkingDirectory)'
      Contents: '**/target/*.?(war|jar)'
      TargetFolder: $(Build.ArtifactStagingDirectory)
  - upload: $(Build.ArtifactStagingDirectory)
    artifact: drop

有关详细信息，请查看使用 Maven 构建 Java 应用的步骤。

JavaScript 应用的以下 YAML rolling 部署作业取决于成功完成 Build 阶段。 部署作业假定每个代理 VM 上已预安装或预配置以下要求。 对于完全自动化，可以在 VM 上安装和配置这些应用和服务作为管道的一部分。

• 已安装 Node.js 16.x，并确保 npm 在构建代理的 PATH 中可用。
• 系统使用一个 systemd 服务文件（如 /etc/systemd/system/pipelines-javascript.service）来配置服务并启动 Node.js 应用。
• 对于代理用户的必要命令，可在 NOPASSWD:/etc/sudoers 中设置免密码 sudo。
• 为代理用户写入 /opt/pipelines-javascript 或其他部署目标的权限。

- stage: Deploy
  displayName: Rolling Deploy to VMs
  dependsOn: Build
  condition: succeeded()
  jobs:
  - deployment: RollingDeploy
    displayName: Rolling deploy to Ubuntu VMs
    environment:
      name: <environment-name>
      resourceType: VirtualMachine
    strategy:
      rolling:
        maxParallel: 1   #or 2 for parallel. For percentages, use x%
        preDeploy:
          steps:
          - download: current
            artifact: drop
          - script: echo "Pre-deploy on $(hostname)"
        deploy:
          steps:
          - script: |
              echo "Unpacking Node.js app on $(hostname)"
              sudo mkdir -p /opt/pipelines-javascript
              sudo tar -xzf $(Pipeline.Workspace)/drop/$(Build.BuildId).tar.gz -C /opt/pipelines-javascript --strip-components=1
              cd /opt/pipelines-javascript
              echo "Installing production dependencies"
              sudo npm ci --only=production
              echo "Restarting Node.js service"
              sudo systemctl restart pipelines-javascript
            displayName: 'Extract, install, and restart Node.js service'
        routeTraffic:
          steps:
          - script: echo "Routing traffic on $(hostname)"
        postRouteTraffic:
          steps:
          - script: echo "Post-route health check on $(hostname)"
        on:
          failure:
            steps:
            - script: echo "Deployment failed on $(hostname)"
          success:
            steps:
            - script: echo "Deployment succeeded on $(hostname)"

Java 应用的以下 YAML rolling 部署作业取决于成功完成 Build 阶段。

- deployment: VMDeploy
  displayName: web
  dependsOn: Build
  condition: succeeded()
  environment:
    name: <environment name>
    resourceType: VirtualMachine
  strategy:
      rolling:
        maxParallel: 1   #or 2 for parallel. For percentages, use x%
        preDeploy:
          steps:
          - download: current
            artifact: drop
          - script: echo initialize, cleanup, backup, install certs
        deploy:
          steps:
          - task: Bash@3
            displayName: Start Java app, check health, and stop
            inputs:
              targetType: 'inline'
              script: |
                JAR=$(ls $(Pipeline.Workspace)/drop/target/*.jar | head -n 1)
                java -jar "$JAR" --server.port=8081 &
                PID=$!
                # Health check loop
                for i in {1..10}; do
                  if curl -sf http://localhost:8081/actuator/health; then
                    echo "App is up!"
                    break
                  else
                    echo "Waiting for app to be healthy... ($i/10)"
                    sleep 3
                  fi
                done
                # Stop the app manually
                kill $PID 2>/dev/null || echo "Process already exited" 
        routeTraffic:
          steps:
          - script: echo routing traffic
        postRouteTraffic:
          steps:
          - script: echo health check post-route traffic
        on:
          failure:
            steps:
            - script: echo Restore from backup! This is on failure
          success:
            steps:
            - script: echo Notify! This is on success