Ancestor changed?

[7.1.23907]

After upgrade from 7.0 to 7.1 we start having weird triggering on builds belonging to a release branch when we commit to /trunk.  This is the change details specified from TC:

Ancestor changed: /trunk] (directory)
Ancestor changed: /trunk] (directory)
[Ancestor changed: /trunk] (directory)
     changed: /trunk] (directory)

"[Ancestor changed: /trunk] (directory)"

We have 3 vcs roots set up: /branches/rb-1.0 (branched from /trunk), /trunk and /trunk/projB each used in multiple TC configurations.
All TC configs are set to check out on build agent. rb-1.0 and /trunk are using checkout rule -:projB

Any ideas what's going on here?
Thanks.
8 comments
Comment actions Permalink

FYI: We solved it by only using 1 vcs root (subversion 1.7), and use checkout rules instead to define what to checkout (however I do not understand how I am supposed to solve it without getting warning
"Exclude checkout rules are specified while "checkout on agent" mode is used. Applying these checkout rules requires additional overhead and is inefficient. "
since I need to use svn commands during build, but can't use multiple vcs roots due to "ancestor changed" error.

0
Comment actions Permalink

Never mind that, issue is still there even with 1 common vcs root :(

0
Comment actions Permalink

I am having the same problem with 7.1.

edited DotNet/[Ancestor changed: /Development/xxx/yyy/trunk/Flash/Games] (directory)
edited DotNet/[Ancestor changed: /Development/xxx/yyy/trunk/Flash] (directory)
edited DotNet/[Ancestor changed: /Development/xxx/yyy/trunk] (directory)
0
Comment actions Permalink

Apparently it should have been fixed in 7.1.2 (  http://youtrack.jetbrains.com/issue/TW-24356 ), we have the upgrade TC in our todo stack so cannot confirm it...

0
Comment actions Permalink

I am running

TeamCity Enterprise 7.1.2 (build 24170)

It is not a huge issue for me at the moment, just wanted to make sure it was not a configuration issue on my side.

0
Comment actions Permalink

Hello Jarret,

  Sorry for the delay with replay, I'd appreciate if you provide more details about the problem:

  - How VCS settings look like, what is the VCS path, what is SVN repository root
  - What are checkout rules for the configuration?
  - What kind of changes are incorrectly detected? Any change in /Development/.../trunk? Or only some specific kind changes? Which paths are altered in the incorrectly detected changes?

  Thanks,
  KIR
0
Comment actions Permalink

I'm running 7.1.5.  It appears to be detecting a sibling change as an ancestor change.  This may be due to svn externals though.  I am pulling http://psvmdv01/svn/software/branches/449maint/ePartsFinderSln as the root, but it detects:

[Ancestor changed: /branches/449maint/PARTSFinder Hydra] (directory)


Projects under the Hydra directory are referenced from ePartsFinderSln via externals.

If this is due to the externals, can a merge tracking only change get filtered out?  This is annoying, because our testers think they have to rebuild the test env even though the only change is to the svn merge tracking property.

See attached screen shots for details.



Attachment(s):
3.PNG
2.PNG
1.PNG
0
Comment actions Permalink

Hello Mark,

   We have a separate request for filtering out merge changes, please vote/watch: http://youtrack.jetbrains.com/issue/TW-11452

   Sorry for the problem.
   KIR

0

Please sign in to leave a comment.