Continuous Build error due to folder move
We have a continuous build on RTC. Only the changes are accepted and build and "Delete directory before
loading" is unchecked.
Out stream consists of many components and components are loaded as folders.
This setup works fine until the point when the new changeset contains changes which involves folders/files being moved to different levels ( and sometimes even components in same stream)
At this point, the build throws the following error
[Jazz build engine] Fetching files to fetch destination "D:\b\" ...
com.ibm.team.build.internal.scm.SourceControlUtility$3: Status ERROR: com.ibm.team.filesystem.client code=2 Folders to load overlap other contents null children=[Status ERROR: com.ibm.team.filesystem.client code=0 /Build.Image overlaps 2 other folder(s) null]
at com.ibm.team.build.internal.scm.SourceControlUtility.updateFileCopyArea(SourceControlUtility.java:685)
at com.ibm.team.build.internal.engine.JazzScmPreBuildParticipant.preBuild(JazzScmPreBuildParticipant.java:238)
at com.ibm.team.build.internal.engine.BuildLoop.invokePreBuildParticipants(BuildLoop.java:885)
at com.ibm.team.build.internal.engine.BuildLoop$2.run(BuildLoop.java:689)
at java.lang.Thread.run(Unknown Source)
Contains : 0 /Build.Image overlaps 2 other folder(s)
In this case the folder "Build.Image" has been moved elsewhere.
Only way we know is to delete the fetch location and restart the build. Since this is a continuous build, how can this process does not make sense.
How can we make RTC handle this on changes to filesystem level too?
2 answers
Hi Karthik,
We had another user having this issue: https://jazz.net/forum/questions/119411/build-errors-with-loading-components. Just try recreating new workspace to check whether it helped.
We had another user having this issue: https://jazz.net/forum/questions/119411/build-errors-with-loading-components. Just try recreating new workspace to check whether it helped.
Hi Karthik,
It is likely that something else has happened in your workspace, components and folders for this folder collision to happen. I ran some test builds here using the options you described and didn't have any problems loading source. As Heather suggested, run a build after checking "Delete directory before loading" to clean up the load directory. Then you can uncheck it again and your continuous build should be unblocked.
Scott
It is likely that something else has happened in your workspace, components and folders for this folder collision to happen. I ran some test builds here using the options you described and didn't have any problems loading source. As Heather suggested, run a build after checking "Delete directory before loading" to clean up the load directory. Then you can uncheck it again and your continuous build should be unblocked.
Scott
Comments
Like I mentioned checking this "Delete directory before loading" & running build works bu the questions is how can this be handled automatically.
Please see my above comment for example (my usecase)
Hi Karthik,
Heather guessed what specifically was causing your problem and I am able to reproduce it now in v4.0.1. It is the move of a component root folder into another folder. What version are you using?
I've opened this defect, SourceControlUtility.updateFileCopyArea fails if component root was moved to another folder (298101).
Please update the work item with any further comments,
Scott
1 vote
Thanks Scott.
We use RTC 4.0.2
same in 4.0.5 too. As suggested I will raise a PMR
Comments
Heather Fraser-Dube
JAZZ DEVELOPER Jan 16 '14, 10:11 a.m.Are you using load rules for your build? Can you describe where "Build.Image" used to be in relation to the other shares (top level items) that were loaded. Then where it is after the move. Did any shares (top level items loaded) move underneath "Build.Image"?
At this moment, you would need to check off "Delete directory before loading". But I am trying to understand if we can determine what the problem is and handle it better in the build engine.
If you have this error using load rules and after deleting the directory before loading, that would indicate a problem with what you have specified in the load rule.
1 vote
Karthik Krishnan
Jan 16 '14, 11:44 a.m.we are not using load rules for loading build the workspace