Remote-run branch changes not visible

I've got the following setup:

VCS:
+:refs/heads/(master)
+:refs/heads/merge/*
+:refs/heads/(Deploy-*)

Branch Remote Run Trigger:
refs/heads/remote-run/*


So I made sure that my remote run branches are not in the branch specification, in order to make sure the remote run gets triggered. Now when I push something to remote-run/someuser, the build gets triggered and runs, but no changes are taken into account. So I can commit and push to remote-run/someuser forever, no changes will end up in the build.

Now, when I push to /refs/heads/merge/someuser, those changes become visible for my remote-run and my next personal build will include those changes.

Is there something I'm missing here?

5 comments
Comment actions Permalink

Hi,

Your configuration looks correctly. Could you please enable debug-vcs logging preset and provide teamcity-vcs.log and teamcity-remote-run.log files?

0
Comment actions Permalink

Is it possible to send the logs by mail?

0
Comment actions Permalink

Yes, please send it to teamcity-feedback@jetbrains.com with a link to this thread.

0
Comment actions Permalink

I've sent the logs. Please note that before those logs, I've started out with remote-run in the branches specification, but later removed that from the VCS, so I could trigger a personal build.

0
Comment actions Permalink

Dmitry created an issue for this: http://youtrack.jetbrains.com/issue/TW-37288

Many thanks for the outstanding support!

For reference purposes, I'll copy-paste his mail here:
-----------------

it turns Branch remote-run trigger doesn't work correctly with the branch specification you have. I've created an issue http://youtrack.jetbrains.com/issue/TW-37288, please watch it.

As a workaround you can change you branch specification to

+:refs/heads/(master)

+:refs/heads/(merge/*)

+:refs/heads/(Deploy-*)


Or even better you can switch to a VCS trigger instead of the Branch remote-run trigger, because it doesn't add much value: unlike changes you remote-run from an IDE, your personal branches appear in a repository visible to everyone.

0

Please sign in to leave a comment.