locked
All 2015 vNext builds fail on fetching source from Git with 404 not found RRS feed

  • Question

  • I've tried several different builds that work under older 2013 XAML build definitions, on several different vNext build servers, and all fail with the following error in the worker_xxxxxxxx-xxxxxx-utc_xxxx.txt files in the _diag dir

    Catch LibGit2SharpException during git clone, retried 1 of 3
    .Exception: LibGit2Sharp.LibGit2SharpException: Response status code does not indicate success: 404 (Not Found).
       at LibGit2Sharp.Core.Ensure.HandleError(Int32 result)
       at LibGit2Sharp.Core.Proxy.git_clone(String url, String workdir, GitCloneOptions& opts)
       at LibGit2Sharp.Repository.Clone(String sourceUrl, String workdirPath, CloneOptions options)
       at Microsoft.TeamFoundation.DistributedTask.Task.Internal.Core.GitHelper.CloneRepository(String repositoryPath, Uri repositoryUrl, Boolean checkoutSubmodules, String username, String password)

    The repository url is correct and the build service is running under an account that has access to the repository.

    I can't think what else to try to fix this - the vNext build system is just unusable in this state.

    Any help gratefully received

    Mark.

    Wednesday, August 19, 2015 12:53 PM

All replies

  • Hi Mark,  

    Thanks for your post.

    You’re using TFS 2015 RTM and this issue happened in your Git team project vNext build definition to get repo files from your Git team project?

    I will test this scenario in my TFS 2015 RTM Server and check the result.

    If you have any further research of this issue, please share your experience here.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. Click HERE to participate the survey.

    Thursday, August 20, 2015 5:32 AM
    Moderator
  • Yes, this was a 2013 CU4 server that was updated to 2015 RTM. I took a couple of existing team projects with working XAML builds and tried to create vNext builds using exactly the same Git repositories and the default Visual Studio build steps.

    Tried on multiple vNext build servers with the same result.

    Thursday, August 20, 2015 8:50 AM
  • Hi Mark,

    Thanks for your reply.

    I tested it in my default vNext build agent(installed on TFS 2015 RTM Server by default), the Git vnext build defintion worked fine, please check below screenshots:


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. Click HERE to participate the survey.

    Thursday, August 20, 2015 10:22 AM
    Moderator
  • Looks the same as mine

    I've set up a test TFS2015 install and that works fine so it's definitely something wrong with my TFS installation, but I can't figure out what. Any ideas where I can look?

    Thursday, August 20, 2015 10:28 AM
  • Hi Mark,  

    Thanks for your reply.

    There’s no any error during upgrade to TFS 2015 RTM?

    If you create a new Git team project in your TFS 2015 RTM and add new solution in this new Git team project. Then create new vNext build definition to build this new solution, this new vNext build definition can run successfully or will receive the same error?


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. Click HERE to participate the survey.

    Friday, August 21, 2015 9:43 AM
    Moderator
  • Hi Mark,

    Have you confirmed that?

    If this issue has been resolved, please share your experience here.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. Click HERE to participate the survey.

    Friday, August 28, 2015 9:57 AM
    Moderator