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
It would be really helpful for me if I had access to the custom pipeline name, either plain string or slugified, as a default BBP variable. I see that I have access to the UUID, but that's not super accessible. I've seen that the slugified version can be triggered via API, so I know the attribute is in there...any plans to expose it as a default variable?
The problem I'm trying to solve is how to use a DRY Bash notification script in the after-script section, one that takes the name of the pipeline as an argument. This script would replace, per pipeline, 7 lines of logic/output code with a single line of code.