It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,788
×11,931

question asked: May 13 '15, 1:20 p.m.
question was seen: 2,464 times
last updated: May 14 '15, 11:34 a.m.

Related questions

FAQ - How this Forum works

logRetriever doesn't support the "fileName" attribute

0
David Hou (11●1) | asked May 13 '15, 1:20 p.m.
Hi,

I am using BuildToolkit 5.0.2 to run RTC Ant tasks, but I got below error when try to call logRetriever Task:

logRetriever doesn't support the "fileName" attribute

My code for retrive the log is:
        <logPublisher repositoryAddress="${repositoryAddress}"
                      userId="${userId}"
                      passwordFile="${passwordFile}"
                      buildResultUUID="${buildResultUUID}"
                      filePath="console.log"
                      label="Jenkins automation test log"
                      verbose="true" />

Can anyone please advise is it an usage error or anything I should do to retrieve the log from RTC server ?

Thanks.
David Hou
Comments
Martha (Ruby) Andrews commented May 13 '15, 2:40 p.m.
JAZZ DEVELOPER

Your question is about logRetriever and fileName but the snippet is logPublisher and filePath. Is this the wrong snippet?

Martha (Ruby) Andrews commented May 13 '15, 2:44 p.m.
JAZZ DEVELOPER

Your question is about logRetriever and fileName but the snippet is logPublisher and filePath. Is this the wrong snippet?

David Hou commented May 13 '15, 9:41 p.m. | edited May 14 '15, 11:34 a.m.

@Martha, Sorry for paste the wrong snippet. Should be like below:

   <logRetriever repositoryAddress="${repositoryAddress}"
                      userId="${userId}"
                      passwordFile="${passwordFile}"
                      buildResultUUID="${childBuildResultUUID}"
                      fileName="console.log"
                      destFileName="console.log"
                      verbose="true" />

David

Be the first one to answer this question!

Register or to post 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.