azure-pipelines

问题 Snippet from Yaml file of my pipeline where I archive the build directory, publish it to artifacts and then try to make the artifact available as a universal package in Azure Artifacts. - task: ArchiveFiles@2 inputs: rootFolderOrFile: '$(Build.SourcesDirectory)/Software/MCU/build/pkgs' archiveType: 'zip' archiveFile: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip - task: PublishBuildArtifacts@1 inputs: pathtoPublish: '$(Build.ArtifactStagingDirectory)' artifactName: MCU_Build - task:

问题 Snippet from Yaml file of my pipeline where I archive the build directory, publish it to artifacts and then try to make the artifact available as a universal package in Azure Artifacts. - task: ArchiveFiles@2 inputs: rootFolderOrFile: '$(Build.SourcesDirectory)/Software/MCU/build/pkgs' archiveType: 'zip' archiveFile: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip - task: PublishBuildArtifacts@1 inputs: pathtoPublish: '$(Build.ArtifactStagingDirectory)' artifactName: MCU_Build - task:

问题 Snippet from Yaml file of my pipeline where I archive the build directory, publish it to artifacts and then try to make the artifact available as a universal package in Azure Artifacts. - task: ArchiveFiles@2 inputs: rootFolderOrFile: '$(Build.SourcesDirectory)/Software/MCU/build/pkgs' archiveType: 'zip' archiveFile: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip - task: PublishBuildArtifacts@1 inputs: pathtoPublish: '$(Build.ArtifactStagingDirectory)' artifactName: MCU_Build - task:

问题 I'd like to rename my organisation URL in Azure Devops. The support articles describe the impact, and what to do. But they don't mention any impact on the Azure Pipelines agent. However, when I look at the .agent config file, there's a serverUrl property that points to the specific organisation URL. So - if I rename my organisation URL, will it impact my agents? Do I need to reconfigure them? 回答1: Yes, it will impact your agents. Currently, they configure to the first URL, when you change the

问题 I'd like to rename my organisation URL in Azure Devops. The support articles describe the impact, and what to do. But they don't mention any impact on the Azure Pipelines agent. However, when I look at the .agent config file, there's a serverUrl property that points to the specific organisation URL. So - if I rename my organisation URL, will it impact my agents? Do I need to reconfigure them? 回答1: Yes, it will impact your agents. Currently, they configure to the first URL, when you change the

问题 I have an issue that makes all my previous commits show as associated changes in each new build. I believe the issue is related to the automatic triggering of the build definition using a wildcard branch pattern. I trigger our release builds on any commits on a branch name with the pattern 'release/*'. Each production release of our software starts with a new release branch with the following naming convention 'release/1', 'release/2', etc. where the number matches our released software

问题 I have an issue that makes all my previous commits show as associated changes in each new build. I believe the issue is related to the automatic triggering of the build definition using a wildcard branch pattern. I trigger our release builds on any commits on a branch name with the pattern 'release/*'. Each production release of our software starts with a new release branch with the following naming convention 'release/1', 'release/2', etc. where the number matches our released software

问题 I have an issue that makes all my previous commits show as associated changes in each new build. I believe the issue is related to the automatic triggering of the build definition using a wildcard branch pattern. I trigger our release builds on any commits on a branch name with the pattern 'release/*'. Each production release of our software starts with a new release branch with the following naming convention 'release/1', 'release/2', etc. where the number matches our released software

问题 I have an issue that makes all my previous commits show as associated changes in each new build. I believe the issue is related to the automatic triggering of the build definition using a wildcard branch pattern. I trigger our release builds on any commits on a branch name with the pattern 'release/*'. Each production release of our software starts with a new release branch with the following naming convention 'release/1', 'release/2', etc. where the number matches our released software

问题 I have an issue that makes all my previous commits show as associated changes in each new build. I believe the issue is related to the automatic triggering of the build definition using a wildcard branch pattern. I trigger our release builds on any commits on a branch name with the pattern 'release/*'. Each production release of our software starts with a new release branch with the following naming convention 'release/1', 'release/2', etc. where the number matches our released software