[JIRA] (JENKINS-46988) String.eachLine only reads first line
Title: Message Title Jo Rhett edited a comment on JENKINS-46988 Re: String.eachLine only reads first line I don't feel that this issue is Minor, nor do I feel that the workaround is an acceptable solution. This basically means that every Jenkins user worldwide will burn some hours diagnosing this problem only to end up here. That this bug is more than 2 years old speaks to a significant lack of care. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185366.1505906799000.9909.1571332140516%40Atlassian.JIRA.
[JIRA] (JENKINS-46988) String.eachLine only reads first line
Title: Message Title Jo Rhett edited a comment on JENKINS-46988 Re: String.eachLine only reads first line I don'tfeel that this issue is Minor, nor do I feel that the workaround is an acceptable solution. This basically means that every Jenkins user worldwide will burn some hours diagnosing this problem only to end up here. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185366.1505906799000.9892.1571331901488%40Atlassian.JIRA.
[JIRA] (JENKINS-46988) String.eachLine only reads first line
Title: Message Title Jo Rhett commented on JENKINS-46988 Re: String.eachLine only reads first line I don't Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185366.1505906799000.9849.1571331120466%40Atlassian.JIRA.
[JIRA] (JENKINS-54250) Disable restarting stages in jenkinsfile optionally
Title: Message Title
Jo Rhett commented on JENKINS-54250
Re: Disable restarting stages in jenkinsfile optionally
Alex Simenduev add it to a pipeline library as documented at https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-custom-steps Thanks Jonathan Sokolowski but I wanted to point out this doesn't solve the situation for any stage which has a when section and is also a required build step. (GitHub accepts "I didn't do this stage" as pass )
Stage "Validate changed files" skipped due to this build restarting at stage "Run downstream jobs"
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Run downstream jobs)
Stage "Run downstream jobs" skipped due to when conditional
Build shows green, let's deploy! (facepalm) This really needs a global option.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194892.1540468831000.4086.1570672680496%40Atlassian.JIRA.
[JIRA] (JENKINS-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Jo Rhett commented on JENKINS-49997 Re: Pipeline Declarative post unsuccessful block It would be really awesome if the documentation at https://jenkins.io/doc/book/pipeline/syntax/#post-conditions mentioned which states unsuccessful includes, so that we don't have to search to find this issue 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188994.1520441679000.9923.1565193660320%40Atlassian.JIRA.
[JIRA] (JENKINS-58631) kubernetes-plugin defaultContainer is not documented
Title: Message Title Jo Rhett created an issue Jenkins / JENKINS-58631 kubernetes-plugin defaultContainer is not documented Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-07-24 08:10 Priority: Minor Reporter: Jo Rhett The README refers to the defaultContainer option, and show its use in examples... but does not document this as an option or describe what it does. Can one safely use this to avoid having container() blocks in every stage? Any impact on the JNLP container which manages the master connection? Add Comment
