This action will copy files from one pipeline filesystem to another. It's most commonly used with apps that have multi-repository structure, like back-end and front-end, for passing arguments from one pipeline to another or to archive artifacts in the pipeline’s filesystem.
Split tests Alternatives
Weighing your options? Checkout these 6 alternatives that could help you accomplish your goal.
This action finds & replaces strings in a specified file in the pipeline filesystem. Often used to generate configuration files with pipeline variables from templates stored in the repository.
This action asks user via Buddy web UI to pass arguments to pipeline for other actions to use.
This action triggers another pipeline from the same or from another project. The action allows to create waterfall-type of workflows or to trigger another pipeline in parallel after a specific stage has been completed. It also allows a streamline management of multi-repository applications.
This action pauses pipeline execution for specified number of seconds.
This action stops pipeline execution and ask a user if the pipeline should proceed. The pipeline execution is paused until approval is given . It allows an easy switch between continuous delivery and continuous deployment scenarios and creates multi-level deployment acceptance rules.