TeamCity Changes is updated on an issue, but not the Fixed in Build?!?

Hi,

I am having a problem where the Fix in Build field is not being updated after TeamCity has performed a build. When I check-in code into subversion I add a comment similar to "#TASKER-1 fixed". After this has been done I perform a build within TeamCity. This all seems to work fine because the issue details are tagged to the result of the build. If I then go into YouTrack and click the "Get changes from TeamCity now", then the build details are pulled through and the "state" is updated to "fixed", but the "fixed in build" remains on "Next Build".

Any thoughts as to why this is happening?

Kind Regards

Michael

P.S I am using the latest versions of TeamCity and YouTrack.

P.P.S On a different note...if I user can't access the "Get changes from TeamCity now" link how long do they have to wait for the changes?

9 comments
Comment actions Permalink

Hi,

I just checked this morning and I think it may have updated the "fixed in build" field. Just doing another test now to see if I've got this wrong. Will clicking the "Get changes from TeamCity now" link update the "fixed in build" field? How long is it before YouTrack will automatically get the changes from TeamCity?

Thanks

Michael

0
Comment actions Permalink

Hi

I done a test this morning and the TeamCity Changes tab is automatically updated after a check-in and build, but the "fixed in build" field does get updated. This is after waiting about 1h 40mins.

Michael

0
Comment actions Permalink

Michael,

Is 'Process red builds' option checked for your build mapping configuration? If this is not the case, YouTrack will only process successful builds.

YouTrack automatically fetches changes and build info from TeamCity on interval configured on Administration -> TeamCity Integration -> Common Settings.

Best regards,

  Alexander

0
Comment actions Permalink

Hi Alexander,

The option is not enabled, but the builds I am running all complete successfully. I can access TeamCity info from YouTrack, and vice-versa, as expected, it's just the "fixed in build" field that isn't updating. I will try with the "process red builds" enabled and see if anything different happens.

Thanks

Michael

0
Comment actions Permalink

Hi

It appears that the "fixed in build" is being updated after the 2nd build is performed. I've not tried this on a clean installation, but if I create an issue, perform the code change, check-in the code and perform a build, then after a 5 minutes (I changed the refresh option) the issue becomes "fixed" and the changes can be found in the "TeamCity" tab, but the "fixed in build" is still not set.

If I then create another issue and follow the same process, then the "fixed in build" of the previous issue is set with the latest build number, but the new issue gets set to "fixed" and the "fixed in build" remains at "next build".

Michael

EDIT: The revision number, or "version", found within the TeamCity tab is correct, but it does not match up with the revision number found against the "fixed in build" field when it actually gets assigned a number.

0
Comment actions Permalink

Michael,

The issue has to do with the following. When processing build info YT - TC integration would only apply commands (those configured per build mapping configuration) to issues that got fixed after previous build and before the current one. Time of the current build assemblement is retrieved from TeamCity.

I believe in your case time on TeamCity server is ab. 40 min "earlier" than on YouTrack server and adjusting it would help.

Best regards,

  Alexander

0
Comment actions Permalink

Hi Alexander,

Could you explain the meaning of "Time of the current build assemblement is retrieved from TeamCity"?

If I were to start with a fresh installation of TeamCity and YouTrack I would create an issue, do the code, check it in, run a build and YouTrack would show me the TeamCity changes and the "fixed in build" would have the build number. Would you agree with this? It's just at the moment all of this works as described apart from the last bit.

Am I missing something about the TC-YT integration from the above?

Thanks

Michael

0
Comment actions Permalink

Hi Michael,

You are exactly correct. "Time of the current build assemblement is retrieved from TeamCity" means that YouTrack retrieves a build start timestamp from TeamCity. This timestamp is then used to find issues that were resolved after the previous build and before the current one.

Let's say you commited a change with comment #ISS-1 fixed at 3pm that made YouTrack apply this command and make the issue Fixed at 3:01pm. You then run a build at 3:05pm, but on your TC server it is 2:50pm. YouTrack will retirieve build information and try to find issues resolved after prev. build and before 2:50pm. Thus the issue will not be found and will not have it's Fixed in Build field set untill you trigger the next build.

Best regards,

  Alexander

0
Comment actions Permalink

I will double check the times on the machines and have another go.

Many Thanks.

0

Please sign in to leave a comment.