Multiple JBE's and build definitions
Hi
I've noticed that the Build Definition contains things like "Load Directory" and "Working Directory". Both of these attributes are coded centrally at the Jazz Server but they refer to the filesystem on the JBE machine. If you want your Build Definition to be independent of the system running the JBE, it seems that you should avoid coding an absolute path in both of these attributes. I understand that relative paths are resolved using the JBE's CWD. If you do code absolute paths then you can't move the JBE to a system that doesn't have the same filesystem structure .. correct ?? So, using relative paths for Build Definitions would seem to be a good best-practice ?? Cheers |
2 answers
David, you are correct. I would use relative paths for any path in the build
definition. I'd also use a forward slash for path separators, which will enable the definition to work on windows or linux build machines. Relative path support is new in beta2, so you may still see a few people using absolute paths. We support both, but relative paths is the recommended approach now. Ryan Manwiller Jazz Team Build Lead |
|
Great .. thanks
Ryan Manwiller wrote: David, you are correct. I would use relative paths for any path in the |
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.