[JIRA] (JENKINS-50392) Use the right API to get process' exitcode

2018-10-16 Thread vinc...@latombe.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50392  
 
 
  Use the right API to get process' exitcode   
 

  
 
 
 
 

 
Change By: 
 Vincent Latombe  
 

  
 
 
 
 

 
 The current kubernetes-client library doesn't properly support the `error` websocket channel, merging it into stderr instead.Because of this, getting the proper return code of a `sh` step involved parsing stderr, string manipulation, breaking other plugins that rely on stdout parsing too (e.g. pipeline-maven), and workarounds ([https://github.com/jenkinsci/kubernetes-plugin/pull/242 ] ). ] [https://github.com/fabric8io/kubernetes-client/pull/1045] adds proper support to the error channel, so the returned information can be fetched separately. See [https://github.com/kubernetes-client/python/issues/297] as an example.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50392) Use the right API to get process' exitcode

2018-05-25 Thread jenkins...@carlossanchez.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Sanchez updated  JENKINS-50392  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50392  
 
 
  Use the right API to get process' exitcode   
 

  
 
 
 
 

 
Change By: 
 Carlos Sanchez  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50392) Use the right API to get process' exitcode

2018-03-26 Thread jenkins...@carlossanchez.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Sanchez started work on  JENKINS-50392  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Carlos Sanchez  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50392) Use the right API to get process' exitcode

2018-03-25 Thread giuseppe.ianne...@brokenloop.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Giuseppe Iannello created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50392  
 
 
  Use the right API to get process' exitcode   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Carlos Sanchez  
 
 
Components: 
 kubernetes-plugin  
 
 
Created: 
 2018-03-25 12:09  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Giuseppe Iannello  
 

  
 
 
 
 

 
 The current kubernetes-client library doesn't properly support the `error` websocket channel, merging it into stderr instead. Because of this, getting the proper return code of a `sh` step involved parsing stderr, string manipulation, breaking other plugins that rely on stdout parsing too (e.g. pipeline-maven), and workarounds (https://github.com/jenkinsci/kubernetes-plugin/pull/242). https://github.com/fabric8io/kubernetes-client/pull/1045 adds proper support to the error channel, so the returned information can be fetched separately. See https://github.com/kubernetes-client/python/issues/297 as an example.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment