How to add links to documentation to pipeline run in Azure Devops

2022-05-04 10:30 Win32Sector imported from Stackoverflow

We have a few hundred different pipelines in Azure DevOps and we have documentation about the variables and describing what the pipeline does.

Perhaps there is a way to add a link to the documentation to the pipelines run? For example here

1 answer

answered 2022-05-05 02:32 Bowman Zhu-MSFT
From the screenshot, the pipeline was not run indeed.

If you are using YAML pipeline, just add the comments to the pipeline definition:
```
# Follow below link for more details:
# https://www.xxx.xxx

trigger:
- dev

pool:
  vmImage: ubuntu-latest

steps:
- script: echo Hello, world!
  displayName: 'Run a one-line script'
```
Then, you can press 'Ctrl' and right-click to go to the details page.

If you are using Classic pipeline, you can add it to this place:

You cannot add custom display items where you show. If you want to see it there, you can do this:

If you are using YAML:

For the YAML pipeline, be sure to follow the steps I provided above, otherwise, the variable won't show up there.

The classic pipeline is similar.

Let me know if you have more concerns.

See also questions close to this topic

How to exclude tagged commit
I have a build pipeline in Azure Pipelines with
```
trigger:
  branches:
    include:
    - '*'
  tags:
    include:
    - v/*
```
In other words: I build all branches (in practice I only have one), and all tags that start with v/ (these are my releases).

When I push a commit and its tag, Azure Pipelines kicks off two builds - one for the branch and one for the tag - even though they're the same commit. This takes up unnecessary pipeline resources, particularly when I want to release from many repositories at the same time.

Is there a way to skip the "branch build" of a commit (or cancel if ongoing) when a "tag build" of the same commit is started?

Automate Azure Devops (FTP Upload) and Git to upload on Remote Server

The current setup is as below

Version Control - Git
Repos and Branch hosted on - Azure DevOps
Codebase - External server

The dev team clones Azure Repo into local git project and any staged changes are committed via Git and pushed to specific branch of Azure DevOps. In this setup we would want to upload the changes to external FTP servers and avoid manual upload. Currently trying to use Azure Devops FTP Upload Task (https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/ftp-upload?view=azure-devops), however facing issues; yaml script as below

trigger:
- main

pool:
  vmImage: 'ubuntu-latest'

variables:
  phpVersion: 7.4
  webAppName: 'Test Project'
  buildConfiguration: 'Release'
  vmImageName: 'ubuntu-latest'

steps:

- publish: $(System.DefaultWorkingDirectory)/AzureRepoName
  artifact: Test Project Deploy

- task: FtpUpload@2
  displayName: 'FTP Upload'
  inputs:
    credentialsOption: inputs
    serverUrl: 'ftps://00.00.00.00:22'
    username: ftp-username
    password: ftp-password
    rootDirectory: '$(System.DefaultWorkingDirectory)/AzureRepoName'
    remoteDirectory: '/home/public_html'
    clean: false
    cleanContents: false
    preservePaths: true
    trustSSL: true

PROBLEM

Following errors occur when I commit (for test purposes) something.

Starting: PublishPipelineArtifact
==============================================================================
Task         : Publish Pipeline Artifacts
Description  : Publish (upload) a file or directory as a named artifact for the current run
Version      : 1.199.0
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/publish-pipeline-artifact
==============================================================================
Artifact name input: Test Project Deploy
##[error]Path does not exist: /home/vsts/work/1/s/AzureRepoName
Finishing: PublishPipelineArtifact

I want to upload any staged change that is committed to main branch on Azure Devops to be automatically deploy on the remote FTP server

Thanks

Migrate Azure Devops Artifacts between organizations

I am trying to migrate (clone) an Azure Devops project to another project / organization. I successfully

cloned the repos
migrated the work items using Azure DevOps Migration Tools by NkdAgility
I exported the build and release pipelines as json files and imported them again.
I created a selfhosted agent on my VM and trying to run the build pipelines - the job "dotnet restore" on that.
I created a new feed under Artifacts. Unfortunately the job with dotnet restore fails because it relies on the artifacts only available in the old project

How can I migrate the packages from the feeds of the old project to the new one(s)?

I assume I am supposed to clone the feeds of the old project somehow so that I can simply update the nuget.config with the name of the new organization. Thank you in advance.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <!-- remove any machine-wide sources with <clear/> -->
    <clear />
    <!-- also get packages from the NuGet Gallery -->
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
    <add key="DotNetArcade" value="https://dotnetfeed.blob.core.windows.net/dotnet-core/index.json" />
    <add key="<OLD_FEED1" value="https://pkgs.dev.azure.com/<old org>/_packaging/<OLD_FEED1>/nuget/v3/index.json" />
    <add key="<OLD_FEED2" value="https://pkgs.dev.azure.com/<old org>/_packaging/<OLD_FEED2>/nuget/v3/index.json" />
    <add key="<OLD_FEED3" value="https://pkgs.dev.azure.com/<old org>/_packaging/<OLD_FEED3>/nuget/v3/index.json" />
  </packageSources>
  <activePackageSource>
    <add key="All" value="(Aggregate source)" />
  </activePackageSource>
</configuration>

Related questions

How to add links to documentation to pipeline run in Azure Devops

1 answer

See also questions close to this topic