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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

How do you define deployment environment variables at the workspace level?

All of our bitbucket pipelines for all our repos use the same environments and same secrets. I suspect this is common for many other users too.

I don't want users to have to add these same environment variables to every repo they create because they could all be the same and be defined at the workspace level once.

How do you do this? When I look at the PIPELINES setting at the workspace level I see only: 

* Workspace runners
* Workspace variables

Where is "Workspace environments" ?


1 answer

0 votes
Mark C Atlassian Team Jul 12, 2022

Hi @Ben Orgil,

Thanks for reaching out to the community.

Unfortunately, we do not have a setting where you can add deployment environment variables at the workspace level.
However, I do believe it is a useful feature to be able to set/add that at the workspace level.
For this, I went ahead and created a feature request for it that can be located through this link. -
You can upvote and watch it for now so that you'll be notified of any updates from our team when the feature becomes available on Bitbucket Cloud.
Please do note that we don't have an exact ETA for the feature request as all new features will be implemented according to our policy here.

As a workaround, instead of using deployment environment variables, you can add your variables to the Workspace level environment variables instead.
For now, you'll have to manage the variable naming based on your environments (e.g. for Staging/test, production).

Do let me know if you have further questions.

Mark C

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events