Forge Home


Installs and configures Perforce GitFusion


7,572 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.0 (latest)
  • 0.1.0
released May 9th 2016
This version is compatible with:
  • Puppet Enterprise >= 3.0.0 < 2017.0.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-gitfusion', '0.2.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

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

Manually install this module globally with Puppet module tool:

puppet module install alanpetersen-gitfusion --version 0.2.0

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/gitfusion — version 0.2.0 May 9th 2016



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


NOTE: This version of the Git Fusion module installs the Git Fusion binaries, but does not install the helix p4d service. Git Fusion can be configured to point to a local instance or remote instance.

class { 'gitfusion':
  p4super          => 'p4super',
  p4super_password => 'p@ssw0rd',
  gfp4_password    => 'p@ssw0rd',

Class Parameters

The following parameters are available in the gitfusion class:

  • p4super -- REQUIRED -- the existing superuser account that will be used to configure the Git Fusion repo, triggers, etc. in the Perforce Helix instance.
  • p4super_password -- REQUIRED -- the password for the Perforce superuser account.
  • gfp4_password -- REQUIRED -- the password to be used for the Git Fusion accounts created in Perforce.
  • gf_sys_user -- the system user to run Git Fusion as. If the user does not exist, it will be created. Defaults to "git".
  • gf_dir -- the path to the Git Fusion executable files.
  • server -- the server type to be used with this Git Fusion instance. This defaults to 'local'. The valid values are:
    • local = use an existing Perforce service on this machine
    • remote = use an existing Perforce service on another machine
  • server_id -- the server id used to identify the Git Fusion server. Defaults to the current hostname.
  • p4port -- the P4PORT for the Perforce service. Defaults to '1666'.
  • timezone -- the Perforce service's timezone in Olson format.
  • unknownuser -- a flag that specifies how to handle the Perforce change owner for git commits authored by non-Perforce users. This defaults to 'reject'
    • reject = reject push which contains commits authored by non-Perforce users
    • pusher = accept commits authored by non-Perforce users and set the change owner to the pusher
    • unknown = accept commits authored by non-Perforce users and set the change owner to 'unknown_git'
  • https -- a boolean indicating whether or not Git Fusion should support HTTPS protocol using Apache. NOTE This module does not install Apache, that would have to be done before this module is configured.
  • debug -- a boolean flag which turns on debugging for the Git Fusion installer.

Hiera Usage Example

You can provide data for your Git Fusion management using Hiera. To do this, simply classify your node

include gitfusion

and then in your hiera data provide something like:

gitfusion::p4super: p4superuser
gitfusion::p4super_password: p4superuserpassword
gitfusion::gfp4_password: git_fusion_user_password
gitfusion::server: local
gitfusion::p4port: 1666