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,463,474
Community Members
 
Community Events
176
Community Groups

How to use secrets in code as variables in pipeline?

Hello guys, I am using Selenium with Java Maven for automation UI testing. In the photo bellow I use username/password from .env file and is working perfectly fine locally.

Screenshot_1.png

My question is how and is it possible to setup TEST_USERNAME and TEST_PASSWORD as variables in Bitbucket and use them during the pipeline?

 

1 answer

0 votes

Hi @Vladimir Parlikj and welcome to the community!

You can define Pipelines variables
- either for a workspace (they can be used by all repos in that workspace)
- or for a repository (they can be used in that repo only)
- or as deployment variables (they can be used only in a deployment step of that specific deployment)

You can see more details here:

If you define a variable named TEST_USERNAME, then you can reference it in a file as ${TEST_USERNAME}

If you don't want to make use of Pipelines variables and you want to use the .env file you have, then you can

- commit the .env file in the repo (if it's not part of the repo already)
- source it at the beginning of the build, e.g. if the file is named build.env

source build.env

- you can then reference the variable the same way, as ${TEST_USERNAME}

Is this something that works for you? Or do you perhaps have some different/additional requirements?

Kind regards,
Theodora

You are welcome Vladimir, please feel free to let me know if you need anything further!

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events