You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
In our bitbucket account, there are multiple users. Each user has his own secrets for accessing his own AWS environment.
We have a generic pipeline that we use for running the tests on the user's own environment. This is done by having Repository Variables set for all users and then the pipeline takes the correct environment based on the user that requested the pipeline.
This is wrong, but we failed to find a better way to solve this.
My question is this, is there a way to set user-level environment variables that based on the initiator of the pipeline, these own user level environment settings will be also available during the build?