Our `bitbucket-pipelines.yml` contains `stepdefinitions` that do nothing more than write a configuration file:
image: ourcompany/our-custom-docker-image
clone:
lfs: true
depth: 1
stepdefinitions:
- configure-deployment-staging: &configure-deployment-staging
deployment: staging
name: Configure deploy staging
image: alpine
script:
- echo "PROJECT=project-staging" >> deploy.properties
artifacts:
- deploy.properties
- configure-deployment-production: &configure-deployment-production
deployment: staging
name: Configure deploy production
image: alpine
script:
- echo "PROJECT=project-production" >> deploy.properties
artifacts:
- deploy.properties
- deploy: &deploy
script:
- set -a
- . ./deploy.properties
- set +a
- deploy.sh #actually more that I don't want to duplicate
pipelines:
custom:
deploy-staging:
- step: *configure-deployment-staging
- step: *deploy
deploy-production:
- step: *configure-deployment-production
- step: *deploy
I want to speed up the pipeline by skipping the cloning of the project for the `configure` steps. Is it possible, in general, to have steps where the repo is not checked out?
