You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
System_StageName is defined thus ##[debug]System.StageName=__default in the Azure Pipeline usage of the Task but not in the test console and that discrepancy causes differences in data retrieved and processed from the Azure APIs.
Repo Steps
Run test console with and without the environment variable "System_StageName": "__default" and notice differences
in the log output
Getting items associated the builds since the last successful build to the stage '__default'
Found '25' matching builds to consider
Matching 'successful' builds only
An override build number has been passed, will only consider this build
Found the over ride build 6485
Getting the details between 6485 and 6701
Using workaround for build API limitation (see issue #349)
VS
Getting items associated the builds since the last successful build to the stage 'undefined'
No stage name provided, cannot find last successful build by stage
There has been no past successful build for this stage, we need to get the details for all past builds
Using workaround for build API limitation (see issue #349)
and corresponding differences in generated markdown.
Expected Behavior
System_StageName env var in test console should match azure pipeline so their output does not differ when they have the same settings in e.g. build-settings.json
Logging Information
No response
The text was updated successfully, but these errors were encountered:
Azure DevOps Extensions
Generate Release Notes (Node Cross Platform)
Platform
Azure DevOps Services
Azure DevOps Server (TFS) Version
No response
Extension Version
No response
Describe the bug
System_StageName is defined thus
##[debug]System.StageName=__default
in the Azure Pipeline usage of the Task but not in the test console and that discrepancy causes differences in data retrieved and processed from the Azure APIs.Repo Steps
Run test console with and without the environment variable "System_StageName": "__default" and notice differences
VS
Expected Behavior
System_StageName env var in test console should match azure pipeline so their output does not differ when they have the same settings in e.g. build-settings.json
Logging Information
No response
The text was updated successfully, but these errors were encountered: