[JENKINS-20878] Windows Command timing out running Gulp Script.

Running a Gulp script (like Grunt) from Jenkins

Gulp is an orchestrator/nodejs mix

During execution of the Gulp command, via windows batch command it fails the build half way through the process, however I can run the full process via command line, so it seems Jenkins is timing out the processes.

I have had "npm install" commands that took over 2hours, and not sure why this Gulp script is not allowed to finish.

The 5 basic steps of the Gulp script are (clean, version, build, test, deploy) aborts during the test phase.

Using Jenkins to run our Gulp script is an intricate part of our CI process.

---
Originally reported by joewjordan, imported from: Windows Command timing out running Gulp Script.

• status: Open
  
• priority: Major
  
• component(s): durable-task-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 2025-12-09
  

Raw content of original issue

Running a Gulp script (like Grunt) from Jenkins 

Gulp is an orchestrator/nodejs mix


During execution of the Gulp command, via windows batch command it fails the build half way through the process, however I can run the full process via command line, so it seems Jenkins is timing out the processes. 


I have had "npm install" commands that took over 2hours, and not sure why this Gulp script is not allowed to finish.


The 5 basic steps of the Gulp script are (clean, version, build, test, deploy) aborts during the test phase. 


Using Jenkins to run our Gulp script is an intricate part of our CI process. 

• environment: Linux jenkins Master with job restricted to Windows Jenkins slave