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
I have big amount of variable for each deployment (more then 200 for each), how to pass all deployment variable through steps correctly?
option with export each variable into artifact is not ok when you have good amount of variables.
(also it is not very good to remember that besides of add to bitbucket deployment page new variable, you need to add export of it in to artifact in the pipline file).
I try to use printenv output on deployment step into artifact (for future source of this artifact file in needed step), but some variable have space, some could be array.
So it is not very confident and secure way (with parsing artifact file to correct all this moments before source).
Exist some correct way to do it?
You could use the stage option in your yml file to group steps, and then specify a deployment environment for the stage.
For example, if you have a pipeline like the following, the deployment variables of staging will be available to both the second and the third step of the pipeline.
name: Build and test
- sh ./build-app.sh
name: Deploy to staging
- sh ./deploy-app.sh
name: Run end-to-end tests
- sh ./run-e2e-tests.sh
You can read more about stages here:
Does this work for you? Please feel free to reach out if you have any questions.
Parallel steps are indeed not supported for stages yet. We have this feature request in our issue tracker, you can add your vote and feedback to it to express your interest: