We need access to our private repos in pipelines and its a bit cumbersome when you have a lot of repos to add the ENV var for the private access key and the public access key to every repo.
So we added the private key to a team ENV var. But it still cant access!?
The docs say "Environment variables specified for a team or an individual account can be accessed from all repositories that belong to the team or account."
Does "belong" mean, projects that are owned by the team or also projects that the team has read/write access to?
A solution how to make *many* depending private repositories accessable at a time in pipelines would be great.
Any suggestions welcome.
> Does "belong" mean, projects that are owned by the team or also projects that the team has read/write access to?
Belong means the owning team or account.
Let's say I have a team called "atlassian" and a repo "website" -> url would be https://bitbucket.org/atlassian/website. Then the "owner" of website is atlassian.
If I added environment variable PRIVATE_KEY at the team level to "atlassian", then any pipeline running for website should get the $PRIVATE_KEY variable
If website doesn't get $PRIVATE_KEY, then this is a bug and you should raise it with our support team.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot