Specifying a separate Repository for GenerateReleaseNotes Extension in Azure DevOps Pipeline

[ArneReith]

I have a Repository where I store all my Azure Devops YAML Pipelines and other related materials like templates an bash scripts. The pipelines are executed within this repository. The actual project, wich contains the application itself, is loaded from a separate repository via resources:

resources:
  repositories:
  - repository: "projectrepo"
    type: git
    name: myapplication

I've integrated the GenerateReleaseNotes Extension in a pipeline task. Currently it generates the release notes for the main project, which includes the pipelines. However, I would like the release notes to be generated for the projectrepo instead.

Is it possible to specify the repository that should be used for generating the release notes?

Thank you,
Arne

[ArneReith]

Am I right, that it is simply not possible?

I've seen in the code (https://github.com/rfennell/AzurePipelines/blob/main/Extensions/XplatGenerateReleaseNotes/XplatGenerateReleaseNotesTask/src/GenerateReleaseNotes.ts) that your get the values via tl.getVariable("System.TeamProject"); and tl.getVariable("System.TeamFoundationCollectionUri"); And I think that the only way would be to offer an override like you have already done it with overrideActiveBuildReleaseId.

Would you be open for a merge request, if I would implement it?

thx, Arne

[rfennell]

I do consider any PRs, but I am not sure what you are suggesting will work. The variables you mention are just used to access the AzDo instance the build is running in.

The core of this task are the AzDo API calls that find the associated CS & WI between two builds of a given build definition. This constrains the repo being looked at to the one that contains the running pipeline (though this can use YAML template in other repos).

So if we had a repo MyProj, that used YAML from MyYAMLTempaltes, the release notes are generate based on the MyProj repo build as that is where the build lives

[rfennell]

If experimenting use the local tester it makes life much easier as you want rerun the same test easily