Pipelines for Applications

The Puppet Pipelines appliance consists of two OVA files in OVF 1.0 format.

These images can be imported into most virtual hosting packages, including VMWare.

System requirements

  • The Puppet Pipelines build server must be able to communicate with Pipelines.
  • The Puppet Pipelines build server must be able to communicate with Docker Hub to push/pull build images on setup.
  • If the desired version of the enterprise software isn't already on disk, the Puppet Pipelines server requires internet connectivity to download software.

Install and set up the appliance

Use the links below to download the two images.

  1. puppet-pipelines-server.ova This is the main Puppet Pipelines server image. It includes MySQL databases configured for Pipelines and Artifactory, an install of Artifactory configured as a generic large object store, and Pipelines bits and install script on disk.

  2. puppet-pipelines-build-server.ova This is a preconfigured Puppet Pipelines shared build server. This includes an installation of Docker and is pre-populated with various Docker build images. For more info on shared build servers, see Set up Shared Build Images.

Install the Puppet Pipelines server

  1. Import the puppet-pipelines-server.ova image into your virtual hosting platform.

    Minimum requirements: 6 GB RAM, two CPUs, 500 GB disk space.

  2. Start the virtual machine. The default username for the VM is pipelines and the default password is puppet.

  3. SSH to the virtual machine as the pipelines user.

  4. Run ./pipelines-install.sh | tee install_output.log. The script will bootstrap the Puppet Pipelines server.

    This install script can be used as-is in simple environments. If needed, select variables can be overwritten to cusomize the installation:

    • IPADDRESS - defaults to the IP of the interface associated with the default gateway.
    • PIPELINES_EMAIL - username for the Pipelines web UI root user.
    • PIPELINES_PASSWORD - password for the Pipelines web UI root user.
  5. Verify that Puppet Pipelines is up and running by navigating to the server at http://:8080.

    If necessary, determine the IP or FQDN of the server by logging into the VM console as the pipelines user and running facter ipaddress.

  6. Install an enterprise license, then log into the Puppet Pipelines web UI as the root user, using either the default credentials above or those you customized in the install script.

Install the shared build server

  1. Import the puppet-pipelines-build-server.ova image into your virtual hosting platform.

    Minimum requirements: 4 GB RAM, one CPU, 200 GB disk space.

  2. Start the virtual machine. Note that the IP address of the VM is shown as part of the VM console’s login prompt.

  3. On the command line, SSH to the virtual machine as the pipelines user.

  4. Run the setup script:


    When prompted, enter the address of the Puppet Pipelines server.

  5. Next, the setup script will install the Pipelines agent. When prompted, enter your agent credential access token and secret key, which can be found in the Pipelines web UI by clicking Settings > Agent.

    When the Pipelines agent starts, the shared Docker build images are rebuilt with the local agent embedded in them.

At this point, when you open the Pipelines for Applications web UI, you’ll see the new build server listed on the Servers page.

Update config file

Finally, update the Pipelines shared image Docker config file. This file can be found on the Pipelines server at:


  1. Locate "DockerImages" : { in the JSON blob, and update the file to include these entries:

    "gamma/*/DockerImages" : {
        "pipelines-base": "Pipelines Base",
        "pipelines-android": "Pipelines Android",
        "pipelines-go": "Pipelines Go",
        "pipelines-jvm": "Pipelines Java",
        "pipelines-javascript": "Pipelines Javascript",
        "pipelines-perl": "Pipelines Perl",
        "pipelines-php": "Pipelines PHP",
        "pipelines-python": "Pipelines Python",
        "pipelines-ruby": "Pipelines Ruby"
  2. Adjust your file settings and save the file.

  3. Restart the Pipelines agent supervise process by running:

    sudo distelli supervise stop
    sudo distelli supervise start

Your Puppet Pipelines appliance installation is now complete and ready to be used.


Default credential for Username Password
VM (SSH or console) root puppet
VM (SSH or console) pipelines puppet
MySQL (full privileges) root puppet
MySQL (localhost access to artifactory) artifactory puppet
MySQL (localhost access to pipelines) pipelines puppet
Artifactory UI admin password
Pipelines web UI [email protected] puppet

We strongly recommended changing these passwords. Realize that if you change a password, you also must change the password in the install script.

Back to top
The page rank or the 1 our of 5 rating a user has given the page.
The email address of the user submitting feedback.
The URL of the page being ranked/rated.