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

[Sergey Morkovkin]

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?

[Michael Knight · Accepted solution]

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.

[Sergey Morkovkin]

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?

[Sergey Morkovkin]

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

[Sergey Morkovkin]

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

[Michael Knight]

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

• http://www.downforeveryoneorjustme.com/support.atlassian.com