Missing commits on Release notes

[lucasssfigueredo]

Hi all.

I have the Generate Release Notes task added to my Release Pipeline which has 94 commits for the first execution of this pipeline:

For some reason, the Build that triggered this Release is showing 50 commits associated, and that's exactly the number of commits I see on the Release Notes.

I had the idea that once I am running the tool from a Release Pipeline, it would bring the Commits from the Release and not from the Build.

Any ideas?

[rfennell]

No immediate idea, if you could run the pipeline with the variable system.debug=true so we get a detailed log of the calls made we might spot something. Maybe a call is not set to get all items, just the first 50.

You might find the command line tester useful to allow repeated running of the generation process without rerunning the task (this defaults to detailed logging buy the way)

[lucasssfigueredo]

Hi Richard,

Thanks a lot for your prompt response. I need to learn how to test it locally :). I'll keep you posted.

Thank you.

[rfennell]

If you testing it with the test harness is too much of a problem, I can just publish the change. It has already been through my automated tests and passed.

[lucasssfigueredo]

Please, go ahead. I will re-run the Release as soon as I hear from you.

[rfennell]

Has been released as 3.73.2

[lucasssfigueredo]

It worked now 👍

Thanks again

[rfennell]

Fixed in 3.73.2