We are trying to setup git-sm integration with the UiPath studio but to no avail.
We created a server (VM) hosted on our network and installed git-sm, but we are stuck in connecting UiPath Studio.
All of the documentation available is pointing out to GitHub repositories, is there any UiPath documentation or any media showing the steps of such a scenario?
It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.
First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.
You can check out some of our resources directly, see below:
Always search first. It is the best way to quickly find your answer. Check out the icon for that.
Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.
Topic that contains most common solutions with example project files can be found here.
Read our official documentation where you can find a lot of information and instructions about each of our products:
Meet us and our users on our Community Slack and ask your question there.
Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.
Thank you for helping us build our UiPath Community!
We’ve finally been able to integrate git-scm with UiPath Studio using https connection rather than ssh - the solution worked with a local git server and apache (although we use Azure and IIS is preferred) nevertheless, you can do the same by following some of the below instructions:
Apache fresh installation provides http connection therefore you need to configure your ssl certificate and key.
There is too much configuration you need to do in Apache to allow the git-http-backend CGI to receive and send packages (GIT Repos push and pull). Happy to answer questions
We reviewed the configuration and the maintenance procedures of this setup and we actually opted out since the maintenance is somehow hectic - it all comes down to how you want to collaborate. would love to hear how your organization is dealing with developer collaboration and have more. insights.