[JIRA] [active-choices-plugin] (JENKINS-32044) Fail to evaluate Boolean parameter to "on" when checked
Title: Message Title Gil Shinar commented on JENKINS-32044 Re: Fail to evaluate Boolean parameter to "on" when checked So maybe the issue is with chrome? I'll test that with FF 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] [junit-plugin] (JENKINS-32148) highlight test result lines on hover
Title: Message Title Dirk Thomas updated an issue Jenkins / JENKINS-32148 highlight test result lines on hover Change By: Dirk Thomas Summary: highlight test result lines on hover 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] [junit-plugin] (JENKINS-32148) highlight lines on hover
Title: Message Title
Dirk Thomas created an issue
Jenkins / JENKINS-32148
highlight lines on hover
Issue Type:
Improvement
Assignee:
Unassigned
Components:
junit-plugin
Created:
20/Dec/15 12:50 AM
Priority:
Trivial
Reporter:
Dirk Thomas
The tables ("All failed tests" and "All Tests") can be very wide. When looking at the test names in the first column it is not that easy to see which values in the other columns belong to the same row. It would be a great improvement if each line would highlight (change its background color) on hover.
Something similar already happens for each build in the build history on the left pane and in the parameter form when triggering a parameterized build.
Add Comment
[JIRA] [bitbucket-approve-plugin] (JENKINS-32147) Support setting build status in bitbucket.
Title: Message Title Anders Kreinøe created an issue Jenkins / JENKINS-32147 Support setting build status in bitbucket. Issue Type: New Feature Assignee: Björn Hurling Components: bitbucket-approve-plugin Created: 19/Dec/15 9:35 PM Priority: Minor Reporter: Anders Kreinøe Bitbucket now supports setting build status: http://blog.bitbucket.org/2015/11/18/introducing-the-build-status-api-for-bitbucket-cloud/ This will in many cases be a better solution than approving a commit. Add Comment
[JIRA] [bitbucket-plugin] (JENKINS-29606) Approve/unapprove pull requests based on build status
Title: Message Title Anders Kreinøe commented on JENKINS-29606 Re: Approve/unapprove pull requests based on build status Or better, use bitbuckets new build status support: http://blog.bitbucket.org/2015/11/18/introducing-the-build-status-api-for-bitbucket-cloud/ 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] [dashboard-view-plugin] (JENKINS-29690) Icons missing in Build Statistics portlet
Title: Message Title Oliver Gondža commented on JENKINS-29690 Re: Icons missing in Build Statistics portlet Thanks for the fix Daniel, 2.9.7 is underway. I do not consider myself the maintainer, FTR. 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] [sqlplus-script-runner-plugin] (JENKINS-31597) SQLPlus Script Runner Plugin: ORACLE_HOME at job or slave level
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31597 Re: SQLPlus Script Runner Plugin: ORACLE_HOME at job or slave level Code changed in jenkins User: Bruno P. Kinoshita Path: pom.xml src/main/java/org/jenkinsci/plugins/sqlplusscriptrunner/ExternalProgramUtil.java src/main/java/org/jenkinsci/plugins/sqlplusscriptrunner/SQLPlusRunner.java src/main/java/org/jenkinsci/plugins/sqlplusscriptrunner/SQLPlusRunnerBuilder.java src/main/java/org/jenkinsci/plugins/sqlplusscriptrunner/SQLPlusRunnerException.java src/test/java/org/jenkinsci/plugins/sqlplusscriptrunner/test/TestSQLPlus.java http://jenkins-ci.org/commit/sqlplus-script-runner-plugin/a8e31456464d4841be0a634b558c697dff81e864 Log: JENKINS-31597 First tentative of adding support to distributed builds - WIP, not thoroughly tested 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] [sqlplus-script-runner-plugin] (JENKINS-31597) SQLPlus Script Runner Plugin: ORACLE_HOME at job or slave level
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31597 Re: SQLPlus Script Runner Plugin: ORACLE_HOME at job or slave level Code changed in jenkins User: Fernando Boaglio Path: pom.xml src/main/java/org/jenkinsci/plugins/sqlplusscriptrunner/ExternalProgramUtil.java src/main/java/org/jenkinsci/plugins/sqlplusscriptrunner/SQLPlusRunner.java src/main/java/org/jenkinsci/plugins/sqlplusscriptrunner/SQLPlusRunnerBuilder.java src/main/java/org/jenkinsci/plugins/sqlplusscriptrunner/SQLPlusRunnerException.java src/test/java/org/jenkinsci/plugins/sqlplusscriptrunner/test/TestSQLPlus.java http://jenkins-ci.org/commit/sqlplus-script-runner-plugin/7d37f211e18e222c68c439046fc8e2b491ffd221 Log: Merge pull request #1 from kinow/master JENKINS-31597 First tentative of adding support to distributed builds - WIP, not thoroughly tested Compare: https://github.com/jenkinsci/sqlplus-script-runner-plugin/compare/4bca186d5f06...7d37f211e18e 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] [prioritysorter-plugin] (JENKINS-32138) Impossible to assign priority more than 5
Title: Message Title
Alexey Pakseykin updated an issue
Jenkins / JENKINS-32138
Impossible to assign priority more than 5
Change By:
Alexey Pakseykin
It seems there is no priorities more than 5.It is impossible to assign such priority more than 5 in GUI as well as directly in XML .There is XML configuration for Jenkins (e.g. on Linux) {{/var/lib/jenkins/jenkins.advancedqueue.PriorityConfiguration.xml}}. However, even if I set priority more than 5 directly inside XML file, for any such priority is shows "-- use default priority --" in GUI.
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] [embeddable-build-status-plugin] (JENKINS-25384) Custom label for builds
Title: Message Title Sami Kankaristo commented on JENKINS-25384 Re: Custom label for builds Just found this: https://github.com/badges/shields That's the "badge standard" that's being used by shields.io. It seems to have been adopted by a lot of services, including Travis CI and Coveralls. Sounds like a relatively simple solution? I'm not suggesting to use shields.io (doesn't make sense to eat their bandwidth), but you could use their code to generate an SVG? 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] [workflow-plugin] (JENKINS-32146) ArtifactArchiver does not mark step as failing
Title: Message Title ngiger created an issue Jenkins / JENKINS-32146 ArtifactArchiver does not mark step as failing Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 19/Dec/15 1:40 PM Priority: Minor Reporter: ngiger I created a small project https://github.com/ngiger/jenkins-bug which produces contains two ArtifactArchivers steps. Both have fingreprinting enabled. I created a Multibranch Worksflow project, using the Jenkinsfile from the github project mentioned aboed. The first step one completes successfully, as the file exist. The second step one references a non existing file. All steps of the build have the blue icon, but inside the build.xml I see only one line FAILURE whereas the successful step hadREADME.md 3f7c3b7d5e5d582a09643416b80fafaf Add Comment
[JIRA] [gearman-plugin] (JENKINS-28936) Gearman plugin should not decide on which node a build should be executed
Title: Message Title Antoine Musso commented on JENKINS-28936 Re: Gearman plugin should not decide on which node a build should be executed I am facing with issue as well with the Throttle Concurrent Builds Plugin. My use case can be summarized down to: permanent slaves having 2 executors. Slave 1 and Slave 2 A long job consuming lot of disk space. The job is allowed to run concurrently, but since it almost starve a slave, I am using the Throttle Concurrent Builds Plugin to only allow one instance of the job per node. I have no idea how the Zuul Gearman server schedule the jobs, it seems to be using round robin over all available workers with Gearman Plugin reassigning the worker to a Jenkins executor slot on the fly. Anyway I often end up with: Slave 1 running the job Slave 2 idling The Jenkins queue showing the job waiting for next available executor on Slave 1. Looking at https://github.com/jenkinsci/throttle-concurrent-builds-plugin it implements the same extension point / method: QueueTaskDispatcher.canTake() which state: Vetos are additive. When multiple QueueTaskDispatchers are in the system, the task won't run on the given node if any one of them returns a non-null value. (This relationship is also the same with built-in check logic.) So it is blocked properly. But as noted by Christian, there is only one node to choose from anyway. Seems GearmanProxy.canTake() iterates all the node workers threads and simply rely on NodeAvailabilityMonitor.canTake() which seems to have its own locking not respecting QueueTaskDispatcher.canTake() which is altered by other plugins. Could GearmanProxy.canTake() ask the QueueTaskDispatcher instead? Add Comment
[JIRA] [core] (JENKINS-31256) hudson.Remoting.Engine#waitForServerToBack does not use credentials for connection
Title: Message Title Tim Pambor commented on JENKINS-31256 Re: hudson.Remoting.Engine#waitForServerToBack does not use credentials for connection I submitted a pull request for this bug. https://github.com/jenkinsci/remoting/pull/67 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-31256) hudson.Remoting.Engine#waitForServerToBack does not use credentials for connection
Title: Message Title Tim Pambor assigned an issue to Tim Pambor Jenkins / JENKINS-31256 hudson.Remoting.Engine#waitForServerToBack does not use credentials for connection Change By: Tim Pambor Assignee: Tim Pambor 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-31256) hudson.Remoting.Engine#waitForServerToBack does not use credentials for connection
Title: Message Title Tim Pambor started work on JENKINS-31256 Change By: Tim Pambor Status: Open In Progress 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] [active-choices-plugin] (JENKINS-29476) The 'jenkinsProject' variable is not set in the binding after restarting Jenkins
Title: Message Title Bruno P. Kinoshita commented on JENKINS-29476 Re: The 'jenkinsProject' variable is not set in the binding after restarting Jenkins This will be the last issue fixed before the 1.3 release (probably before x-mas) 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] [active-choices-plugin] (JENKINS-29476) The 'jenkinsProject' variable is not set in the binding after restarting Jenkins
Title: Message Title Bruno P. Kinoshita started work on JENKINS-29476 Change By: Bruno P. Kinoshita Status: Open In Progress 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] [active-choices-plugin] (JENKINS-30592) An AC Reactive Reference is always displayed unless it references a parameter
Title: Message Title Bruno P. Kinoshita commented on JENKINS-30592 Re: An AC Reactive Reference is always displayed unless it references a parameter Fixed, but we will need to run some manual tests to make sure we don't introduce a regression here. The parameters marked to be hidden, were being hidden during a for loop for each referenced parameter. I believe this may speed up the plug-in behaviour a little bit, and also fix the issue reported. Unit tests (Java and JS) pass with no errors. Parameters seem to work fine in the browser, but might still be a good idea to run some further testing before releasing a with 1.3. Will attach a plug-in version here with the fix. 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] [active-choices-plugin] (JENKINS-30592) An AC Reactive Reference is always displayed unless it references a parameter
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30592 Re: An AC Reactive Reference is always displayed unless it references a parameter Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/resources/org/biouno/unochoice/DynamicReferenceParameter/index.jelly http://jenkins-ci.org/commit/active-choices-plugin/c603534b41ac9ce6af48a99bd5dbb22cf7900a21 Log: [FIXED JENKINS-30592] Hide hidden formatted parameters right after the elements are created in the DOM 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] [active-choices-plugin] (JENKINS-30592) An AC Reactive Reference is always displayed unless it references a parameter
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-30592 An AC Reactive Reference is always displayed unless it references a parameter Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed 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] [active-choices-plugin] (JENKINS-30592) An AC Reactive Reference is always displayed unless it references a parameter
Title: Message Title Bruno P. Kinoshita commented on JENKINS-30592 Re: An AC Reactive Reference is always displayed unless it references a parameter Oh, successfully reproduced the issue. Interesting. Not really sure why that's happening, but I believe it might be easy to fix. 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] [active-choices-plugin] (JENKINS-32044) Fail to evaluate Boolean parameter to "on" when checked
Title: Message Title Bruno P. Kinoshita resolved as Cannot Reproduce Could not reproduce it. The script seems to be working as expected. By the default the checkbox is not checked, and the single select value is false. Then if you check the boolean parameter, the cascaded parameter changes its value to true. Firefox 43.0, Ubuntu Server LTS 14.04.3. Jenkins / JENKINS-32044 Fail to evaluate Boolean parameter to "on" when checked Change By: Bruno P. Kinoshita Status: Open Resolved Resolution: Cannot Reproduce 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] [embeddable-build-status-plugin] (JENKINS-25384) Custom label for builds
Title: Message Title Sami Kankaristo commented on JENKINS-25384 Re: Custom label for builds This would also be really useful for us, because we want to track Linux, OS X and Windows builds. Later we might add a Jenkins job for e.g. generating documentation, which would also benefit from this. I wouldn't mind creating the images myself, so just allowing custom passing/failing images per job would be a good solution for us. Generating the image from a string would be even better, but obviously more complex to develop. 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] [active-choices-plugin] (JENKINS-32044) Fail to evaluate Boolean parameter to "on" when checked
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-32044 Fail to evaluate Boolean parameter to "on" when checked Change By: Bruno P. Kinoshita Attachment: config_2.xml 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] [active-choices-plugin] (JENKINS-32044) Fail to evaluate Boolean parameter to "on" when checked
Title: Message Title Bruno P. Kinoshita commented on JENKINS-32044 Re: Fail to evaluate Boolean parameter to "on" when checked Environment settings: Jenkins ver. 1.625.3 (downloaded from jenkins-ci.org, running with a new JENKINS_HOME directory) Job attached (config_2.xml) uno-choice 1.2 jquery 1.11.2-0 The script seemed to work with for both LTS versions tested, with and without the JQuery plug-in. 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] [active-choices-plugin] (JENKINS-32044) Fail to evaluate Boolean parameter to "on" when checked
Title: Message Title Bruno P. Kinoshita commented on JENKINS-32044 Re: Fail to evaluate Boolean parameter to "on" when checked Working for 1.625.3 + Active Choices 1.2, but no JQuery plug-in. 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] [active-choices-plugin] (JENKINS-32044) Fail to evaluate Boolean parameter to "on" when checked
Title: Message Title Bruno P. Kinoshita edited a comment on JENKINS-32044 Re: Fail to evaluate Boolean parameter to "on" when checked Could not reproduce it with 1.580.1 without the JQuery plug-in . Trying with 1.625.3 now. 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] [active-choices-plugin] (JENKINS-32044) Fail to evaluate Boolean parameter to "on" when checked
Title: Message Title Bruno P. Kinoshita commented on JENKINS-32044 Re: Fail to evaluate Boolean parameter to "on" when checked Could not reproduce it with 1.580.1. Trying with 1.625.3 now. 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] [jira-plugin] (JENKINS-32145) ERROR Jira plugin
Title: Message Title Radek Antoniuk commented on JENKINS-32145 Re: ERROR Jira plugin What JIRA and plugin version? 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.
