[JIRA] (JENKINS-39415) Xvfb in a parallel pipeline doesn't use the executor number as display name
Title: Message Title Giuseppe Iannello commented on JENKINS-39415 Re: Xvfb in a parallel pipeline doesn't use the executor number as display name We managed to track down those random failures to the plugin timing out waiting for Xvfb to return a display number. Increasing the timeout with 'autoDisplayName': true, 'timeout': 15 solves the problem, but slows down the builds - as far as I understood, that's not really a timeout, but more like a wait time before checking the output of Xvfb for the display number. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [saltstack-plugin] (JENKINS-34053) Add support for local_subset client
Title: Message Title Giuseppe Iannello created an issue Jenkins / JENKINS-34053 Add support for local_subset client Issue Type: New Feature Assignee: Christian McHugh Components: saltstack-plugin Created: 2016/Apr/06 9:59 AM Priority: Major Reporter: Giuseppe Iannello Despite the documentation is not mentioning it, it seems like SaltStack NetApi currently supports the local_subset client (https://github.com/saltstack/salt/blob/develop/salt/netapi/__init__.py) Would be great to have it available in the saltstack plugin. Add Comment
[JIRA] [saltstack-plugin] (JENKINS-34049) Errors from minions not detected
Title: Message Title Giuseppe Iannello created an issue Jenkins / JENKINS-34049 Errors from minions not detected Issue Type: Bug Assignee: Christian McHugh Components: saltstack-plugin Created: 2016/Apr/06 8:34 AM Environment: saltstack plugin 1.7.0 Priority: Critical Reporter: Giuseppe Iannello Return codes from minions are not correctly handled. Executing the following command on the salt master root@xxx:~# salt 'salt-master' cmd.run '/bin/false' salt-master: ERROR: Minions returned with non-zero exit code root@xxx:~# echo $? 11 correctly reports the failure. Executing the same command with the saltstack plugin results in a SUCCESSful build, instead of a FAILURE.
[JIRA] [build-pipeline-plugin] (JENKINS-33122) Add filter for "Show pipeline parameters"
Title: Message Title Giuseppe Iannello created an issue Jenkins / JENKINS-33122 Add filter for "Show pipeline parameters" Issue Type: Bug Assignee: Unassigned Attachments: Screenshot from 2016-02-24 11-30-30.png Components: build-pipeline-plugin Created: 24/Feb/16 10:43 AM Priority: Minor Reporter: Giuseppe Iannello When displaying a build with a lot of parameters, like those triggered by the GitHub Pull Request Builder plugin, the resulting view is pretty broken, due to the amount of params and the length of their values. It would be extremely useful to have a filter that allows to display only a subset of parameters - whatever is relevant for displaying on a shared screen Add Comment
[JIRA] [ghprb-plugin] (JENKINS-33121) "Commit status build result" uses wrong context
Title: Message Title Giuseppe Iannello created an issue Jenkins / JENKINS-33121 "Commit status build result" uses wrong context Issue Type: Bug Assignee: Honza Brázdil Attachments: Screenshot from 2016-02-24 11-22-24.png Components: ghprb-plugin Created: 24/Feb/16 10:25 AM Environment: Jenkins 1.649, GHPRB plugin 1.30.4 Priority: Trivial Reporter: Giuseppe Iannello When setting up a custom Commit Status Context, the custom Commit Status Build Result messages are not respecting it, and post to GitHub as "default". That results in GitHub thinking there are 2 separate build processes, and one remains in "pending" state.
[JIRA] [ghprb-plugin] (JENKINS-31686) Jenkins injects the old git commit as GIT_COMMIT env variable
Title: Message Title Giuseppe Iannello commented on JENKINS-31686 Re: Jenkins injects the old git commit as GIT_COMMIT env variable +1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31458) NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameter
Title: Message Title Giuseppe Iannello edited a comment on JENKINS-31458 Re: NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition Confirmed solved in 1.640 + Extended Choice Parameter v0.55 Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31458) NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameter
Title: Message Title Giuseppe Iannello commented on JENKINS-31458 Re: NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition Confirmed solved in 1.640 Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31458) NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameter
Title: Message Title Giuseppe Iannello updated an issue Jenkins / JENKINS-31458 NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition Change By: Giuseppe Iannello Environment: Jenkins ver. 1.637, Jenkins ver. 1.638 , Jenkins ver. 1.639 Plugin ver. 0.53 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [extended-choice-parameter-plugin] (JENKINS-31458) Exception when saving job configuration
Title: Message Title Giuseppe Iannello commented on JENKINS-31458 Re: Exception when saving job configuration We keep jenkins always up-to-date, but since we didn't edit/create jobs so often I can't tell exactly which version broke the plugin. I can roughly assume it's something released in the last 4 weeks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [extended-choice-parameter-plugin] (JENKINS-31458) Exception when saving job configuration
Title: Message Title Giuseppe Iannello updated an issue Jenkins / JENKINS-31458 Exception when saving job configuration Change By: Giuseppe Iannello Environment: Jenkins ver. 1.637 , Jenkins ver. 1.638 Plugin ver. 0.53 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [extended-choice-parameter-plugin] (JENKINS-31458) Exception when saving job configuration
Title: Message Title Giuseppe Iannello created an issue Jenkins / JENKINS-31458 Exception when saving job configuration Issue Type: Bug Assignee: vimil Components: extended-choice-parameter-plugin Created: 09/Nov/15 3:17 PM Environment: Jenkins ver. 1.637 Plugin ver. 0.53 Priority: Blocker Reporter: Giuseppe Iannello When changing the configuration for a job that includes a parameter provided by the plugin, the following stack trace is shown after saving, and the job is not updated. This is preventing any job using an Extended Choice Parameter to be reconfigured. Error while serving https://[redacted]:8080/job/Deploy/job/Staging/configSubmit java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(Met
[JIRA] [android-emulator-plugin] (JENKINS-27456) Emulator can't connect to adb server!?
Title: Message Title Giuseppe Iannello commented on JENKINS-27456 Re: Emulator can't connect to adb server!? +1 - same setup, same problem. It also appears that launching the emulator manually and configuring the job with the running emulator's name doesn't work, as the plugin will try to start the emulator again Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
