Consider Partially Successful Release not working

[levimatheri]

For some reason, checking the 'Consider Partially Successful Release' is not working. It's still going all the way to find the 'fully' last successful build. Using Task Version 3.74.3

[rfennell]

Can you provide a detailed log of the run i.e. with the system.debug variable set to true.

[levimatheri]

See log below. This is from a build pipeline btw.

releaseNotesLog.txt

[levimatheri]

I'm thinking maybe need to add another BuildResult here for 'PartiallySucceeded'?

[rfennell]

Yes, you are correct. Looking that the code the considerPartiallySuccessfulReleases was only implemented for Classic Releases. Corresponding logic is required for Multistage YAML as you identified.

I will raise an issue and push a new release out

[rfennell]

Fixed in 3.75.3

[levimatheri]

Thank you for the quick response and fix!

[levimatheri]

@rfennell It doesn't seem to be working with the new release. Am I doing something wrong?
Logs:
LOG.txt

[levimatheri]

I haven't used the tester before, but will try it out. Thanks

[rfennell]

FYI The value I used for return code are from https://docs.microsoft.com/en-us/javascript/api/azure-devops-extension-api/buildresult

• None = 0 - No result
• Succeeded = 2 - The build completed successfully.
• PartiallySucceeded = 4- The build completed compilation successfully but had other errors.
• Failed = 8 - The build completed unsuccessfully.
• Canceled = 32 - The build was canceled before starting.

[levimatheri]

@rfennell Found required stage __default in the 2 state with the result 1 state for build <buildNumber>. What are the different numerical representations for the result? I'm guessing '1' here means 'partially succeeded'? In the code it's checking for result === "4". I changed it to '1' and it started working correctly. I will submit a PR, thanks!

[levimatheri]

@rfennell Here's the PR, thanks. #1164

[rfennell]

3.76.4 is just being published with a correct enum value for the timeline result