Reputation: 18445
I thought I had set this up right but none of the VCS commands seem to be propagating through.
I have a git repository which TeamCity hooks into, when a check-in happens TeamCity runs the build script and creates an artifact. YouTrack has been integrated with TeamCity and has had the projects mapped, so the project build (the one which auto builds and creates an artifact) and it is run on behalf of the admin user (root).
I have told it to process red builds, the mapping maintainer is root, everything else is default. Now both the server and the mapping are ticked as active, and I can see the last Synchronised time, and the build it processed, all of that looks fine, however the commands in the commit were not actioned.
Lets say it processed build 250, which had a VCS comment of:
#PMI-52 Fixed
Have finally fixed this annoying issue
I would expect task PMI-52 to be moved to the Fixed state, and with Youtrack 4 have the comment below added to the task comments for PMI-52. However none of this happens. So am I missing something or should this put the changes into the tasks/issues?
Upvotes: 1
Views: 2492
Reputation: 2116
Your expectations are completely correct. So the issue must be in the configuration. For the sample you've provided, do you observe the change on 'TeamCity Changes' issue tab of PMI-52? If you do and command there is in red, please consider the error message (click on '?' on the right of the command). The most probable reason is that the integration did not manage to match the TeamCity user to YouTrack user to run the command on behalf of. For the users to match they have to have identical emails.
Upvotes: 1