Exception by the build with "component load rules"
To speed up the build process, we defined the "component load rules" as the example in http://publib.boulder.ibm.com/infocenter/rtc/v1r0m0/index.jsp?topic=/com.ibm.team.build.doc/topics/r_scm_build_loadrules.html
Our load rules' definition:
but we got the exception at the building time:
Would you give us any suggestion? Thanks so much in advance. |
8 answers
I ended up using the foldername=/projectname/ directive on my load rules because the RootFolderName directive only loads the contents of each named component minus the actual projectname. I think the RootFolderName should only be used if you have a structure like this
/ (component | |-feature | | | |-feature1/ | |-feature2/ | |-plugins | | | |-plugin1/ | |-plugin2/ where RootFolderName will target either of /feature/ or /plugins/ to load the child projects. The thing is that I understand it the other way when reading the documentation in RTC (which you also linked). ciao! |
this is unusable!
you need a mechanism to choose specific folders in your component and have them copied out in the same structure, not 'flattened out' otherwise the likelihood of a clash is very high. using foldername as an alternative is not viable - far too much maintenance, and just way too complex for the simple principle of loading part of your component. If you need an example of how it can be done, reference Perforce's client spec .. See https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=85020 and, more broadly https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=44004 Also, for multi-component loads, including the component name in the path is covered by https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=96400 |
Geoffrey Clemm (30.1k●3●30●35)
| answered Oct 13 '09, 11:47 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The relevant work item is 88677 ... (or 85020). This work item is
currently scheduled for 3.0, but it doesn't appear to be started yet, so it wouldn't hurt to add a comment to one of those work items indicating your interest. Cheers, Geoff jazzajg wrote: this is unusable! |
The SCM development team is busy wrapping up 2.0.0.2 but we have done our 3.0 planning.
If you want to know about developments in this area, subscribe to 44004. It will be updated once work starts. The relevant work item is 88677 ... (or 85020). This work item is this is unusable! |
If you want to exclude certain projects from the load during a build, one option is to move those into a separate SCM component, then add this component to the 'Components to exclude' field in the Jazz SCM page of the build definition.
|
How do I load a component root as a directory during a build? I can do it from the command line and from the UI. The Component load rules in the build definition only allows for folders within a component.
I imported a ClearCase VOB into an RTC component and it has this structure: VOB_Name -> CommonFile.txt -> Dir1 -> Dir2 Unless I load the component root (i.e. VOB_Name) as a directory I do not get the CommonFile.txt loaded. I cannot figure out how to do this as part of the build automation. Thanks, Jeff |
This is not currently supported in 2.0.0.2, but is planned for 3.0. See 85020: scm load should provide an option to load artifacts with full path information comment 10.
For now, can you just avoid specifying any load rule? This will load all the files in the component, into the load directory (not a subdirectory). If a subdirectory is really needed, the only workaround I know of is to define a corresponding folder in the component. |
I suppose another workaround would be to specify all components in 'Components to exclude' in the build definition except one containing your build script, then have the script do the rest of the load itself using the teamFetch Ant task or the SCM CLI.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.