Bamboo OnDemand plan won't start on commit to OnDemand Subversion

We are trying to establish continuous integration, but for some reason nothing is triggered when code is commited to SVN. We use Bamboo OnDemand and SVN OnDemand. Plan is configured to be triggered on code commit. Should we somehow configure SVN hooks as well to make this work?

1 answer

1 accepted

Bamboo should be configured to poll the repository for new commits. I believe this is the default but it's possible it was changed by somone, so it would be worthwhile checking your plan configuration.

If it looks like it's configured appropriately, please raise a support request and we'll look into it further for you.

Occasionally, I've discovered it's actually working. However, it doesn't start on every commit. Is there a setting that control this behavior? We only have 1 Elastic Instance. May this be the cause?

It actually triggered automatically only once. More than 15 commits were ignored.

For some reason doesn't respond. Is this at my end?

I'm not aware of any recent outage with our Support site. You could try this link to check:

Suggest an answer

Log in or Join to answer
Community showcase
Renan Battaglin
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,071 views 0 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot