pipeline-trigger | trigger allows you to trigger and wait for the results | BPM library

Turned out the problem was the encoding of the powershell-output. Default encoding from powershell 5 is UFT16BOM and my reencoding to UTF8 resulted in UFT8BOM wich gitlab can´t handle properly. My sollution was to encode in ASCII. What I can´t explain is why it was able to interpret the first job correctly, I thought that encodeing would result in an all or nothing outcome. Maybe the CRLF-CRLF after the first job caused the errror

Have a look at Pipeline resource variables

In each run, the metadata for a pipeline resource is available to all jobs in the form of predefined variables. The is the identifier that you gave for your pipeline resource. Pipeline resources variables are only available at runtime.

There are also a number of predefined variables called Build.TriggeredBy.*, amongst them Build.TriggeredBy.DefinitionName, however documentation suggests that for yaml pipeline with pipeline triggers the resource variables should be used instead

If the build was triggered by another build, then this variable is set to the name of the triggering build pipeline. In Classic pipelines, this variable is triggered by a build completion trigger.

This variable is agent-scoped, and can be used as an environment variable in a script and as a parameter in a build task, but not as part of the build number or as a version control tag.

If you are triggering a YAML pipeline using resources, you should use the resources variables instead.

• pipeline: securitylib specifies the name of the pipeline resource, and is used when referring to the pipeline resource from other parts of the pipeline, such as pipeline resource variables.

is a name for the pipeline resource. This is not pipeline name in Azure Devops. It it is like

One way would be to create a tag at the end of the CI and CD can be triggered by this tag.

ADO CI pipeline sample code :

Updates are made every few weeks to the cloud-hosted version, Azure DevOps Services. These updates are then rolled up and made available through quarterly updates to the on-premises Azure DevOps Server and TFS.So, all features are release in Azure DevOps Service first.

A timeline of feature released and those planned in the feature release can be found at here-- Azure DevOps Feature Timeline

You could choose to directly use cloud version Azure DevOps Service instead or monitor latest update on above Feature Timeline with Azure DevOps Server. Sorry for any inconvenience.

Assuming your pipelines are all in the same project, and assuming you're using Windows-based build agents whose services are running under a Windows account that has permission to access your project in Azure DevOps (as opposed to LOCAL SYSTEM et cetera), you can run the script below as a build task for the purpose of triggering other builds, which could then trigger releases.

Working Solution

Because all of my builds are centralised in one pipeline template, I changed this template to trigger my pipeline A on successful publishing of an artifact. Here's the pipeline trigger code which is pretty much verbatim from (https://docs.microsoft.com/en-us/azure/devops/cli/azure-devops-cli-in-yaml?view=azure-devops), apart from the last couple of steps:

I tested and got the same result, tags triggers for other git doesnot work. You can submit a feature request(click suggest a feature and choose Azure devops) for supporting tag triggers for gitlab repo to Micrsoft Development team. Please check this thread for example.

As workaround you can use multiple agent jobs to achieve above currently.

You can add another agent job before your original agent job to run a script task, And add dependency on it in your original agent job. The script task will check if there is tag associated to the current commit. If the tag exits, the script task will pass, and the following agent job will run. Or the script task fails and the following agent job will be skipped.

The detailed steps is as below:

1. add a agent job with a single powershell task. Check below screenshot.

2. Run below inline scripts in the powershell task to check the tags

Custom GitHub PR comment triggers for Azure Pipelines

Yes, you are right. The feature Incoming Webhook should not yet implemented in Azure Pipelines at this time.

Now, Azure pipeline trigger only support the "standard" GitHub Pull Request comments, like /AzurePipelines runor /AzurePipelines run . So we could not use the custom GitHub PR comment trigger the Azure pipeline currently.

The workaround as Levi Lu answered in that post, but the limitation is that the pipeline still needs to be executed for each PR.

If above workaround not help you, you could add your request for this feature on our UserVoice site (https://developercommunity.visualstudio.com/content/idea/post.html?space=21 ), which is our main forum for product suggestions. Thank you for helping us build a better Azure DevOps:

Hope this helps.