October 8, 2015

GitSwarm Projects with All the Power of Helix

Git at Scale

In a previous article I explained how to start a GitSwarm project with a blank repo. But one of the key strengths of GitSwarm is how well it plays with others, and more specifically with the rest of the Helix platform. Today we’ll discuss very briefly how to establish that integration and what it provides.

Importing project content directly from Helix is pretty trivial once you have the system configured to do so, so let’s start with that. There are a few, simple steps to follow, as detailed in the GitSwarm help at http://[gitswarm]/help/workflow/importing/import_from_gitfusion, where ‘[gitswarm]’ is to be replaced with the host name of your GitSwarm server. If don’t already have it configured, you’ll be offered the correct link on the page used for creating new projects.

The short version of the story is that you need to add a few lines to the GitSwarm configuration file and restart the server, and make sure that your Helix Versioning Engine is configured to expose repositories via Git Fusion. You’ll know it’s configured properly when the project creation page offers you a list of the available repositories.

Creating a project and importing from Helix is then as simple as selecting the desired repository, filling out the rest of the fields, and clicking the “Create project” button. The process will take a little time, depending upon the number of files and history to be imported. Once finished, you’ll enjoy all the great features of GitSwarm while working directly with your Helix content.

This makes it possible for you to do what no other Git management solution has previously offered: work with tiny, Git-sized slices of an otherwise Helix-sized (read: huge) monorepo. The Helix Versioning Engine manages and versions any number or size of files, which GitSwarm then serves up with the simple kind of pull-request workflow Git developers prefer.

Even better, bidirectional, automatic mirroring will be configured as part of the creation process. So any changes made to your GitSwarm project will propagate to Helix (and vice versa) behind the scenes. This makes it possible for Git developers to enjoy all the other advantages of GitSwarm while others can work on the same project assets using a broader variety of Helix tools and work flows. The key point is to put the right tools in the hands of every contributor, coder, designer, artist, et al.

Every push to GitSwarm results in a parallel change list submitted in Helix (and vice versa), stamped with a variety of details from the Git commit. This makes it easy for DevOps and others to integrate and follow history in whatever direction the code takes.

GitSwarm is free and ready for download, so why not give it a try?