Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,457,881
Community Members
 
Community Events
176
Community Groups

Running tests after deployment best practices

I see questions for this related to bamboo. But I’m using bitbucket cloud. 

What is the best process for running integration tests post-deployment? Should that be in the deployment step/script? Or a build step that runs after the deployment in the pipeline? Is it even possible to run a build step after a deployment step? If so, how do I make sure I don’t run another deployment while the build(tests) are running. 

I’m thinking it makes most sense to run the tests as a part of the deployment step, as then the deployment can pass/fail as a whole. Also keeps deployments in other pipelines for the same environment from running. 

looking for confirmation on this approach or other ideas. 

Thanks!

1 answer

Hey Brendan, 

Environment in Bitbucket is defined at a step level unfortunately, previously I have worked with Gitlab which did not have this limitation.

As per https://support.atlassian.com/bitbucket-cloud/docs/deployment-concurrency-control/ the deployments are paused if there is one running for the environment.

So it makes sense to add them in the same script and not as a separate step.


Also, generally one should run the tests before the deployment happens, is there a reason there is a post-deployment test run? If that fails would you rollback?

Or by deployment you mean just the build process?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events