ChangelogDocsPricingContact
Sign inInstall Self-Hosted
Get Started on Cloud
AboutX (Twitter)support@buddy.works
BasicsPipelinesActions & ServicesEnvironmentsIntegrationsTargetsTestsDomainsSandboxesSelf-HostedAgents & TunnelsYAMLBuddy GitFAQAPI
  • Pipelines
Pipelines
Introduction
New pipeline
Creating a pipeline
Workflow Configuration
YAML templates
Triggering pipelines
On git event
Webhook Trigger
Manual trigger
On schedule
Wildcards
Trigger pipeline action
Advanced trigger types
REST API
Commit commands
Slack slash commands
Contexts
Pipeline loop
Pipeline list
Pipeline filesystem
Pipeline history
Analytics
Advanced settings
Cache
Filesystem cache
Build action cache
Docker cache
Cache maintenance
Builds & testing
Concurrency & parallelism
Conditional runs
DB migrations & custom scripts
Variables
Scope and configuration
Combining phrases
Passing variables
Parameterized pipelines
Passing parameters on run
Passing parameters between pipelines
Manual approval
Folders
SSH keys
Status badges
Private dependencies
Private dependencies
Submodules
Deployment
Node.js packages
Composer PHP packages
Copy pipeline
Duplicating
Export / Import
Pipeline examples
CDN invalidation
Continuous Delivery
Continuous Deployment
Daily integration tests
Deployment pipeline
Link validation pipeline
Monitoring pipeline
Pull requests testing
Release after every tag push
Run tests after every push
Selenium tests
Semantic versioning and settable variables
Zero-downtime deployment
  • Pipelines

Cache

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

What does cache contain?

List of elements that are currently cached:

  1. Repository files, dependencies and artifacts (cached within the pipeline filesystem)
  2. Docker images in which build actions are run (no need to build the environment from scratch every time)
  3. Docker images used in the Run Image action
  4. Docker layers built with the Build Image action

You can also enable cache for services and databases attached to build actions or an extra cache

  • Filesystem cache

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

  • Build action 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.

  • Docker 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.

  • Cache maintenance

    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.

Resources

  • Docs
  • API
  • Terraform
  • Guides
  • Download Self-Hosted
  • Security
  • Blog
  • Tutorials

Company

  • About
  • Customers
  • Support
  • X (Twitter)
  • Responsible Disclosure
  • GDPR
  • Terms of Service
  • Privacy Policy
SOC2
SOC2

© 2026

All systems are operational