We need to update this, and potentially the Jenkins plugin at the same time.

Any SCM is part of a stack in a production environment, usually tied to automation if that is set up and we need to bring plastic scm out of the dark ages and towards functionality that other scm providers have.

Alternative triggers would be a good start. For example attribute changes on a branch could trigger specific builds, a label change could trigger a build.

It allows you to parameterize the attribute/label information inside the automation suite and then you can use that as a parameter in your build.

As well as polling for changes, we can also be polling for attribute/labels on specific branches and that would open up a lot of possibilities and a deeper integration.