How do I get the console log "Hudson.log" posted to the build result when starting a RTC Build from Jenkins.
When using the RTC Team Concert plugin with Jenkins, I can request a build from RTC and the console log "Hudson.log" will get posted to the Build Result. If I request the build from Jenkins the console log does not get posted to the Build Result. Is there some way to make this happen.
I did notice that someone posted a similar question:
https://jazz.net/forum/questions/169624/is-there-a-way-to-make-the-hudson-log-available-in-rtc-when-poll-scm-is-enabled-in-jenkins?redirect=%2Fforum%2Fquestions%2F169624%2Fis-there-a-way-to-make-the-hudson-log-available-in-rtc-when-poll-scm-is-enabled-in-jenkins
And the answer to the above link was a bit dismissive to say the least, i.e. "Working as Designed". Even if that is the case, I would say that it is not designed the way I would like it.
|
2 answers
I would suggest opening an enhancement request at https://www.ibm.com/developerworks/rfe/
|
I am searching for a better answer, but if the last thing you do in the ANT script is return the Jenkins log, you get most of what you want, this is not perfect but better than nothing (you must also ensure that this runs on the master not the slave). Downloading the console output build result html page would be a better option still, but I am stopped by a security issue, might be https issue.
<logPublisher buildResultUUID="${buildResultUUID}"
repositoryAddress="${repositoryAddress}"
userId="${userId}"
password="${password}"
filePath="C:/Jenkins/jobs/Folder/jobs/BuildJobName/lastSuccessful/log"
label="console output from Jenkins URL" />
|
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.
Comments
I also wish that it worked as you suggest.. I do not have anything to do with product development, I am just another user. looking at the code, there are a bunch of technical things that make it harder to do. and I can understand why it is the way it is.
my current employer doesn't use RTC for source code mgmt or build, so I have no ability to impact the solution.