Using Windows Agent Causes Failure When Create artifact from portal

Azure / apiops

APIOps applies the concepts of GitOps and DevOps to API deployment. By using practices from these two methodologies, APIOps can enable everyone involved in the lifecycle of API design, development, and deployment with self-service and automated tools to ensure the quality of the specifications and APIs that they’re building.

MIT License

309 stars 181 forks source link

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

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.

Azure / apiops