apiops icon indicating copy to clipboard operation
apiops copied to clipboard

Using Windows Agent Causes Failure When Create artifact from portal

Open platformengineering01 opened this issue 1 year ago • 4 comments

Release version

LATEST

Question Details

I wanted to use the windows extractor file locally in an Azure DevOps repo rather than calling out to the internet with the Git URL. To use this, I must also set the Pool Image to windows-latest as using windows agents in Azure DevOps. But by doing this I'm constantly getting a pipeline error (extractor pipeline) ##[error]--output was unexpected at this time , ##[error]Script has output to stderr. Failing as failOnStdErr is set to true.

When using windows-latest and only using the windows extractor.exe file, are there any other amendments that need to be made?

Expected behavior

All stages pass in pipeline

Actual behavior

Failing at 'Set Extraction Variables'

Reproduction Steps

Change to windows-latest Run windows extractor file locally rather than using git URL

platformengineering01 avatar Sep 17 '24 13:09 platformengineering01

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

github-actions[bot] avatar Sep 17 '24 13:09 github-actions[bot]

Did you check closed issues? I remember this issue being brought up in the past.

waelkdouh avatar Sep 18 '24 02:09 waelkdouh

@waelkdouh Unfortunately I cannot find anything in issues relating to this

platformengineering01 avatar Oct 10 '24 12:10 platformengineering01

This error is due to the az cli code that fetches all the subscriptions under the account. I was able to do a work-around by removing the logic and providing the subscription id as an input parameter. Write-Host "##vso[task.setvariable issecret=true;variable=AZURE_SUBSCRIPTION_ID]$(DATAINT_SUBSCRIPTION_ID_DEV)"

UmairSyed avatar Mar 26 '25 03:03 UmairSyed