|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I added a dummy pom.xml to this jar. In Jenkins create a new "Maven project" (I attached a screenshot of creating this type of project). I don't know if you need a plugin to create a Maven project, or if it comes out-of-the-box-Jenkins.
In the configuration of the job, point it to the pom.xml and select "test" as the target (I've attached a screenshot of this too).
The build will fail, since there are no sources, but it doesn't have to pass to reproduce this problem.
When you build it, the text on the console will have something like:
==========================
blah blah blah
blah <===[JENKINS REMOTING CAPACITY]===>
blah blah blah
Failure
==========================
The message body will only contain stuff above the "Jenkins Remoting Capacity" text.
On a side note, I'm also going to try to get rid of one other variable: Cloudbees. I'm going to install Jenkins locally on my machine and try to reproduce this. I'm more and more convinced that it has to do with how Jenkins Cloudbees handles the console text. The reason I say this is because if I just try to echo out the contents of the console text, it works fine.
I will let you know my results.