configuring steps in pipelines. Do we need repeated steps? Edited

I have configured 3 steps in pipelines


build UI and static assets

deploy UI to website

Deploy assets to CDN


I notice i have to install yarn for each step and yarn install. Is it possible to only do this for 1 step. Seems strange it has to install yarn and install the packages 3 times before it can run the command.

- step Build UI and assets


- curl -o- -L | bash -s -- --version 1.3.2

 -export PATH=$HOME/.yarn/bin:$PATH

- yarn install

- yarn run build:ui

- yarn run build:assets

-step Deploy UI to website

script: - curl -o- -L | bash -s -- --version 1.3.2
- export PATH=$HOME/.yarn/bin:$PATH

- yarn install

- yarn run deploy:ui


1 answer

0 votes

Hey Gavin,

you could look at configuring artifacts. You define which folders you want to preserve in your first step, and then these are passed along in your subsequent steps. 


Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

673 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot