Build: artifactLinkPublisher and filePublisher never return
Hi all,
I'm trying to setup a night build that generates, among others, a test code coverage report. I've followed the compile-and-test-coverage example in the build toolkit directory and so tried to use both the filePublisher and artifactLinkPublisher Ant tasks. When I run this script, the report is correctly generated and zipped in a 200KB file, but both the artifactLinkPublisher and filePublisher tasks never seem to finish, even after I've let them run for an hour. The tasks are correctly invoked and the parameters are all set. build.xml excerpt:
Build log excerpt:
I'm running the 1.0 RC5 build engine on Windows XP. Is this a known issue? Thanks, GB |
6 answers
I'm not sure what the problem is, but there are a few things I noticed...
It appears you are using https, so the userId and password must be correct. In your build.xml it appears you login as "admin". Well, the default adminstrator is "ADMIN". Case matters for the user id. Have you really created a user with id lowercase "admin"? Also, it is common that the ADMIN account is disabled. Make sure you are logging in with a valid user. Next, I notice that you set failOnError="false". I would change that to true for debugging purposes. You could also add a -verbose to the ant arguments in the build definition Ant page, to get more debug information. Question: do any other buildtoolkit ant tasks in your build successfully connect? For example, you could try throwing this task to change the label just to see if it works: <buildResultPublisher> Lastly, do you have access to the server logs. If so, is there anything build related in there? My theory is that the connection to the repository is failing, but for some reason its not timing out. --- Ryan Manwiller Jazz Team |
Hi Ryan and thanks for taking the time to answer.
The login/password pair is correct, I just didn't want to post the real thing on the interwebs :) I have changed failOnError to false but I still see the same behavior. I have added -verbose to the Ant arguments, but it didn't output any logs about invoking the task or the task itself working. When talking about logs, I'm talking about the build logs generated in the buildsystem/buildengine/eclipse directory - are there other logs I could look at? I have tried the artifactLinkPublisher and similar tasks that need to connect and none of them complete. Tasks that do not need to connect work fine. You're probably right that this is coming from a connection problem, maybe because of the use of HTTPS. Will the build engine accept the SSL certificate coming from the Jazz repo automatically? One thing I forgot to mention is that I'm running the build engine on my local machine (for testing purposes) and the Jazz repo is on another server. Thanks again, GB |
Are you directly invoking ant on your script? Or are you actually requesting
a build in RTC and its running from the jazz build engine? |
I'm requesting a build from RTC which is then run on my local build engine.
|
Ok. Then I am confused how you got the ant log in the first place? Normally,
this is published on the logs page of the build result. But, if the build is hanging, you'd never get that log. Anyway, if you do have the ant log somehow, then this is where the more verbose output would be. Not the build engine log. Also, your response "I have changed failOnError to false but I still see the same behavior." You should set it to true. |
I don't believe setting the -verbose flag at the ant level will cause any
vebose info from our task to be output. It would only affect output from ant itself. You would also need to set verbose="true" on the invocation of our task for it to log any additional information it may be able to provide. Also...if you run basically an empty build script does the build complete and get published to the build result? Don Weinand Jazz Team Build "Ryan Manwiller" <ryanman> wrote in message news:garjac$vr9$1@localhost.localdomain... I'm not sure what the problem is, but there are a few things I noticed... |
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.