Forge Home


Installs and configures Perforce Gitswarm


7,735 latest version

4.3 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.2.4 (latest)
  • 0.2.3
  • 0.2.2
  • 0.2.1
  • 0.2.0
  • 0.1.3
  • 0.1.2
  • 0.1.1
  • 0.1.0
released Jan 3rd 2016
This version is compatible with:
  • Puppet Enterprise >= 3.0.0 < 2015.4.0
  • Puppet >= 3.0.0 < 5.0.0
  • , , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'alanpetersen-gitswarm', '0.2.4'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add alanpetersen-gitswarm
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install alanpetersen-gitswarm --version 0.2.4

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



alanpetersen/gitswarm — version 0.2.4 Jan 3rd 2016



Installs and configures Perforce GitSwarm. See the following for more information:


Usage is pretty simple. You can simply include the gitswarm class to configure GitSwarm on the node:

include gitswarm

The base class determines the $::osfamily of the node and includes the appropriate os-specific class: gitswarm::debian or gitswarm::redhat.

If you want to customize how GitSwarm is installed, you can either use hiera to specify parameters, or you can declare the os-specific class with the appropriate parameters set. For example, on CentOS 7, you could do something like:

class { 'gitswarm::redhat':
  pkgname            => 'helix-gitswarm',
  pubkey_url         => '',
  yum_baseurl        => '',
  perforce_repo_name => 'perforce',


The installation will create an administrative account in GitSwarm called root with the password 5iveL!fe. When you log in, you will be asked to change that password to something that isn't on a README page on GitHub.

Once logged in, you can create projects, new users, groups, etc.

The P4D Instance

The installation creates a P4D instance running on ssl::1666. Logged into the instance, you can run p4 info to get more information:

Logging In

There are several Perforce user accounts that are created initially in the instance:

The gitswarm user has an existing ticket

And that user is a superuser

So you should use that account to set the password for the root account in p4d:

Note that security is configured to be level 3, so strong passwords are required.

HINT: If you don't log in before the ticket expires (12h), then you can find the generated password in the /etc/gitswarm/gitswarm.rb file. Do not change the gitswarm user's password without consulting the GitSwarm documentation! Bad things may happen if you do.


Currently, only supports RedHat/CentOS. Debian coming soon.