I am having similar issue. I am using the RC with latest plugins 2.1
When I have a bat call that takes a little time the job does not relize it
has completed. I can see from task manager on the jenkins machine that the
bat task is complete. Two CMD instance are spun up when the task start one
for jenkins-wrap.bat and one for jenkins-main.bat. Then the acctual task
happing in the main bat such as NODE for npm or 7zip or javac etc. Once
all of these are no longer running in taskmanager completed on thier own.
I check jenkins and job still things things are working. Check the
durable task folder where the jenkins-wrap and main bat files have been
writen and no jenkins-result.txt file has been written. With the 2.0beta
this hangs consistenly 95% of the time. With the RC I am seeing less
hanging. The job log shows the results of the bat file but never moved on
to the next task.
A ThreadDump shows:
Thread #2
at DSL.bat(Native Method)
at WorkflowScript.run(WorkflowScript:12)
at DSL.node(Native Method)
at WorkflowScript.run(WorkflowScript:1)
I have to kill the Job task or mannualy create a jenkins-result.txt file
for the job to end. This is making for an unusable setup.
Daniel D.
On Thursday, April 7, 2016 at 7:15:28 AM UTC-4, Daniel Beck wrote:
>
>
> On 06.04.2016, at 13:01, Javed Mandary <[email protected] <javascript:>>
> wrote:
>
> > When you run the build the project stays indefinitely in progress and
> nothing happens.
> >
> > I have checked the WAR deployed on tomcat 8 as well as using the
> installer for windows both give the same results.
> >
>
> If your version of the Pipeline plugin is 2.0, update it to 2.1.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/de5ff9c5-76a4-4d13-96b5-7d10a674eb44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.