1

在我的 azure devops 项目中，我使用模板创建了一个管道。这是我的构建管道的主要 yaml 文件

name: Test-$(Date:yyyyMMdd)$(Rev:.r)

resources:
  repositories:
    - repository: api
      type: git
      name: porject/api
      ref: master
    - repository: front
      type: git
      name: project/front
      ref: master
    - repository: strapi
      type: git
      name: project/strapi
      ref: master

trigger:
  branches:
    include:
      - master

pool:
  vmImage: 'ubuntu-latest'
  workspace:
    clean: all

variables:
- name: workingDir
  value: project
- name: tfVersion
  value: 0.12.29
- name: backendServiceGCP
  value: test
- name: backendGCPBucketName
  value: test
- name: tfpath
  value: test
- name: env
  value: dev

stages:
- stage: Terraform  
  jobs:
  - job: Build
    displayName: Build Terraform Infra
    steps:
      # Set and Export env var for api version to deploy
      - template: templates/fetch-tag.yml
        parameters:
          repo: 'api'
          envVar: TERRAFORM_API_TAG

      # Set and Export env var for front version to deploy
      - template: templates/fetch-tag.yml
        parameters:
          repo: 'front'
          envVar: TERRAFORM_FRONT_TAG

      # Set and Export env var for strapi version to deploy
      - template: templates/fetch-tag.yml
        parameters:
          repo: 'strapi'
          envVar: TERRAFORM_STRAPI_TAG

      # Init Terraform providers
      - template: templates/tf-init.yml
        parameters:
          backendServiceGCP: '$(backendServiceGCP)'
          backendGCPBucketName: '$(backendGCPBucketName)'
          workingDir: '$(workingDir)'
          variableFilePath: $(buildSubscription)-common.tfvars

      # Plan Terraform Infra to Deploy
      - template: templates/tf-plan.yml
        parameters:
          backendServiceGCP: '$(backendServiceGCP)'
          workingDir: '$(workingDir)'
          variableFilePath: $(buildSubscription)-common.tfvars

      # Publish Public Artifact with Terraform ressources to deploy
      - template: templates/publish-artifact.yml
        parameters:
          tfpath: '$(tfpath)'

当我尝试运行管道时，出现以下错误：

Encountered error(s) while parsing pipeline YAML:
Job Build: The step name version appears more than once. Step names must be unique within a job.
Job Build: The step name version appears more than once. Step names must be unique within a job.
Job Build: The step name version appears more than once. Step names must be unique within a job.
Job Build: The step name version appears more than once. Step names must be unique within a job.
Job Build: The step name version appears more than once. Step names must be unique within a job.

我真的不明白为什么。这是我在名为的管道中使用的模板示例publish-artifact.yml：

parameters:
  tfPath: ''

steps:
- task: CopyFiles@2
  inputs:
    sourceFolder: ${{ parameters.tfpath }}
    contents: |
      tfplan
      **/*.tf
      **/*.tfvars
      **/*.json
      !**/.terraform
      **/*.sh
    targetFolder: $(Build.ArtifactStagingDirectory)
- task: PublishBuildArtifacts@1
  inputs:
    pathtoPublish: $(Build.ArtifactStagingDirectory)
    artifactName: tf

我在工作名称上做错了什么？

4

1 回答 1

0

Azure Devops 支持将一个步骤的输出变量作为下一步的输入传递。看到这张票：

我们可以这样命名一个步骤：

  steps:
  - script: echo test
    name: ScriptName

  - task: PowerShell@2
  inputs:
    targetType: 'inline'
    script: |
      Write-Host '##vso[task.setvariable variable=xxx;isOutput=true;]xxx'
  name: PSName

必须是唯一的name，以便我们可以使用格式$(referencename.variablename)从特定步骤访问输出变量。

该错误表明模板中的某些步骤具有相同的名称version！这不受支持。关于为什么会出现这个问题：

1.你多次调用同一个模板，这是你问题的主要原因。

Devops 在处理 pipeline时首先扩展模板，因此如果您的fetch-tag模板有一个名为 的步骤version，则最终消耗的 azure-pipeline.yml 将是：

stages:
- stage: Terraform  
  jobs:
  - job: Build
    displayName: Build Terraform Infra
      steps:
      - task: PowerShell@2
        inputs:
          targetType: 'inline'
          script: |
            Write-Host "Hello World"
        name: version
      ...
      - task: PowerShell@2
        inputs:
          targetType: 'inline'
          script: |
            Write-Host "Hello World"
        name: version
      ...
      - task: PowerShell@2
        inputs:
          targetType: 'inline'
          script: |
            Write-Host "Hello World"
        name: version
      ...

2.您可能还需要检查您的不同模板中是否有同名的步骤。

我们可以在一个管道中多次调用相同的模板，但不能调用命名为 step的相同模板。因为管道将多次扩展模板，最终管道将包含许多具有相同名称的步骤。这不受支持，因为名称应该是唯一的。

解决方案：

1.name如果您不需要使用上面提到的输出变量，请删除您的步骤元素。

2.或者您可以制作多个副本fetch-tag.yml并将它们命名为 fetch-tag-api.yml、fetch-tag-front.yml 和 fetch-tag-strapi.yml。version将这三个文件中的referenceName重命名为version1、version2之类的。然后您可以使用以下命令运行管道：

    steps:
      # Set and Export env var for api version to deploy
      - template: templates/fetch-tag-api.yml
        parameters:
          repo: 'api'
          envVar: TERRAFORM_API_TAG

      # Set and Export env var for front version to deploy
      - template: templates/fetch-tag-front.yml
        parameters:
          repo: 'front'
          envVar: TERRAFORM_FRONT_TAG

      # Set and Export env var for strapi version to deploy
      - template: templates/fetch-tag-strapi.yml
        parameters:
          repo: 'strapi'
          envVar: TERRAFORM_STRAPI_TAG
于 2020-08-12T09:40:17.000 回答