Helix GitSwarm Live Demo
Your Questions Answered
Our 20-minute, live demo of Git management using Helix GitSwarm attracted an impressive turnout, and I would like to thank everyone who attended. If you missed it, keep an eye out for the next one on the demo registration page as we will continue to present our solutions.
Git management using Helix GitSwarm provides a collaborative Git workflow that users know and love while providing the scalability, security, and policy that enterprises require.
In our last webinar, we had so many questions from participants that we didn’t have time to answer them all. So, I would like to take the time to address them in this blog post. If you don’t see the question or answer that is on your mind, please contact us at firstname.lastname@example.org
Q. Is there a step-by-step installation guide to facilitate setting up a Helix GitSwarm server and typing it into a Helix Versioning Engine?
A. The documentation is pretty comprehensive and lays out all of the installation requirements and procedures. Other aspects, such as configuring Helix mirroring are shown in the documentation as well. Linux package installation is the easiest way to install GitSwarm and it will deploy a Helix Versioning Engine (with all dependencies) automatically. However, if you were looking for something akin to a Quick Start installation guide, we don’t currently have a single-page installation document — even though that would be a great idea. We have added that to an enhancement request.
Q. Does Perforce provide any upstream contributions to Gitlab?
A. Yes. We are actively contributing to the GitLab CE project.
Q. Are there video demos of how to set up the connection between Helix and Git? Since this is a complex activity, having access to that type of resource would be great.
A. There are no demo videos of installation and configuration at this time, but that is another great idea. We will definitely look into creating one. In the meantime, you can ask us to show you how to configure a Helix-Git connection via demo. Please contact us at email@example.com
Q. How often does GitSwarm synchronize a project that is mirrored in Helix? Is that configurable?
A. The default is for GitSwarm to pull from Helix every 5 minutes, but you can change this rate in the GitSwarm configuration file.
Q. Is this integration still Git Fusion under the covers? Is this UI just adjusting Git Fusion configuration behind the scenes?
A. For projects already in the Helix Versioning Engine, Git Fusion creates the Git repos of projects that will be managed in GitSwarm. The answer to the second part of this question is yes. GitSwarm utilizes Git Fusion to define and create Git repos when projects are mirrored to the Helix Versioning Engine or when you create a narrow, or shallow, repo of a project in Helix.
Q. For those already familiar with GitLab, is there a document outlining the ways in which GitSwarm diverges from GitLab?
A. Our release notes (https://www.perforce.com/perforce/doc.current/user/gitswarm-relnotes.txt) indicate which version of GitLab (8.10 as of this writing) our GitSwarm is based on, all major and minor functionality improvements, and fixed bugs.
If you are interested in a personalized demo of GitSwarm, don’t hesitate to reach out to us at firstname.lastname@example.org. We would be happy to schedule a demo.