• Type: Bug
• Resolution: Unresolved
• Priority: Blocker
• Component/s: phing-plugin
• Labels:

  • bomb
  • fork
  • phing
• Environment:

  Jenkins 1.541 Linux Debian x64
  Phing v2.71

1. 

   Capture.PNG

   172 kB

   2013-12-02 11:47

2. jenkinslogs.zip

   45 kB

   2014-01-31 06:42

[JENKINS-20835] calling phing long running targets spawns new phing processes endlessly

Collapse comment: Frank K added a comment - 2014-01-28 18:01, Edited by Frank K - 2014-01-28 18:01

Frank K added a comment - 2014-01-28 18:01 - edited

I'm facing the very same issue on a freshly installed Jenkins on Ubuntu 12.04.
Running Phing trough Jenkins results in a massive list of processes, a high load and unresponsive server.
Running the exact same command manually on the commandline works just fine and only launches one process.

This is quite a serious issue, I can't believe there hasn't been any response whatsoever in the past ~2 months since this issue has been reported!

Expand comment: Frank K added a comment - 2014-01-28 18:01, Edited by Frank K - 2014-01-28 18:01

Frank K added a comment - 2014-01-28 18:01 - edited I'm facing the very same issue on a freshly installed Jenkins on Ubuntu 12.04. Running Phing trough Jenkins results in a massive list of processes, a high load and unresponsive server. Running the exact same command manually on the commandline works just fine and only launches one process. This is quite a serious issue, I can't believe there hasn't been any response whatsoever in the past ~2 months since this issue has been reported!

Collapse comment: sogabe added a comment - 2014-01-31 04:41

sogabe added a comment - 2014-01-31 04:41

Any log in system log? Manage Jenkins -> System log -> All Jenkins Logs

Expand comment: sogabe added a comment - 2014-01-31 04:41

sogabe added a comment - 2014-01-31 04:41 Any log in system log? Manage Jenkins -> System log -> All Jenkins Logs

Collapse comment: Justinas Urbanavicius added a comment - 2014-01-31 06:34, Edited by Justinas Urbanavicius - 2014-01-31 06:37

Justinas Urbanavicius added a comment - 2014-01-31 06:34 - edited

where are the logs physically located ? Jenkins does not show whole log, and since the issue is quite old i can't find anything about it in the short fragment that is displayed.

ok, found it in /var/log/jenkins
attaching log files

Expand comment: Justinas Urbanavicius added a comment - 2014-01-31 06:34, Edited by Justinas Urbanavicius - 2014-01-31 06:37

Justinas Urbanavicius added a comment - 2014-01-31 06:34 - edited where are the logs physically located ? Jenkins does not show whole log, and since the issue is quite old i can't find anything about it in the short fragment that is displayed. ok, found it in /var/log/jenkins attaching log files

Collapse comment: Frank K added a comment - 2014-01-31 06:43

Frank K added a comment - 2014-01-31 06:43

I have figured out why it is causing problems for us and resolved it. In our case it was because we configured a full path to the phing binary (which wasn't in the path).
After adding the phing binary to the /usr/bin (via update-alternatives) and disabling the phing-path its working fine for our Jenkins.

Expand comment: Frank K added a comment - 2014-01-31 06:43

Frank K added a comment - 2014-01-31 06:43 I have figured out why it is causing problems for us and resolved it. In our case it was because we configured a full path to the phing binary (which wasn't in the path). After adding the phing binary to the /usr/bin (via update-alternatives) and disabling the phing-path its working fine for our Jenkins.