Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System_StageName env var in test console should match azure pipeline #1563

Closed
Stan-Stani opened this issue Nov 3, 2023 · 0 comments
Closed
Labels

Comments

@Stan-Stani
Copy link
Contributor

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

  • 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants