Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,293,245
Community Members
 
Community Events
165
Community Groups

Multiple steps are not useful

Deleted user Sep 02, 2018

As a user, I want to be able to logically group my testing/building/deploying steps.

However, the current step implementation does not seem to be set up to do this effectively. Does bitbucket allow any way to share data (artifacts and/or caches) between steps that doesn't require uploading/downloading to s3?

Example:

Step 1) Build frontend app, run tests
Step 2) Build backend app, run tests
Step 3) Build new docker containers
Step 4) Deploy new frontend/backend assets and containers to server

As you can see, each of these steps have some overlap. They all need to download the same caches (docker, node modules, etc), and data/artifacts from steps 1 and 2 (eg, app.bundle.js, all static assets, etc) could easily be reused in steps 3 and 4.

Because steps run in total isolation isolation, caches (which can get quite large and time-consuming to download) have to be downloaded each time. Sharing any data between steps (via artifacts) requires an upload to s3, and then downloading it right after. So, it ends up being far more efficient to just run everything as one giant step.

Having one giant step is very unfortunate because in order to see why a build failed I need to dig through a giant log file without any help from the UI. It also removes the ability to rerun failed steps (ie, if the tests passed but the deploy failed, I have to run the entire thing over from scratch, instead of just the last step).

How are others dealing with this? My situation does not feel unique.

Thanks!

0 comments

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

2,084 views 2 9
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you