Self-Hosted

Runners

Configuration file

Example delivery workflows for PHP, Node, React.js, Python, Ruby, .NET Core & more.

Node.js

Java

JavaScript

Python

Ruby

.NET Core

Android

React.js

React Native

C/C++

Angular

Aurelia

Clojure

Django

Elixir

Ember.js

Gatsby

Haskell

Hexo

Hugo

Jekyll

Middleman

Scala

Workflows

Automate deployment to your type of server or cloud service.

About Deployments

Azure

Capistrano

DigitalOcean

DigitalOcean Spaces

FTP/FTPS

Git pull

Git push

Google Cloud

Heroku

Netlify

Rackspace

Rsync

SFTP

Shopify

Vultr

Deployments

Customize your build and store sensitive data with environment variables.

Environment variables are pairs of key and value that can be used to customize the build process and store sensitive data.

Introduction to variables

Buddy populates a number of environment variables during each pipeline run.

Default variables

Variables can be combined with other words to create longer phrases than can be used.

Variable phrases

To further optimize your builds, you can pass values of variables between actions, pipelines and runs.

Passing variables

Variables

Manage your team thanks to wide range of collaboration tools in Buddy

Manage workspace users to control project flow effectively.

User management

Explore role management options for better workflow control.

User Roles

Restrict or grant pipeline-specific access to specific users or entire groups.

Pipeline permissions

Check how you can customize access with permissions.

Integration permissions

User groups allow for easier team management.

Groups

Learn more about workspace administrators and what they are able to do.

Administrators

Activity streams allow you to monitor actions taken by the members of your worspace.

Activity streams

User managment

General information regarding subscription options and pricing.

Billing gives you access to all the necessary information related to your CI/CD expendetures

Billing & Usage

GB-minutes are the spending unit consumed by running pipelines and our main appraisal method for workspace usage.

GB-minutes

Buddy offers a variety of plans all of which are fully functional CI/CD delivery systems but vary in terms of resources and some more advanced features

Plans and Features

Billing

Learn how to change the name, URL handle, and owner of your workspace.

General settings

Learn how Buddy helps keep your workspace safe from unauthorized access.

Security

Configure and use SAML SSO to manage users and permissions.

Single Sign-On (SSO)

Workspace settings

Check how you can protect your sensitive data in Buddy.

When using certain pipeline actions in Buddy, providing sensitive data may be required. 

Private data in actions

In addition to securing sensitive data in pipeline actions, Buddy also provides encryption for environment variables

Variable encryption

If you are using YAML configuration, there are two ways you can handle your sensitive data

Secrets in YAML

Configuration files often contain sensitive data. Depending on the application version they are different, which means you need to deploy them together with the app files.

Data in configuration files

Secrets and encryption

Basics

Familiarize yourself with the basics of how pipelines operate.

Learn more about private dependencies and submodules configuration.

New pipeline

There are multiple ways you can trigger a pipeline, helping you adjust to diffrent deployments scenarios

Triggering pipelines

Each pipeline has its own configuration and filesystem attached. You can create multiple pipelines that will run different tasks within one repository.

Pipeline list

The Runs tab displays the recent history of executions and configuration changes of the given pipeline.

Pipeline history

Pipeline filesystem

Analytics tab provides you with more information about the perofrmance of your builds.

Analytics

Advanced settings

Introduction

Check out how Buddy caches your files to speed up the deployments.

Each pipeline has its own filesystem. On the first pipeline run, the repository is cloned to the filesystem.

Filesystem cache

Builds, tests, and other commands defined in the build action are executed in the context of the filesystem containing the repository. This is the primary cache of the pipeline.

Build action cache

All layers created in Docker-building actions are cached. During subsequent builds, Buddy adds only the layers that have not been built in the previous step.

Docker cache

Sometimes you may want to clear the cache – for example, if you need to regenerate the artifacts. In such case, you can either clear the cache manually, or select an option which will do that automatically before every execution.

Cache maintenance

Cache

Learn more about builds and tests you can perform in Buddy

Builds & testing

Run multiple pipelines and actions in parallel to speed up your workflow.

Concurrency & parallelism

Learn how pipelines and actions can be configured to run on specific conditions.

Conditional runs

Migrate databases and run custom scripts on remotes with the SSH action.

DB migrations & custom scripts

Variables are pairs of keys and values that can be used to customize the build and to store sensitive data.

Variables in Buddy are highly customizable not only in their function but also scope

Scope and configuration

Variables can be combined with other words to create longer phrases than can be used

Combining phrases

For effective workflow automation, you may want to sometimes pass variables between pipelines and actions.

Parameterized pipelines offer a powerful way to customize and configure your workflows in Buddy.

Passing parameters on run

Passing parameters between pipelines

Manual approval

Parameterized pipelines

Learn how to organize your Buddy pipelines with application folders

Folders

Learn how to upload and use SSH keys to authenticate deployment and script execution on remote servers.

SSH keys

Learn more about personalizing GitHub status badges in Buddy

Status badges

Learn more about managing private dependencies in Buddy.

Private dependencies

Learn about using submodules in Buddy to integrate between different projects.

Submodules

Learn about deploying submodules and private dependencies in Buddy.

Deployment

Learn how to use private modules from an npm registry in your Node projects.

Node.js packages

Learn how to download private Composer packages and use them in your PHP actions.

Composer PHP packages

Buddy lets you easily reproduce both individual actions and complete pipelines without the need to manually configure actions every time you do it.

When you duplicate a pipeline, Buddy creates an exact copy of all the pipeline's actions and settings.

Duplicating

You can export pipeline configuration to YAML files that can be easily used in any new project or workspace.

Export / Import

Copy pipeline

Detailed use cases showcasing how you can use Buddy in actual development process.

Learn how to invalidate cache after deployment with Buddy's pipelines

CDN invalidation

Creating a delivery automation pipeline in Buddy is simple and effortless. Here's an example of a Continuous Delivery pipeline setup in Buddy.

Continuous Delivery

An example of how to build a Continuous Deployment pipeline in Buddy.

Continuous Deployment

Learn how simply you can create a daily integration tests pipeline using Buddy.

Daily integration tests

See how easy it is to automate your process using Buddy deployment pipeline.

Deployment pipeline

Learn how to validate the URLs on your website using the dedicated Link Checker action.

Link validation pipeline

Create a simple monitoring pipeline using Buddy and automate your maintenance.

Monitoring pipeline

Check how simple it is to run pull-request tests using Buddy.

Pull requests testing

Learn how to configure conditional pipeline triggering by using tags in Buddy

Release after every tag push

Learn how easily you can create on-push tests using Buddy.

Run tests after every push

Learn how to attach Selenium services to your builds and run browser tests on your apps and websites.

Selenium tests

Learn about using settable variables for semantic versioning in Buddy.

Semantic versioning and settable variables

There is nothing more frustrating than taking your app down for maintenance. See how you can reduce the application downtime to zero using a zero downtime deployment configuration in Buddy.

Zero-downtime deployment

Pipeline examples

Pipelines

Predefined actions are the building-blocks of every pipeline.

About actions

Learn how to define your own custom actions using YAML

Action definition

Custom actions are defined as code in a similar manner to default Buddy actions.

YAML Configuration

If your custom action has inputs defined, they are displayed in the Setup tab of the action.

Custom tabs

Actions should be created and updated in the default branch of the repository and versioned with Git tags.

Name	Type	Description
`--drain`	Boolean	Defines whether the runner is set to draining mode.
`--standalone-host`	String	The IP address of the main instance. Cannot be empty.
`--token`	String	The authorization token generated by the installation wizard. Can be regenerated with `buddy configure`
`--runner-memory`	Number	The amount of RAM in MB allocated for the runner service.
`--tag`	String	The tag applied to the runner. If set to empty (`tag: ""`), the tag is cleared.
`--cpus`	String	The number of CPUs that can be used by the build actions on the runner. Can be equal to `0` (unlimited) or greater.
`--memory`	Number	The amount of RAM in MB that can be used by the build actions on the runner. Can be equal to `0` (unlimited) or greater.
`--concurrent`	String	The number of concurrent pipeline runners on the runner. Can be equal to `0` (unlimited) or greater.
`--internal-host`	The IP address that will be bound by the runner. Default value: empty (binds to all IP's on the server).
`--external-host`	The external IP address of the server as seen by the primary server. Default value: the first detected external IP address.
`--runner-internal-port`	Number	The listening port of the runner. Can be changed if the port is taken. Must be > 0 or will be ignored.
`--runner-external-port`	Number	The external port of the runner to which Buddy self-hosted is connecting. Can be changed if the ports are mapped. Must be > 0 or will be ignored
`--registry-internal-port`	Number	The listening port of the registry. Can be changed if the port is taken. Must be > 0 or will be ignored.
`--registry-external-port`	Number	The external port of the registry to which Buddy self-hosted is connecting. Can be changed if the ports are mapped. Must be > 0 or will be ignored.