Repository mis-placing changesets?

So we’re experiencing a strange issue. We have a branch in TFS, when changes are checked in, Continua is seeing the changes but is applying them to “(no branch)”. Only one branch is showing this behavior, and Continua detects it as a branch when we apply repository mappings. Changes in other branches are being picked up properly. As far as I can tell, the branch in TFS is just fine.

Hi Andy,

Yes, this is strange. We are not seeing any similar issues, so we would need to look at a debug log to understand what is happening here and reproduce the issue.

Could you enable debugging, restart the Continua CI Server service, commit a new change to the Services/Patient Processor Service branch, wait for the change to be picked up in the Changes tab and then send the log file to me by direct message?

Can you also post (or send us) a screenshot of the folder structure in TFS so we can see how the branches are set up?

After some debugging, we discovered there was difference in case between the file path and branch path. We have updated the branch matching to be case-insensitive as from version v1.9.0.188