I've got an interesting scenario here, and I'm willing to suggest a PEBCAK. I do apologise for the long winded explanations, but I think a number of logic issues are coming into play.
Repository
HG\Bibucket
Poll Freq: 5 min
Timeout: 60m
UX Process
I setup a continua project and configuration for a project that I needed to run unit tests against.
I setup all the usual steps, and ran the first manual test 1.0.0.0. It runs against the changeset I've highlighted in the orange box.
Reviewed the 1.0.0.0 failures, so I started look at why. I hadn't push local files from my workstation to HG, so I pushed them, then continue coding.
Again, forget to push from workstation to Bitbucket, I manually run build 1.0.0.1.
Reviewed the 1.0.0.1 failures, determined multiple build issues 1) Nuget packages folder was not committed to HG, so added the folder and pushed to Bitbucket (610) files. 2) A CodeSmith Generator MSBuild component is required for the VS Action to pass.
Purposely didn't manually trigger Continua build, because change sets were flowing to the project (see screen shot)
Still reviewing the error log, discovered a workstation agent was not using in v1870 of continua, so I installed it and confirmed the agent found CodeSmith MSBuild components installed.
I updated the first stage to include agent requirements $Agent.CodeSmith.Installed$ Exists, forcing the build to use the workstation agent. Confirmed the project configuration would run on the Workstation with CodeSmith installed.
Result
As you can see, nothing in the BUILD Queue!, despite lots of code changes since the last manual build. (everything is enabled).
So I change the Repository TimeOut to 5 minutes and check the server repositories and watch it "check for changes", still nothing. In past builds of continua, call changes would trigger a build being added to the queue, but this time it hasn't queue any of the new changesets (3-7 changeset Id's, by my count, depending on my assumptions for repo polling frequency). See Purple boxes and arrows.
While reviewing the various views I notice that the Column TITLE "Changes" on Activity View (top) is used in a different way to the Changes view(bottom). (Green box -> Red Box??? and highlighted in yellow). I found it hard to determine which changeset was used in the build 1.0.0.0/1, view without drilling down/up through these views to match the "Commit Message". I just wonder if referencing the changset ID or matching the number of files changed might be easier. Or alternatively, modify the Changes View to include any matching $Build.Version$ references, helping the poor developer to find the CI issue.
Attachment unavailable