Copy files from another pipeline with YAML

YAML parameters for Copy files from another pipeline

You can find the list with common parameters for all Buddy actions here.

NameTypeDescription
action
Required		StringThe ID of the action.
type
Required		StringThe type of the action. Should be set to COPY_FILES.
source_pipeline_id
Required		IntegerThe ID of the pipeline from which files will be copied. Not required if both source_project_name and source_pipeline_name are set instead.
source_project_name
Required		StringThe name of the project containing the pipeline from which files will be copied. Not required if source_pipeline is set instead.
source_pipeline_name
Required		StringThe name of the pipeline from which files will be copied. Not required if source_pipeline is set instead.
source_pathStringThe path in the source pipeline’s filesystem.
target_pathStringThe path in the current pipeline’s filesystem.
deployment_excludesString[]The paths and/or files that will be left out during the deployment.
deployment_includesString[]The exceptions from the ignore patterns set in deployment_excludes.
copy_hidden_filesBooleanWhen set to true the hidden files and folders (the ones with the name beginning with a ".") are copied.

YAML example for Copy files from another pipeline

actions:
  - action: "Copy files from  backend/dev"
    type: "COPY_FILES"
    copy_hidden_files: true
    trigger_time: "ON_EVERY_EXECUTION"
    source_project_name: "backend"
    source_pipeline_name: "dev"
    source_path: "/src"
    target_path: "/www"
    deployment_excludes:
    - "/tmp"
    - "*.log"
    deployment_includes:
    - "/tmp/assets"
    - "/tmp/styles"
Questions?

Not sure how to configure a pipeline for your process? Reach out on the live-chat, contact support, or ask our community on our forum.

Sign up for Buddy Digest

Best practices on CI/CD and fresh changelogs delivered weekly to your inbox.