We have observed many Changesets are not firing Builds by Repository Triggers, but we can’t make the problem reproducible.
A commit is sent to a Pull Request, and no build is triggered. Then the same user, hours later, makes a new “fake” commit by changing only one blank line in the same file, so the build is triggered.
This leads me to conclude that there is no misconfiguration, but there is something else preventing the trigger from triggering the build. We have tried to enable logging on
Continua.Server.Service.exe.config but we have not found any information that would lead to the problem mentioned.
How could I find out why many Changesets aren’t firing Builds by Triggers?
Follows print of a recent example. No associated builds for this changeset:
In the Changes tab, the changeset only appears on page 9 although it was one of the most recent:
Trigger that should have fired, Files configuration:
Making a fake commit, same files, the Build was fired by Repository Trigger: