-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Windows Server 2012 R2
Jenkins 2.73.3
Durable Task Plugin 1.17
Pipeline: Nodes and Processes 2.17
Powershell 4
java.specification.vendor Oracle Corporation
java.runtime.version 1.8.0_144-b01
Jenkins was installed using the windows installer, and is deploying to the same server (not remoting into other nodes).Windows Server 2012 R2 Jenkins 2.73.3 Durable Task Plugin 1.17 Pipeline: Nodes and Processes 2.17 Powershell 4 java.specification.vendor Oracle Corporation java.runtime.version 1.8.0_144-b01 Jenkins was installed using the windows installer, and is deploying to the same server (not remoting into other nodes).
Jenkinsfile:
pipeline { agent any options { timeout(time: 1, unit: 'HOURS') } stages { stage('Starting') { steps { echo "Running ${env.JOB_NAME} - ${env.BUILD_ID}" } } stage('Checkout') { steps { echo 'Checkout..' checkout scm } } stage('Build') { steps { powershell 'Write-Output "Hello, World!"' } } } }
Here's the console output:
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build)
[Pipeline] powershell
[devel] Running PowerShell script
And it just times out after an hour.
Powershell tasks were working last week. The change may have coincided with a Jenkins update from 2.73.2 to 2.73.3, but I reverting back to 2.73.2 has not resolved the issue.
- duplicates
-
JENKINS-46508 Powershell Pipeline Step hangs if capturing Stdout and output is null
- Closed
-
JENKINS-46876 PowerShell: incorrect handling of $LASTEXITCODE can cause broken script to not abort pipeline
- Closed