You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
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.
I'm happy to announce that Bamboo 7.2 has been released and it’s overflowing with awesome new features. This will be the last major Server release before the launch of Bamboo DC. Bamboo logs We...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events