I have a TeamCity project set up using Subversion as a VCS. I have one VCS root and that root has several externals defined. Everything works fine, but my pending changes and changes for a build seem to be showing up more than once in the UI. I use one SVN repository for all my modules. For example:
- module 1
- module 2
- module 3
- maven parent module
- external --> module 1
- external --> module 2
- external --> module 3
I know I should really have each module set up as a separate project and that's eventually what I will do. However, I'd prefer to let TeamCity checkout and build my parent project for the short term. It seems like the changes listed in the UI get listed once for every external location that is affected by a commit. For example, if I refactor some code and it affects modules referenced by 3 different externals I'll see that change 3 times in the TeamCity UI.
I know this is an issue that will go away as my development cycle matures and I improve my build configurations, but I'm wondering if there's a way for me to get TeamCity to recognize that it's listing changeset #NNN more than once?
Edit: I've seen this error in my logs, but it showed up in the UI today. I think it's related:
Failed for the root 'JP Tech Main SVN Repo' #8: Error executing query with params:[707, ryan, Starting to try to set up an OSGi bundle for the Glassfish DAO provider., 1248978939674, 8, 2, 131_2009/07/30 12:35:40 -0600, 131, 6]; uncategorized SQLException for SQL [INSERT INTO vcs_history (MODIFICATION_ID, USER_NAME, DESCRIPTION, CHANGE_DATE, VCS_ROOT_ID, VCS_ROOT_VERSION, VERSION, DISPLAY_VERSION, CHANGES_COUNT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?)]; SQL state ; error code ; ERROR: duplicate key value violates unique constraint "vcs_history_pkey"; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "vcs_history_pkey
The error was only in the UI for less than a minute, then it went away.