ChangelogDocsPricingContact
Sign inInstall Self-Hosted
Get Started on Cloud
AboutX (Twitter)support@buddy.works
BasicsPipelinesActions & ServicesEnvironmentsIntegrationsTargetsDomainsSelf-HostedAgents & TunnelsYAMLBuddy GitTroubleshootingAPI
  • Pipelines
Pipelines
Introduction
New pipeline
Creating a pipelineYAML templates
Triggering pipelines
Basic trigger modes
Manual triggerOn git eventOn scheduleWildcards
Advanced trigger types
WebhooksREST APICommit commandsSlack slash commands
Trigger pipeline action
Pipeline listPipeline historyPipeline filesystemAnalyticsAdvanced settings
Cache
Filesystem cacheBuild action cacheDocker cacheCache maintenance
Builds & testingConcurrency & parallelismConditional runsDB migrations & custom scripts
Variables
Scope and configurationCombining phrasesPassing variables
Parameterized pipelines
Passing parameters on runPassing parameters between pipelinesManual approval
FoldersSSH keysStatus badges
Private dependencies
Private dependenciesSubmodulesDeploymentNode.js packagesComposer PHP packages
Copy pipeline
DuplicatingExport / Import
Pipeline examples
CDN invalidationContinuous DeliveryContinuous DeploymentDaily integration testsDeployment pipelineLink validation pipelineMonitoring pipelinePull requests testingRelease after every tag pushRun tests after every pushSelenium testsSemantic versioning and settable variablesZero-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

© 2025

All systems are operational