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

Azure Pipelines Windows builds broken #5117

Closed
mback2k opened this issue Mar 18, 2020 · 4 comments
Closed

Azure Pipelines Windows builds broken #5117

mback2k opened this issue Mar 18, 2020 · 4 comments
Assignees
Labels
tests Windows

Comments

@mback2k
Copy link
Member

mback2k commented Mar 18, 2020

It seems like Microsoft either changed their YAML parser regarding backslash based paths or something related to running steps in containers.

Anyway, the issue is known to me and I will try to fix it today.

@mback2k
Copy link
Member Author

mback2k commented Mar 18, 2020

I think this issue is related to the March 16 update:
https://docs.microsoft.com/en-us/azure/devops/release-notes/2020/pipelines/sprint-166-update

mback2k added a commit to mback2k/curl that referenced this issue Mar 18, 2020
@mback2k
Copy link
Member Author

mback2k commented Mar 18, 2020

@mback2k
Copy link
Member Author

mback2k commented Mar 18, 2020

My attempts at fixing it by changing the YAML are failing, so we will have to wait for Microsoft to rollback the update or fix the new issue on their side.

mback2k added a commit to mback2k/curl that referenced this issue Mar 20, 2020
@mback2k
Copy link
Member Author

mback2k commented Mar 20, 2020

A workaround for the changed behaviour regarding Windows Containers has been posted here:
microsoft/azure-pipelines-agent#2864 (comment)

@lock lock bot locked as resolved and limited conversation to collaborators Jun 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
tests Windows
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant