Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,360,313
Community Members
 
Community Events
168
Community Groups

YAML Specs remote trigger definitions without IP

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.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 9.0 is now available

Hey there, Data Center community! I'm Martyna Wojtas and I am the Product Manager for Bamboo Data Center. I’m excited to share that Bamboo 9.0 is now available. We purpose-built this platform to help...

307 views 0 7
Read article

Atlassian Community Events