Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice
New Forum User Notice Update to the Unity Editor Software Terms Unite 2023 - Ask the Experts Online

Mercurial: ERROR: Failed to clone / abort: http authorization required error

Discussion in 'Unity Build Automation' started by dcarrigg, Mar 11, 2016.

  1. dcarrigg

    dcarrigg

    Joined:
    May 21, 2014
    Posts:
    24
    We're testing out Unity Cloud Build, and have been unsuccessful so far. Our log files show the following:

    Code (CSharp):
    1. 1: Running Prebuild steps
    2. 2: done.
    3. 3: bvr 1.2.1
    4. 4: bvr-api 0.2.0
    5. 5: $ hg clone --rev default --noupdate OURREPOLOCATION /BUILD_PATH/dcarrigg.uc-server.windows-desktop-64-bit
    6. 6: abort: http authorization required for OURREPOLOCATION
    7. 7: ERROR: Failed to clone OURREPOLOCATION
    8. 8: ERROR: Failed to clone OURREPOLOCATION
    9. 9: postbuildstatus finished successfully.
    10. 10: Deleting project workspace...
    11. 11: Finished: FAILURE
    We've verified the connection information, both our repo location and the username/password. Is there something else we could be missing?

    Thanks
     
    dcarrigg, Mar 11, 2016
    #1

  2. dannyd

    dannyd

    Unity Technologies

    Joined:
    Jun 3, 2014
    Posts:
    785
    Are you hosting the repo with a service, or is it on your own servers? Are you putting your credentials directly in the URL or adding the username/password through the setup wizard?
     
    dannyd, Mar 14, 2016
    #2

  3. dcarrigg

    dcarrigg

    Joined:
    May 21, 2014
    Posts:
    24
    We're using our own server in our office, which we can connect to externally as well. I've tried entering the username/password in the setup wizard, as well as adding them directly to the url... same log output either way.

    I also created a new user account, and double checked the credentials, which didn't seem to make a difference either.
     
    dcarrigg, Mar 14, 2016
    #3

  4. dannyd

    dannyd

    Unity Technologies

    Joined:
    Jun 3, 2014
    Posts:
    785
    This is going to require some investigation on our end. Can you PM me a link to the project so I can look into it?
     
    dannyd, Mar 16, 2016
    #4

  5. dcarrigg

    dcarrigg

    Joined:
    May 21, 2014
    Posts:
    24
    Message sent. Thanks for looking into this!
     
    dcarrigg, Mar 18, 2016
    #5

  6. linxuzi

    linxuzi

    Joined:
    Dec 28, 2012
    Posts:
    2
    we have the same problem
     
    linxuzi, Mar 26, 2016
    #6

  7. dannyd

    dannyd

    Unity Technologies

    Joined:
    Jun 3, 2014
    Posts:
    785
    @linxuzi: We have a fix for this specific mercurial error, however it is dependent on some changes that are part of a major infrastructure upgrade that is still several weeks away from being deployed. Will keep this thread updated once those changes are live.
     
    dannyd, Mar 28, 2016
    #7