I have 3 sibling projects that have a common parent that I'm managing with Maven. The projects share same parent which is one level up. The parent POM has no knowledge of any of the children it simply contains boilerplate, repo definitions and common plugins. Everything works fine until I try to put these on TeamCity. Here's how I do it now
- Create one configuration per branch
- Trigger independently of each other based on check-ins
And now comes the problem: since I have a parent POM one level above the project it's not getting pulled when the child code is checked out and the build quickly fails. I suppose I can create another build configuration just to pull the parent (which is of type POM) but is there a better way that I'm missing?
Also when I create a parent project - how do I check out pom.xml only since I do not want any nested directories? When I put the following checkout rules into the configuration:
I get the following exception:
jetbrains.buildServer.vcs.VcsException: Getting sources for checkout rule './pom.xml=>./pom.xml' failed with erorr: org.tmatesoft.svn.core.SVNException: svn: Cannot replace a directory from within
svn: REPORT of '/svn/!svn/vcc/default': 500 Internal Server Error