-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Authentication for HTTPS cloning #298
Comments
Gitman calls
Does that work? Here are the setup docs in case you missed them: https://gitman.readthedocs.io/en/latest/setup/git/ |
As mentioned try at first to clone the repository via calling git as subprocess to investigate the problem without gitman. |
I am currently investigating this as I would like to find a solution that works both for local development and CI. I would prefer to configure git using command line for automatic build to be authenticated as well. FYI I am working with Azure Pipelines. It seems like if you would like to use the |
You could try passing the extra parameter using the Unfortunately that will mean keeping your secret in Git, but let's see if it clones first, then work on alternative approaches. |
I manage to authenticate to the repository using the system token in Azure DevOps like so. In addition I had to disable Locally I simply used the Git credential manager. This setup allows me to have the same Gitman configuration file for both local development and automated builds in Azure DevOps using HTTPS. |
@SebastianBalle thanks for sharing! Would that be worth adding to the setup docs or do you think it's mostly specific to your situation? |
@jacebrowning I think this would be valuable to add if you are considering having some documentation on CI implementations. The documentation only describes the local development which, I would say, is only half of the work. You could of course simply redirect the user to the official documentation page from the different CI providers but it would be cool if you could have a small compact guide for how to implement the tool in the different systems. I can help draft such a documentation for Azure DevOps at least. |
I am currently investigating replacing our current git submodules with Gitman, however all our repositories are private hence authentication is required. It is not clear to me how Gitman configures authentication when cloning private repositories using HTTPS. All HTTPS examples are using public repositories on Github.
I would like to avoid using SSH.
Example of error when trying to access private repository using HTTPS with Azure DevOps:
I am using Gitman v3.3.1
The text was updated successfully, but these errors were encountered: