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
Next: Root
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
Hi,
Bamboo 7.1.1 build 70117 with Bitbucket Server
Using a yaml spec, residing in the source code repo to be build.
When *not* defining any triggers, the default "Bitbucket Server Repository triggered" is used (it's configured for as as default).
Now I wanted to also define a nightly build trigger. YAML Specs only supports CRON at this point, so I've added
triggers:
- cron: 0 0 2 1/1 * ? *
to the specs. This works fine but now the repository trigger is overwritten, i.e. no longer active.
Specs now would allow me to add a remote trigger for the git repo, but it seems only IP is allowed. This is pretty dirty as I don't want to make commits just because the service may have moved to a different IP.
Is there a way around it? For example, when I look at a spec generated by bamboo for a spec plan without custom triggers, I don't see any trigger definitions at all in the resulting yaml specs.
So, how can I get yaml specs to not override the default trigger or to not rely on IP information for the remote?
I feel inclined to create a ticket for that.