The location of Build Toolkit's component load rules
I can use build toolkit to get specific directory by component load rules.
Reference this document:
My question is, could I put the load rule file in other place instead of RTC?
Because it's strange, when I want to change load rules, I need to check-in/out file in RTC and it's not convenient.
2 answers
Hi Dennys,
Even the updated docs for v4.0.4 indicate "You must create the load rules file in the build workspace."
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m4/topic/com.ibm.team.build.doc/topics/r_scm_build_loadrules.html
I'm sure the intent is so that any JBE can find the file. However, it is also a best practice to generate the load rules file as described here,
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m4/topic/com.ibm.team.scm.doc/topics/t_scm_create_load_rule.html
And the reason is that you can be more confident the load rules file is valid it you have a clean building sandbox.
Scott
Even the updated docs for v4.0.4 indicate "You must create the load rules file in the build workspace."
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m4/topic/com.ibm.team.build.doc/topics/r_scm_build_loadrules.html
I'm sure the intent is so that any JBE can find the file. However, it is also a best practice to generate the load rules file as described here,
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m4/topic/com.ibm.team.scm.doc/topics/t_scm_create_load_rule.html
And the reason is that you can be more confident the load rules file is valid it you have a clean building sandbox.
Scott
The JBE does expect it to be in the build workspace. If you take over the loading of the workspace you could specify the loadrule file as a file on disk. This would mean using the teamAccept ant task to accept the changes into your build workspace, but rather than using the teamFetch ant task to load the workspace, use the CLI instead (example: scm load -r yourRepository -f -L yourBuilds.loadrule "Your Build Workspace"). See https://jazz.net/library/article/1015 for details on load rules themselves.
If you go this route, you will have to propagate any changes you make to a load rule to all the copies of the load rule. Assuming that you have more than 1 machine running builds and the load rule file will be on each machine.
If you go this route, you will have to propagate any changes you make to a load rule to all the copies of the load rule. Assuming that you have more than 1 machine running builds and the load rule file will be on each machine.
Comments
Geoffrey Clemm
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Oct 23 '13, 10:23 a.m.dennys hsieh
Oct 23 '13, 10:34 a.m.Geoffrey Clemm
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Oct 23 '13, 9:06 p.m.