Error when executing Jenkins build with anttask
![]()
Hello,
we are getting the following breakup error during our build with Jenkins Environment: jazz server: 4.0.1 Jenkins: 1.509.2 We're using Ant-tasks 4.0.1 (already updated from 3.0.1) Step to reproduce:
<startTeamBuild buildDefinitionId="${buildDefinitionId}" 14:52:25 /home/builder/Build-System/jazz/Build-System/buildPrepare.xml:187: com.ibm.team.repository.common.transport.TeamServiceException: CRJAZ0098E The com.ibm.team.filesystem.common.IFilesystemService{/jazz/service/com.ibm.team.filesystem.common.IFilesystemService} service failed. The server returned the HTTP error 500 with this error text: Internal Server Error. Do you have an idea what the problem could be? Kind regards Marco |
One answer
![]()
Hi Marco, the setup looks OK to me. Can you check whether all the properties are getting passed through properly to the Ant script, e.g. try adding <echo message="userId is: ${userId}"/>, and likewise for other properties used in the startTeamBuild task invocation.
Can you also check on the server to see if the ccm.log (or jazz.log, depending on your RTC context root) has a corresponding entry?
Comments Also, rather than using the Ant tasks to create the build result, run the SCM phase, etc., I suggest trying our new plugin:
See tutorial and video links at the bottom of that page.
Hi Nick,
If you're seeing the RTC build result, then it sounds like the startTeamBuild succeeded. Either that or you're requesting the build from RTC, so there's already a build result in play (its UUID needs to be passed to Jenkins, e.g. by making the job parameterized with a buildResultUUID parameter).
So it's failing in the fetch, whether you use the teamFetch task or the Jenkins plugin to run the SCM phase? Is there any nested stack trace showing the request on the server-side (i.e. the implementation in FileSystemServiceInternal. getFileTreeByVersionable4)?
Are you able to set up a similar build using JBE? If so, does it have the same problem, or any better error reporting?
I don't find any entries with FileSystemServiceInternal. getFileTreeByVersionable4. I will change the loglevel tomorrow. Maybe the corresponding log entries only appears with another log level (Do you thing that log level INFO is enough?)
Hello guys,
> Do you thing that log level INFO is enough?
If it's responding with a 500, the server thinks it's an internal error, so should already be logging it at ERROR level. The default level is WARNING.
I suggest filing a work item against Source Control and/or with IBM Support.
showing 5 of 6
show 1 more comments
|
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.