[
https://issues.jenkins-ci.org/browse/JENKINS-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162724#comment-162724
]
Lars Kruse commented on JENKINS-13611:
--------------------------------------
Hi Julian
The problem with the new GUI in Jenkins is apparently a problem for quite a lot
of the plugins in the community right now - and we will also fix this issue in
due time. Right now we are very concerned with not-crashing-the-slaves when
something unforeseen happens (missing licenses, missing qaw ...and we have even
seen this phenomena ourselves on linux when running jenkins as a service and
the QAxxx environment variables aren't loaded from the .bash_profile).
IN all these occasion the plugin should fail gracefully with an informative
error message of what is wrong.
What actually does seem to work is (as you are also hinting in your own
description) when both Jenkins master and slave is running as user processes
(e.g master is started using java -jar jenkins.war and the slaves are started
using the .jnlp interface) everything works fine - also the nice informative
error messages.
However, we do realize, that we can not allow ourselves the luxury to
anticipate that all Jenkins environments out there are run like this.
We have created quite a few Plugins, but we must admit, that the PRQA one is
the only one, so far, where we have seen such significant differences in
behavior, dependent on how the jenkins instance is started.
The licence issues are being scrutinized - they do give us grey hair.
But I can assure you, that we're in red-alert and we are working on these
issues as we speak.
We expect to have a new release ready within very short.
> Misleading error leads to slave disconnecting from master
> ---------------------------------------------------------
>
> Key: JENKINS-13611
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13611
> Project: Jenkins
> Issue Type: Bug
> Components: prqa
> Affects Versions: current
> Environment: Jenkins 1.441, Windows 7, QAC-7.2F
> Reporter: Julian Requejo
> Assignee: Mads Nielsen
>
> I'm having some issues running the PQRA Plugin. The
> [documentation|https://wiki.jenkins-ci.org/display/JENKINS/PRQA+Plugin] is a
> bit strange. To start with, the screenshot shows a report type "quality",
> even though it says that currently only compliance is available. Then it also
> says that a tool qaw must be installed, which I don't have anywhere in my
> installation files. In any case, here is the problem: the plugin seems to not
> find this qaw tool, and it produces an error that disconnects my slave agent
> from the master.
> Started by user XXXXX XXXXX, xxxxxx.xx...@xxx.xx
> Building remotely on Legoland
> Updating https://xxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxx
> At revision 1292
> Updating https://xxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxx
> At revision 1292
> Updating https://xxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxx
> At revision 1292
> no change for Updating https://xxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxx since the
> previous build
> no change for Updating https://xxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxx since the
> previous build
> no change for Updating https://xxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxx since the
> previous build
> This job will try to create a report with the following selected parameters:
> QAR selected project file: Sources/xxxx/QAC.prj
> QAR selected product: QAC
> QAR selected report type: Compliance
> Beginning report generation with the following command:
> qaw QAC "Sources/xxxx/QAC.prj" -maseq "qar %Q %P+ %L+ -po
> qar::report_type=Compliance\ Report -po qar::project_name=%J -po
> qar::output_path=c:\_dev\jenkins-int\workspace\xxxxx\ QAC -po
> qar::viewing_program=dummy -po qar::report_format=xhtml"
> ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted
> due to exception
> hudson.remoting.RequestAbortedException:
> hudson.remoting.RequestAbortedException: java.net.SocketException: Connection
> reset
> at hudson.remoting.Request.call(Request.java:149)
> at hudson.remoting.Channel.call(Channel.java:681)
> at hudson.FilePath.act(FilePath.java:772)
> at hudson.FilePath.act(FilePath.java:765)
> at
> net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:203)
> at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
> at
> hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692)
> at
> hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667)
> at
> hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645)
> at hudson.model.Build$RunnerImpl.post2(Build.java:162)
> at
> hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614)
> at hudson.model.Run.run(Run.java:1429)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:238)
> Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException:
> Connection reset
> at hudson.remoting.Request.abort(Request.java:273)
> at hudson.remoting.Channel.terminate(Channel.java:732)
> at hudson.remoting.Channel$ReaderThread.run(Channel.java:1139)
> Caused by: java.net.SocketException: Connection reset
> at java.net.SocketInputStream.read(SocketInputStream.java:168)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
> at
> java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249)
> at
> java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2542)
> at
> java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2552)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
> at hudson.remoting.Channel$ReaderThread.run(Channel.java:1109)
> Notifying upstream projects of job completion
> Finished: FAILURE
> After this, my slave gets disconnected from the master. So my questions:
> - Where do I find this qaw tool? It is not installed with QAC-7.2F
> - Why does the absence of such tool end up in such a brutal way?
> Thanks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
