Azure devops pipeline checkout fails on Windows agent due to path length limits

Nigel Jones 21 Reputation points
2020-10-19T16:21:46.157+00:00

We have code in github, public repo & use Azure devops for doing pre-merge PR checks, and post merge builds, amongst other things. The pipelines are defined in yaml in the git repo. Recently I wanted to add a Windows post-merge build. However the build failed before it even executed my tasks due to path name length restrictions. The pipeline definition is at https://github.com/odpi/egeria/blob/master/.azure-pipelines/win.yml We trigger off a new commit in master, and the next task is simply to do a maven build. When I saw the failures I added a task to update the git config, but this of course runs after the git clone Here's an example build: https://dev.azure.com/ODPi/Egeria/_build/results?buildId=13272&view=logs&j=4dc6fbf2-95db-5f93-ea5a-117822a16d38 It's the checkout stage of the job fails, which is done implicitly rather than explicitly. How can I fix this? The builds are all fine for Linux of course (and many of us use MacOS or linux)

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
38,548 questions
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2020-10-19T16:23:29.857+00:00

    They're actively answering Devops questions in dedicated DeveloperCommunity forums here.
    https://developercommunity.visualstudio.com/spaces/21/index.html

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.