If starting JBE as root, RTC build ID becomes "null&quo
Our users start the JBE as sudo on several Unix servers,, but using valid RTC user credentials to the required parameters to the jbe.sh command, ie,
home/isbld/rtc_tools/v301/buildsystem/buildengine/eclipse/jbe.sh -repository https://ips-xxx.swg.usma.ibm.com/jazz -userID yyyy@us.ibm.com -passwordFile /home/isbld/rtc_tools/v301/pwd_yyyy@us.ibm.com -engineId ISBuild.ia64bld3 This allows the root-owned process to access the Workspace for source, while giving it the permissions necessary to perform the work as required in the executed ANT script. It had been working for a while but now stop working. But now get the following error upon trying to open failed (but completed) task: MESSAGE Unable to create editor ID com.ibm.team.build.ui.editors.buildResultExplorer: null argument:A part's title tool tip must be non-null. Then run with the JBE on the build machine in -verbose mode, and when it wakes up to look for build requests, the following is displayed: 2012-03-13 14:54:54 Sleeping for 30 seconds... 2012-03-13 14:55:24 Searching for build request... 2012-03-13 14:55:28 Build "null" complete. Notice that the build is "null", which matches the "null argument" seen above. if start the JBE as non-sudo, the job will run, but we got intot some local permission issue on the build server. So the question is why JBE failed to idntify the build ID if JBE was started as root on the build server? |
3 answers
On Wed, 14 Mar 2012 19:41:58 +0000, ghu wrote:
Our users start the JBE as sudo on several Unix servers,, but using JBE shouldn't case what user it is running under as long as it can bind to the port (its not privileged) and has access to the file system and other calls needed to perform the build. Have you tried running your ant script outside of the build engine as sudo? -- Boris Kuschel Jazz Jumpstart Team - IBM Software, Rational My Blog: http://blog.boriskuschel.com/ -------------------------------------------------------------------------- This post represents my own opinion, thoughts, and conclusions based on my knowledge of Jazz and the Jazz solutions. For details on receiving official IBM Rational support please go to: https://jazz.net/community/support/ |
Yes. The script was originally developed to be run as sudo and has worked since developed (October 2011) and put into production (February 2012).
|
|
Update/Resolved: As the above scenario was implemented using a front end script to simplify starting/stopping of the JBE, as well as enabling/disabling the JBE during a system reboot, a command line was being built to then execute. It turns out that, due to the addition of using full paths for all parameters specified on the command line, the maximum command line length was exceeded, thereby truncating the last X number of characters that exceed the OS limitation.
This was the fatal flaw in that the option being truncated was the -data <path> option, which must resolve to a writeable directory where the RTC metadata information can be written. As this path was being truncated, the probability of it resolving to a writeable directory was very low. After modifying the front end script to use relative paths, the problem was resolved. |
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.