Using Windows Agent Causes Failure When Create artifact from portal

Open
#664 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure

Research direction

Start with the extractor pipeline's “Set Extraction Variables” stage and the locally used Windows extractor.exe on the windows-latest agent. Compare the pipeline behavior with the documented Windows-agent setup and determine which configuration change prevents the “--output was unexpected at this time” and stderr failures; done means all pipeline stages pass.

Written by the indexing model from the issue text.

Description

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

Dominant language
C#
Stars
448
Forks
247
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/apiops

All issues in Azure/apiops

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.