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

Cloud build fails with private git unity package dependency

Discussion in 'Unity Build Automation' started by nextlevel, Sep 21, 2021.

  1. nextlevel

    nextlevel

    Joined:
    Jan 25, 2014
    Posts:
    6
    I have a project that uses a unity package for part of the code. Both the main project and the unity package are hosted on bitbucket as separate private repositories, within the same account.

    When I try to cloud build, it fails with:

    Error when executing Git command:\n git fetch ... failed with code 128\n \n - stderr: fatal: could not read Password for 'https:// ... terminal prompts disabled\n","level":"error"}

    How do I get Unity Cloud Build to authenticate to be able to fetch the git package during the build?
     
    arproducties likes this.
  2. arproducties

    arproducties

    Joined:
    Sep 7, 2017
    Posts:
    14
    Did you find a solution? I am getting the same error
     
  3. rajivrao

    rajivrao

    Unity Technologies

    Joined:
    Feb 19, 2019
    Posts:
    111
    I would suggest submitting a ticket for this. Would be helpful for the team to see the error log to understand what's going wrong with the authentication process.
     
  4. unclejey34

    unclejey34

    Joined:
    Dec 21, 2017
    Posts:
    53
  5. arproducties

    arproducties

    Joined:
    Sep 7, 2017
    Posts:
    14
    I had to manually add the ssh url in the manifest in unity 2018. For me it was fixed by replacing the ":" in the bitbucket copied ssh url to a "/". It was able to access the package with the same ssh key used to pull the original project, since both of them are on the same private repository. Maybe this will not work if the package is on a different private repo.