[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title Benjamin Heilbrunn commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once We already encountered multiple use cases where we needed to parse STDOUT in case a certain exit code happened. Would be great to have this feature. 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-44141) Define a resource pool
Title: Message Title Benjamin Heilbrunn edited a comment on JENKINS-44141 Re: Define a resource pool +1 for a pool of resources from where I can draw (random) resource instances that the are then locked until explicitly released by the build 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-44141) Define a resource pool
Title: Message Title Benjamin Heilbrunn commented on JENKINS-44141 Re: Define a resource pool +1 for a pool of resources from where I can draw instances that the are then locked until explicitly released by the build 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-49535) Error message of missing credentials entry not meaningful to end user
Title: Message Title Benjamin Heilbrunn updated an issue Jenkins / JENKINS-49535 Error message of missing credentials entry not meaningful to end user Change By: Benjamin Heilbrunn If exceptions occur in a stage, Jenkins Blue Ocean will only show the exception message in the log. Additional context via the stacktrace is only available if users explicitly switch back to the "old" log viewer.Given this behavior, in case of missing credentials, the behavior of the credentials binding plugin is problematic. If it fails, it only provides the credentials ID as output via the CredentialNotFoundException message. This makes it hard for Blue Ocean users to get a grasp of the problem.See: [ SCREENSHOT| https://user-images.githubusercontent.com/916316/35906147-cd18d0e2-0be9-11e8-95f8-17eae02c54ea.png |http://example.com/ ] We created a PR that would fix the issue. A review is appreciated.[https://github.com/jenkinsci/credentials-binding-plugin/pull/48] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49535) Error message of missing credentials entry not meaningful to end user
Title: Message Title Benjamin Heilbrunn created an issue Jenkins / JENKINS-49535 Error message of missing credentials entry not meaningful to end user Issue Type: Improvement Assignee: Jesse Glick Components: credentials-binding-plugin Created: 2018-02-13 17:40 Priority: Minor Reporter: Benjamin Heilbrunn If exceptions occur in a stage, Jenkins Blue Ocean will only show the exception message in the log. Additional context via the stacktrace is only available if users explicitly switch back to the "old" log viewer. Given this behavior, in case of missing credentials, the behavior of the credentials binding plugin is problematic. If it fails, it only provides the credentials ID as output via the CredentialNotFoundException message. This makes it hard for Blue Ocean users to get a grasp of the problem. See: https://user-images.githubusercontent.com/916316/35906147-cd18d0e2-0be9-11e8-95f8-17eae02c54ea.png We created a PR that would fix the issue. A review is appreciated. https://github.com/jenkinsci/credentials-binding-plugin/pull/48 Add Comment
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Benjamin Heilbrunn commented on JENKINS-49278 Re: cat command in docker agents not detected correctly Nicolas De Loof, thanks for the quick fix! 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.
