Azure-devops-docs: Pipeline resource predefined "meta-data" variables

[benc-uk]

I'm trying to use the new pipeline resource to have my build pipeline trigger a CD/release pipeline.
I need to pass the Build.BuildId from my build to the release, which is a very common scenario

The docs mention pre-defined "pipeline-resource-meta-data" variables I can use. However none of these seem to be populated. These variables mention an <Alias> but it's never explained what Alias refers to? I tried the pipeline resource reference I used, but it didn't work

Basically the docs seem incomplete.

https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema#pipeline-resource-meta-data-as-pre-defined-variables

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 7458d5b2-1bb7-7d87-7ce6-2b0c430b0155
• Version Independent ID: edf5bbd3-a3f0-5426-e985-31290f8afd05
• Content: YAML schema - Azure Pipelines
• Content Source: docs/pipelines/yaml-schema.md
• Product: devops
• Technology: devops-cicd
• GitHub Login: @vtbassmatt
• Microsoft Alias: macoope

[benc-uk]

Any response?
Linking pipelines together is practically pointless if you can not pass information like build-id between them

[benc-uk]

I have got this working now, e.g.

# Example CD release pipeline
trigger: none

resources: 
  pipelines:
  - pipeline: buildpipeline
    source: My Build Pipeline
    trigger: true

jobs:
- deployment: deployMyApp

  pool:
    vmImage: ubuntu-latest

  strategy:
    runOnce:
      deploy:
        steps:
        - download: buildpipeline
          artifact: helm-charts
        - bash: echo "Build run name was: $(resources.pipeline.buildpipeline.runName)"

I still think a worked example of CI & CD separated across two pipelines is badly needed in the docs

[sukoneck]

@benc-uk you're the man. Appreciate you documenting all this for the rest of us 👍