Groups
Groups
Sign in
Groups
Groups
Jenkins Issues
Conversations
About
Send feedback
Help
[JIRA] (JENKINS-53500) container step fails on Windows agents with "java.io.IOException: Pipe closed"
11 views
Skip to first unread message
jglick@cloudbees.com (JIRA)
unread,
Sep 30, 2019, 12:59:02 PM
9/30/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jenkinsc...@googlegroups.com
Jesse Glick
updated
an issue
Jenkins
/
JENKINS-53500
container step fails on Windows agents with "java.io.IOException: Pipe closed"
Change By:
Jesse Glick
Summary:
Kubernetes Pipeline
container step
fails on Windows agents with "java.io.IOException: Pipe closed"
Add Comment
This message was sent by Atlassian Jira
(v7.13.6#713006-
sha1:cc4451f
)
jglick@cloudbees.com (JIRA)
unread,
Oct 22, 2019, 4:57:03 PM
10/22/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jenkinsc...@googlegroups.com
Jesse Glick
assigned
an issue to
Jesse Glick
Jenkins
/
JENKINS-53500
container step fails on Windows agents with "java.io.IOException: Pipe closed"
Change By:
Jesse Glick
Assignee:
Ioannis Canellos
Jesse Glick
Add Comment
jglick@cloudbees.com (JIRA)
unread,
Oct 22, 2019, 4:57:52 PM
10/22/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jenkinsc...@googlegroups.com
Jesse Glick
started work
on
JENKINS-53500
Change By:
Jesse Glick
Status:
Open
In Progress
Add Comment
jglick@cloudbees.com (JIRA)
unread,
Oct 24, 2019, 7:16:03 PM
10/24/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jenkinsc...@googlegroups.com
Jesse Glick
updated
JENKINS-53500
Jenkins
/
JENKINS-53500
container step fails on Windows agents with "java.io.IOException: Pipe closed"
Change By:
Jesse Glick
Status:
In
Progress
Review
Add Comment
jglick@cloudbees.com (JIRA)
unread,
Oct 30, 2019, 9:09:11 AM
10/30/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jenkinsc...@googlegroups.com
Jesse Glick
updated
JENKINS-53500
Jenkins
/
JENKINS-53500
container step fails on Windows agents with "java.io.IOException: Pipe closed"
Change By:
Jesse Glick
Status:
In Review
Fixed but Unreleased
Resolution:
Fixed
Add Comment
vincent@latombe.net (JIRA)
unread,
Oct 30, 2019, 11:05:04 AM
10/30/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jenkinsc...@googlegroups.com
Vincent Latombe
updated
JENKINS-53500
Jenkins
/
JENKINS-53500
container step fails on Windows agents with "java.io.IOException: Pipe closed"
Change By:
Vincent Latombe
Status:
Fixed but Unreleased
Closed
Released As:
kubernetes-1.21.0
Add Comment
Reply all
Reply to author
Forward
0 new messages