[JIRA] [cobertura] (JENKINS-23183) Add precision option for the Stability auto update/Health auto update options
Christof Schablinski created JENKINS-23183 Add precision option for the Stability auto update/Health auto update options Issue Type: Improvement Assignee: stephenconnolly Components: cobertura Created: 26/May/14 7:18 AM Description: The options "Stability auto update"/"Health auto update" are quite useful for legacy projects. But getting an unstable build, because the coverage decreased from 21.35 to 21.34 doesn't increase acceptance of this feature. I'd like a lesser precision like 21.3 or 21. Project: Jenkins Priority: Major Reporter: Christof Schablinski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [master-slave] (JENKINS-11992) Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing ' \Java\jre6\bin was unexpected at this time.' error
Robert Grampp commented on JENKINS-11992 Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing \Java\jre6\bin was unexpected at this time. error Hi Chris, thanks for your suggestion, but the problem isn't having spaces in a directory path. The initial problem is that Jenkins adds the path to Java surrounded with quotes! Jenkins adds ;"C:\Program Files (x86)\Java\jre6\bin" to PATH variable. On Windows even directories containing spaces are added without surrounded spaces. That's the change that the Jenkins developers should do. You see this when calling path command on any Windows system, e. g. = PATH=C:\Program Files\Common Files\Microsoft Shared\... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [www] (JENKINS-13401) Provide md5 checksums for updates.jenkins-ci.org download files
Oleg Nenashev commented on JENKINS-13401 Provide md5 checksums for updates.jenkins-ci.org download files Moving to the INFRA project This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [update-center] (JENKINS-13721) Update-Center FileNotFoundException, Status 404
Oleg Nenashev resolved JENKINS-13721 as Fixed Update-Center FileNotFoundException, Status 404 Marking the issue as "Resolved" again Change By: Oleg Nenashev (26/May/14 8:13 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-18718) It isn't clear if you should restart Jenkins after installing a plugin
Sebastian Schuberth commented on JENKINS-18718 It isnt clear if you should restart Jenkins after installing a plugin In the blog article at 1 the author of that feature writes: "I'm even thinking about removing the latter button after a while, once we gain enough confidence in the feature. I can't think of any inherent reasons the latter is desirable over the former. - See more at: http://blog.cloudbees.com/2011/12/installing-plugins-to-jenkins-without.html#sthash.9vT7pY4U.dpuf" Given that this was in December 2011 I'd say it's finally time to get rid of the "Download and Install after restart" completely. 1 http://blog.cloudbees.com/2011/12/installing-plugins-to-jenkins-without.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [javadoc] (JENKINS-1000) Multiple JavaDoc Locations per Project
Oleg Nenashev updated JENKINS-1000 Multiple JavaDoc Locations per Project Change By: Oleg Nenashev (26/May/14 8:28 AM) Component/s: javadoc Component/s: other This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [other] (JENKINS-4326) Exception thrown in polling on remote node is not shown in UI
Oleg Nenashev resolved JENKINS-4326 as Fixed Exception thrown in polling on remote node is not shown in UI Seems to be fixed in latest Jenkins versions Change By: Oleg Nenashev (26/May/14 8:30 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16227) ProjectNamingStrategy: remove Default Strategy from the UI
Harald Albers commented on JENKINS-16227 ProjectNamingStrategy: remove Default Strategy from the UI This would be a much better solution than my original suggestion. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-22949) If a QueueItemAuthenticator is configured but returns null, use ANONYMOUS not SYSTEM
Oleg Nenashev commented on JENKINS-22949 If a QueueItemAuthenticator is configured but returns null, use ANONYMOUS not SYSTEM I suppose that the default user should be configurable from the global security page. SYSTEM should be default (with scary red/yellow warning, of course) Otherwise, it's hard to predict all possible regressions This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-22949) If a QueueItemAuthenticator is configured but returns null, use ANONYMOUS not SYSTEM
Oleg Nenashev edited a comment on JENKINS-22949 If a QueueItemAuthenticator is configured but returns null, use ANONYMOUS not SYSTEM I think that the default user should be configurable from the global security page. SYSTEM should be default (with scary red/yellow warning, of course) Otherwise, it's hard to predict all possible regressions This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [perforce] (JENKINS-23184) Perforce plugin to contribute more env variables for the build
Mikko Tapaninen created JENKINS-23184 Perforce plugin to contribute more env variables for the build Issue Type: Bug Assignee: Rob Petti Components: perforce Created: 26/May/14 8:38 AM Description: I would like Perforce plugin to contribute more environment variables for the build. These are what we need: PERFORCE_DEPOT the depot part of the stream definition (e.g. if stream field defined like //foo/bar then PERFORCE_DEPOT=foo) PERFORCE_STREAM the latter part of the stream definition (e.g. if stream field defined like //foo/bar then PERFORCE_STREAM=bar) PERFORCE_CHANGELIST_SOURCE same as P4_CHANGELIST PERFORCE_CHANGELIST_SOURCE_DATE the timestamp of the latest changelist (PERFORCE_CHANGELIST_SOURCE) in the build Project: Jenkins Priority: Major Reporter: Mikko Tapaninen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-22900) Access log doesn't contain user names
Oleg Nenashev updated JENKINS-22900 Access log doesnt contain user names Not a bug. BTW, an additional input from the submitter would be useful Change By: Oleg Nenashev (26/May/14 8:38 AM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [cppcheck] (JENKINS-23185) Setting build status to FAILURE for new error when errors were fixed
Jan Klass created JENKINS-23185 Setting build status to FAILURE for new error when errors were fixed Issue Type: Bug Assignee: Gregory Boissinot Components: cppcheck Created: 26/May/14 8:38 AM Description: It seems the functionality to mark builds as failed for "new errors" uses the total number of errors in the new result data, rather than the delta of errors. Currently, if one of two errors is fixed, the build will be marked as failed with a new error threshold of 1. Noticed with new error threshold of 1, having 6 errors, then checking in a new build with the result of 4 errors and 26 style warnings. Cppcheck Setting build status to FAILURE since total number of new errors exceeds the threshold value '1'. Jenkins 1.554.1, CPPCheck plugin 1.16 Project: Jenkins Priority: Major Reporter: Jan Klass This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-9597) Autocomplete box in text boxes is not selectable using the enter key
Stas Gromov reopened JENKINS-9597 Autocomplete box in text boxes is not selectable using the enter key reproduced on https://ci.jenkins-ci.org/login?from=%2F Browser: Firefox 29.0.1 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 OS: ArchLinux (x86_64 GNU/Linux) Jenkins ver. 1.565-SNAPSHOT (rc-05/20/2014 18:32 GMT-kohsuke) steps: 1.mouse left-click in first field (field was selected) 2.keypress down-arrow-key (drop-down menu was showed) 3.keypress down-arrow-key once more time (first option in drop-down menu was selected) 4.press "Enter" key to select this option. Expected: option, selected in drop-down-menu, will be in field Actual: option, selected in drop-down-menu, was shown in field and then form automaticaly submits. And then screen with " Invalid login information. Please try again. Try again" was shown Change By: Stas Gromov (26/May/14 8:40 AM) Resolution: CannotReproduce Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-22811) Folder loading can be broken by a NPE in a build wrapper in one job
Oleg Nenashev commented on JENKINS-22811 Folder loading can be broken by a NPE in a build wrapper in one job @Jesse Have you submitted a bug to Artifactory plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [pxe] (JENKINS-9959) PXE NullPointerException While Loading PXE Plugin
Oleg Nenashev updated JENKINS-9959 PXE NullPointerException While Loading PXE Plugin Seems to be an issue in the PXE plugin. Fixed the cpomponent Change By: Oleg Nenashev (26/May/14 8:43 AM) Component/s: pxe Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [pxe] (JENKINS-9958) PXE BindException: Permission denied Even After Setting root Username and Password
Oleg Nenashev updated JENKINS-9958 PXE BindException: Permission denied Even After Setting root Username and Password Seems to be an issue in the PXE plugin. Fixed the cpomponent Change By: Oleg Nenashev (26/May/14 8:44 AM) Component/s: pxe Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-22900) Access log doesn't contain user names
Dirk Heinrichs commented on JENKINS-22900 Access log doesnt contain user names What kind of additional info do you need? I don't think it's not a bug, btw. Jenkins still uses the Winstone options for logging. Winstone docs say there's a username in the output. Jenkins doesn't log the username - bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-9451) Connection reset - windows slave exits from time to time
Oleg Nenashev resolved JENKINS-9451 as Incomplete Connection reset - windows slave exits from time to time Not enough info to analyze the issue. There're plenty of changes in the communication layer, hence the issue needs to be reproduced on newer versions Change By: Oleg Nenashev (26/May/14 8:46 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23186) Got conflicting probe from ourselves warning message on Jenkins startup
Laurent TOURREAU created JENKINS-23186 Got conflicting probe from ourselves warning message on Jenkins startup Issue Type: Bug Assignee: Unassigned Components: core Created: 26/May/14 8:50 AM Description: WARNING: Got conflicting probe from ourselves incoming: Service@562665732 type: TYPE_SRV index 33, class: CLASS_IN index 1, name: Jenkins (9)._http._tcp.local. ttl: 3598/3599 server: server.local.:8050 local : Service@1352459983 type: TYPE_SRV index 33, class: CLASS_IN index 1-unique, name: Jenkins (9)._http._tcp.local. ttl: 3599/3600 server: server.local.:8080 Project: Jenkins Priority: Major Reporter: Laurent TOURREAU This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23187) Set an environment variable listing all installed plugins
Sebastian Schuberth created JENKINS-23187 Set an environment variable listing all installed plugins Issue Type: New Feature Assignee: Unassigned Components: core Created: 26/May/14 8:51 AM Description: It would be nice to have a simple and generic way for build steps to find out what plugins are installed. For example, shell build steps could enable ANSI color output for the tools they call if the ansicolor plugin 1 was installed, or they could disable timing in the tools they call if the timestamper plugin 2 was installed. A simple and generic way to allow for this would be to add a "JENKINS_PLUGINS" variable to the list at 3, set to a whitespace separated list of plugin IDs for all installed plugins. A build step could then check that environment variable for a plugin ID and take actions accordingly. 1 https://wiki.jenkins-ci.org/display/JENKINS/AnsiColor+Plugin 2 https://wiki.jenkins-ci.org/display/JENKINS/Timestamper 3 https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-JenkinsSetEnvironmentVariables Project: Jenkins Priority: Minor Reporter: Sebastian Schuberth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-9598) Bundle Git plugin, or overhaul bundled plugins or setup experience
Oleg Nenashev commented on JENKINS-9598 Bundle Git plugin, or overhaul bundled plugins or setup experience I suppose that several "bundle plugins" would be enough (with a separate page on the update center?). Any plugin could just reference other plugins, but it also could provide setup dialogs or initialize the configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [dumpinfo-buildwrapper] (JENKINS-23187) Set an environment variable listing all installed plugins
Oleg Nenashev commented on JENKINS-23187 Set an environment variable listing all installed plugins This feature should be implemented in a plugin, no need to keep it withing the core. I propose to take a look on http://wiki.hudson-ci.org/display/HUDSON/DumpInfo+BuildWrapper+Plugin I suppose this plugin could be improved for your case This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [dumpinfo-buildwrapper] (JENKINS-23187) Set an environment variable listing all installed plugins
Oleg Nenashev edited a comment on JENKINS-23187 Set an environment variable listing all installed plugins This feature should be implemented in a plugin, no need to keep it withing the core. I propose to take a look on http://wiki.hudson-ci.org/display/HUDSON/DumpInfo+BuildWrapper+Plugin This plugin could be improved for your case This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [dumpinfo-buildwrapper] (JENKINS-23187) Set an environment variable listing all installed plugins
Oleg Nenashev updated JENKINS-23187 Set an environment variable listing all installed plugins Change By: Oleg Nenashev (26/May/14 8:55 AM) Component/s: dumpinfo-buildwrapper Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-parameter] (JENKINS-23188) Tag List Empty
Peter Siegel created JENKINS-23188 Tag List Empty Issue Type: Bug Affects Versions: current Assignee: Niklaus Giger Attachments: git1.PNG, git2.png, git3.PNG Components: git-parameter Created: 26/May/14 8:59 AM Description: I have a git repository containing serval tags. I built my git job in jenkins. Then I added the git parameter plugin for tags. Environment: Jenkins 1.564 Windows Server 2012 Project: Jenkins Priority: Major Reporter: Peter Siegel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [mail-watcher] (JENKINS-23174) Links for jobs within folders are invalid
SCM/JIRA link daemon resolved JENKINS-23174 as Fixed Links for jobs within folders are invalid Change By: SCM/JIRA link daemon (26/May/14 8:58 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [mail-watcher] (JENKINS-23174) Links for jobs within folders are invalid
SCM/JIRA link daemon commented on JENKINS-23174 Links for jobs within folders are invalid Code changed in jenkins User: Oliver Gondža Path: .gitignore src/main/java/org/jenkinsci/plugins/mailwatcher/WatcherItemListener.java http://jenkins-ci.org/commit/mail-watcher-plugin/1d9ae5c8c8dcce3c316cecfb1d4c326a0ae74d85 Log: Merge pull request #1 from stephenc/jenkins-23174 FIXED JENKINS-23174 Links for jobs within folders are invalid This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [mail-watcher] (JENKINS-23174) Links for jobs within folders are invalid
SCM/JIRA link daemon commented on JENKINS-23174 Links for jobs within folders are invalid Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/mailwatcher/WatcherItemListener.java http://jenkins-ci.org/commit/mail-watcher-plugin/59e9ebad7bc7d2a8816fed96dd5d9fade1ec0881 Log: FIXED JENKINS-23174 Links for jobs within folders are invalid This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [dumpinfo-buildwrapper] (JENKINS-23187) Set an environment variable listing all installed plugins
Sebastian Schuberth commented on JENKINS-23187 Set an environment variable listing all installed plugins To me, the need to install a plugin in order to list all plugins seems odd. This is a lightweight feature, and other variables are also set in core. Moreover, the DumpInfo plugin (Jenkins version is at 1) seems to be be rather unmaintained with the last release from Jan 30, 2011. 1 https://wiki.jenkins-ci.org/display/JENKINS/DumpInfo+BuildWrapper+Plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-21098) VM crash with no information in jenkins log
Oleg Nenashev resolved JENKINS-21098 as Cannot Reproduce VM crash with no information in jenkins log Java 1.6u24 is outdated. The issue should be reproduced on newer ones. Change By: Oleg Nenashev (26/May/14 9:02 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-21089) archiving artefacts from beaglebone fails
Oleg Nenashev commented on JENKINS-21089 archiving artefacts from beaglebone fails Could you provide a thread dump for Jenkins master? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-21097) Add line breaking for columns LastSuccessfulBuild, LastFailedBuild, etc
Oleg Nenashev commented on JENKINS-21097 Add line breaking for columns LastSuccessfulBuild, LastFailedBuild, etc Have you tried https://wiki.jenkins-ci.org/display/JENKINS/Compact+Columns ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [dumpinfo-buildwrapper] (JENKINS-23187) Set an environment variable listing all installed plugins
Oleg Nenashev edited a comment on JENKINS-23187 Set an environment variable listing all installed plugins The plugin approach is much more preferable, because... The features in plugins do not depend from the core development cycle (which is very unflexible) Users with old core versions will be able to use it Jenkins does not spam user installations by additional wrappers they don't need ... If the proposed plugin does not suit you, please feel free to find another one or request the creation of a new plugin. Any other contributions like the feature implementation will be appreciated as well This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [dumpinfo-buildwrapper] (JENKINS-23187) Set an environment variable listing all installed plugins
Oleg Nenashev commented on JENKINS-23187 Set an environment variable listing all installed plugins The plugin approach is much more preferable, because... The features in plugins do not depend from the core development cycle (which is very unflexible) Users with old core versions will be able to use it Jenkins does not spam user installations by additional wrappers they don't need ... If the proposed plugin does not suit you, please feel free to find another one or request the creation of a new plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-21884) Project name with apostrophe(s) fails on delete due to JS syntax error
Oleg Nenashev commented on JENKINS-21884 Project name with apostrophe(s) fails on delete due to JS syntax error It's much easier to prohibit such cases than to completely fix them Probably, the default item validation strategy should be changed for new installations This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [gerrit-trigger] (JENKINS-23189) REST related configuration is lost when copy server
rin_ne created JENKINS-23189 REST related configuration is lost when copy server Issue Type: Bug Affects Versions: current Assignee: rsandell Components: gerrit-trigger Created: 26/May/14 9:23 AM Description: I found there is no REST related arguments in copy constructor of Config class. it might be lost when create new server by copying other server. Environment: Static analysis in HEAD Project: Jenkins Priority: Major Reporter: rin_ne This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-parameter] (JENKINS-23188) Tag List Empty
ngiger commented on JENKINS-23188 Tag List Empty My use case is that my Jenkins builds create tags like "J-projectbuildnumber" and then I use as tag-filter "J", but using "" should work (just tested on my project). But maybe the explanation is not correct, as I did not consider the case of adding the git-parameter plug-in to an existing jenkins project. Did you build once your project after adding the git parameter plugin? If not please build it once (it will use the default) and check whether your tags get listed now. If they do, I have to change the explanation, else it might be helpful if you could grep your jenkins log to check for any error and / or log entries like May 26, 2014 11:24:25 AM net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition generateContents INFO: generateContents contenttype PT_TAG RemoteConfig https://github.com/elexis/elexis-3-base/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-21317) Build Time Trend doesn't load, always says Computation in Progress
Michal Hradil commented on JENKINS-21317 Build Time Trend doesnt load, always says Computation in Progress I have the same issue. This regression first appeared in build 1.544, so I assume it is caused by the change "Avoid eagerly loading all builds when displaying lists of them (Build History and Build Time Trend UIs)." - JENKINS-20892 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-21317) Build Time Trend doesn't load, always says Computation in Progress
Michal Hradil edited a comment on JENKINS-21317 Build Time Trend doesnt load, always says Computation in Progress I have the same issue. This regression first appeared in build 1.544, so I assume it is caused by the change "Avoid eagerly loading all builds when displaying lists of them (Build History and Build Time Trend UIs)." - JENKINS-20892. Honestly, if this is the case, I would vote to remove that fixes, as it is now worst, than it was before. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-21317) Build Time Trend doesn't load, always says Computation in Progress
Michal Hradil updated JENKINS-21317 Build Time Trend doesnt load, always says Computation in Progress Change By: Michal Hradil (26/May/14 9:49 AM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-21317) Build Time Trend doesn't load, always says Computation in Progress
Michal Hradil edited a comment on JENKINS-21317 Build Time Trend doesnt load, always says Computation in Progress I have the same issue. I can confirm, that this regression first appeared in build 1.544, so I assume it is caused by the change "Avoid eagerly loading all builds when displaying lists of them (Build History and Build Time Trend UIs)." - JENKINS-20892. Honestly, if this is the case, I would vote to remove that fix, as it is now worst, than it was before. I have increased the Priority to Major since this view is fundamental in the multi-node environment. We cannot track the time used for build on specific nodes, or even see which build run on which node. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-22641) Jenkins no longer kills running processes after job fails
Steven Christou updated JENKINS-22641 Jenkins no longer kills running processes after job fails Change By: Steven Christou (26/May/14 9:55 AM) Assignee: StevenChristou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [gerrit-trigger] (JENKINS-23189) REST related configuration is lost when copy server
rin_ne started work on JENKINS-23189 REST related configuration is lost when copy server Change By: rin_ne (26/May/14 10:04 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [gerrit-trigger] (JENKINS-23189) REST related configuration is lost when copy server
rin_ne updated JENKINS-23189 REST related configuration is lost when copy server Change By: rin_ne (26/May/14 10:04 AM) Assignee: rsandell rin_ne This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [gerrit-trigger] (JENKINS-23189) REST related configuration is lost when copy server
rin_ne stopped work on JENKINS-23189 REST related configuration is lost when copy server Change By: rin_ne (26/May/14 10:12 AM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [gerrit-trigger] (JENKINS-23189) REST related configuration is lost when copy server
rin_ne commented on JENKINS-23189 REST related configuration is lost when copy server PR: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/155 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [cppcheck] (JENKINS-23190) CppCheck plugin: Optionally publish CppCheck report xml filename in CppCheck results
Mavi K created JENKINS-23190 CppCheck plugin: Optionally publish CppCheck report xml filename in CppCheck results Issue Type: New Feature Assignee: Gregory Boissinot Components: cppcheck Created: 26/May/14 12:07 PM Description: The CppCheck plugin supports multiple CppCheck report xml files. However, in the Cppcheck results, the report xml file in which the issue appears isn't stated. This can make it difficult to map issues from the Cppcheck results to the target in which the issue is present if, for example, each report xml file corresponds to a different target and targets share source code. If the CppCheck plugin had a configuration option to enable outputting the Cppcheck report xml file name for each issue in the CppCheck report table, this would alleviate the issue. Project: Jenkins Priority: Minor Reporter: Mavi K This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [gerrit-trigger] (JENKINS-23189) REST related configuration is lost when copy server
rin_ne edited a comment on JENKINS-23189 REST related configuration is lost when copy server PR: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/155 Sorry, this PR is abandoned once. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [columnsplugin] (JENKINS-12039) As a jenkins user, I would like to see the latest release number of a job in the Jenkins jobs list
Oleg Nenashev updated JENKINS-12039 As a jenkins user, I would like to see the latest release number of a job in the Jenkins jobs list Seems to be a good case for the Columns Plugin (or 4 release). New plugins are not required Change By: Oleg Nenashev (26/May/14 12:16 PM) Component/s: columnsplugin Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [acceptance-test-harness] (JENKINS-23113) It shall be possible to use a http proxy with the acceptance test harness
Marco Miller commented on JENKINS-23113 It shall be possible to use a http proxy with the acceptance test harness Test cases I used (GerritTrigger, ActiveDirectory) were successful with the fix for this issue, in both mvn and ide. https://github.com/jenkinsci/acceptance-test-harness/pull/2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [mail-watcher] (JENKINS-20535) Subject for bring a node back online is misleading
Oliver Gondža commented on JENKINS-20535 Subject for bring a node back online is misleading Fixed in 1.6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [mail-watcher] (JENKINS-23174) Links for jobs within folders are invalid
Oliver Gondža commented on JENKINS-23174 Links for jobs within folders are invalid Fixed in 1.6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [downstream-ext] (JENKINS-23191) NPE in downstream jobs
Donato Tagliabue created JENKINS-23191 NPE in downstream jobs Issue Type: Bug Assignee: kutzi Attachments: bug_jenkins_downstreams_jobs.png, bug_jenkins_downstreams_jobs_2.png Components: downstream-ext Created: 26/May/14 12:43 PM Description: Created three jobs: job A, job B, job C. Set job B config to be triggered after job A and to trigger job C. In this case, radio button in the section "build after other projects are built" cannot be saved (even if you save and reopen the configuration page). When job A is built, a NullPointerException is thrown and job B is not started (see attachments). If you chain only job B to job A, it works. Environment: Jenkins 1.563 RHEL6 Project: Jenkins Labels: nullpointer downstream upstream Priority: Major Reporter: Donato Tagliabue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23148) Accessibility problem when editing shell script in the configuration of a job
guillaume gourdier updated JENKINS-23148 Accessibility problem when editing shell script in the configuration of a job Change By: guillaume gourdier (26/May/14 12:49 PM) Environment: Linux2.6.18X86_64/JDK1.6(OpenJDK1.6.0_17X64) ,jenkinswardistribution Component/s: core Component/s: configure-job-column This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [acceptance-test-harness] (JENKINS-23113) It shall be possible to use a http proxy with the acceptance test harness
Scott Hebert started work on JENKINS-23113 It shall be possible to use a http proxy with the acceptance test harness Change By: Scott Hebert (26/May/14 12:58 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-14752) SCM Polling / Max # of concurrent polling = 1 hangs github polling
Sascha Vogt commented on JENKINS-14752 SCM Polling / Max # of concurrent polling = 1 hangs github polling Well, it doesn't matter if you have 1 or 10 concurrent. Sometimes the git command just hangs. Having 10 concurrent pollings just means it needs to happen 10 times before you're completely blocked out. Even if you don't restrict, you will at one point have hundreds or thousands of hanging pollings. I think the right thing here would be to configure a timeout and if that is reached kill the process. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [gerrit-trigger] (JENKINS-23165) Config.gerritAuthKeyFilePassword stored in plaintext
rin_ne commented on JENKINS-23165 Config.gerritAuthKeyFilePassword stored in plaintext Secret.fromString() raises NPE when given parameter is null or empty string. It is inconvenient since SSH password accepts empty... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [gerrit-trigger] (JENKINS-23165) Config.gerritAuthKeyFilePassword stored in plaintext
rin_ne edited a comment on JENKINS-23165 Config.gerritAuthKeyFilePassword stored in plaintext Secret.fromString() raises NPE when given parameter is null or empty string. It is inconvenient since SSH password accepts empty. I don't know whether it is expected behavior or not... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-client] (JENKINS-21074) Git Client plugin fails to install on fresh Jenkins installation
Karthikeyan Annamalai commented on JENKINS-21074 Git Client plugin fails to install on fresh Jenkins installation Facing the same issue in following configuration as well. OS : Windows 7 JDK: 1.7.0_55 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-9666) Test mail should be sent in same language as real mails.
Daniel Beck resolved JENKINS-9666 as Cannot Reproduce Test mail should be sent in same language as real mails. Cannot reproduce on 1.532.3: Jenkins is on an English server, and I set browser locale to French. Then I triggered the test email: It's in English. Change By: Daniel Beck (26/May/14 2:35 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-9057) Hability to disable slaves
ingmartinlopez commented on JENKINS-9057 Hability to disable slaves Ok, thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-22710) Broken Debian upgrades because postinst doesn't check for present group/user
Brendan Holmes commented on JENKINS-22710 Broken Debian upgrades because postinst doesnt check for present group/user Getting this with 1.564 in Lubuntu 14.04 LTS. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-12313) Duplicate plugin options in project config.
Rob Petti edited a comment on JENKINS-12313 Duplicate plugin options in project config. Yes, I'm still affected. The contents of the directory looks perfectly normal, no duplicate files or folders... I suspect this is caused by the way Jenkins handles plugin registration, and how it used to handle it in the past. Nowadays, extensionpoints take care of this sort of thing, but back in the day you used to have to register by extending the Plugin class and adding the necessary classes to the appropriate lists using the start() function. So running old plugins on newer versions of Jenkins would exhibit this behaviour, and it explains why the issue goes away when certain plugins get updated. Ideally these lists (such as BuildStep.PUBLISHERS) should be unique lists, and not allow these duplicates to be added. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-12313) Duplicate plugin options in project config.
Rob Petti commented on JENKINS-12313 Duplicate plugin options in project config. Yes, I'm still affected. The contents of the directory looks perfectly normal, no duplicate files or folders... I suspect this is caused by the way Jenkins handles plugin registration, and how it used to handle it in the past. Nowadays, extensionpoints take care of this sort of thing, but back in the day you used to have to register by extending the Plugin class and adding the necessary classes to the appropriate lists using the start() function. So running old plugins on newer versions of Jenkins would exhibit this behaviour, and it explains why the issue goes away when certain plugins get updated. Ideally these lists (such as BuildStep.PUBLISHERS) should be unique lists, and now allow these duplicates to be added. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-21810) Additional options on slave disconnection
Jason Swager commented on JENKINS-21810 Additional options on slave disconnection v1.1.19 and v1.1.20 both have the Revert and Reset/Restart, which should meet this feature request. This issue will be closed on June 1st if no further information is added. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-21466) Impossible to connect to the VSphere Cloud Anymore
Jason Swager commented on JENKINS-21466 Impossible to connect to the VSphere Cloud Anymore This is some VERY good information. I greatly appreciate the work that you did to hunt down the culprit of this problem. I'll check with the vijava project and see if a change can be pushed to them - or requested. Again, thanks for the help on getting to the root cause of this problem! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23193) UI blocked frequently
Saulo Alvarado Mateos updated JENKINS-23193 UI blocked frequently Change By: Saulo Alvarado Mateos (26/May/14 3:12 PM) Description: InFebruaryweupdateourJenkinstoversion1.540withautomaticupdatetoolandwereunabletostartagain.Manuallywesteppedbacktoversion1.539weholdsince.Howeversinceweareusingversion1.539wehaveseriousproblemsofblockingofthewebuserinterface.Initiallytheuserinterfacestopstorespondeventuallyonceadayoreverycoupleofdays,andlastedabout30or40minutes;butinrecentweeksthefrequencywithwhichthewebinterfacestopsrespondinghasincreaseddramatically;andthewaitingtimehasbecomeexcessive,exceedingthehourorhourandahalfofwaitingtime,andrequiringinmostcasesforcetheshutdownandrestarttheservicebyhand.ThissituationseemsawkwardtoholdupbecausethenumberofprojectsgrowsweeklyandJenkinshavetomanageit.AndthenumberofdevelopersusingJenkins - ( andwebrequests - ) alsogrows.ThesymptomisthatwhenweaskedanyURLtoJenkinsserver,thebrowserwaitsforeverforthereply.Answerthatneverreceives.Curiously,therestoftheserviceisstillrunning.LookingatthelogoutputinrealtimestillappearactivitystartandcompletionoftaskswhenchangesaredetectedintheSubversionrepository.LookingforsimilarissuesrecordedneartheapproximatedatethatweupdateJenkins,Ifound[https://issues.jenkins-ci.org/browse/JENKINS-21487]and[https://issues.jenkins-ci.org/browse/JENKINS-21487].However,inourcasetheservicecontinuestorunscheduledtasks.Justdonotanswerthewebinterface.Anyideawhatwecando?Ialsouploadadumpofthethreadsthatwererunningthismorningafterwaitinghalfanhourforthewebinterfacetorespond.FinallywehadtomanuallystoptheWindowsserviceandrunitagain. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23193) UI blocked frequently
Saulo Alvarado Mateos created JENKINS-23193 UI blocked frequently Issue Type: Bug Assignee: Unassigned Attachments: threaddump-1401097350129.tdump Components: core Created: 26/May/14 3:12 PM Description: In February we update our Jenkins to version 1.540 with automatic update tool and were unable to start again. Manually we stepped back to version 1.539 we hold since. However since we are using version 1.539 we have serious problems of blocking of the web user interface. Initially the user interface stops to respond eventually once a day or every couple of days, and lasted about 30 or 40 minutes; but in recent weeks the frequency with which the web interface stops responding has increased dramatically; and the waiting time has become excessive, exceeding the hour or hour and a half of waiting time, and requiring in most cases force the shutdown and restart the service by hand. This situation seems awkward to hold up because the number of projects grows weekly and Jenkins have to manage it. And the number of developers using Jenkins and web requests also grows. The symptom is that when we asked any URL to Jenkins server, the browser waits forever for the reply. Answer that never receives. Curiously, the rest of the service is still running. Looking at the log output in real time still appear activity start and completion of tasks when changes are detected in the Subversion repository. Looking for similar issues recorded near the approximate date that we update Jenkins, I found https://issues.jenkins-ci.org/browse/JENKINS-21487 and https://issues.jenkins-ci.org/ browse/JENKINS-21487. However, in our case the service continues to run scheduled tasks. Just do not answer the web interface. Any idea what we can do? I also upload a dump of the threads that were running this morning after waiting half an hour for the web interface to respond. Finally we had to manually stop the Windows service and run it again. Environment: Windows Server 2008 R2 Project: Jenkins Priority: Blocker Reporter: Saulo Alvarado Mateos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [gitlab-merge-request-jenkins] (JENKINS-23194) NoSuchMethod when configuring mergeRequest Builder
Udo Waechter created JENKINS-23194 NoSuchMethod when configuring mergeRequest Builder Issue Type: Bug Assignee: Unassigned Components: gitlab-merge-request-jenkins Created: 26/May/14 3:53 PM Description: When I try to configure the Gitlab Merge Request builder, I get the error below. I tried the following crontab lines: H/5 * * * * */5 * * * * 5 * * * * javax.servlet.ServletException: java.lang.NoSuchMethodError: hudson.triggers.TimerTrigger$DescriptorImpl.doCheckSpec(Ljava/lang/String;)Lhudson/util/FormValidation; at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1221) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.marvelution.jenkins.plugins.jira.filter.OAuthServletFilter.doFilter(OAuthServletFilter.java:70) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.marvelution.jenkins.plugins.jira.filter.StreamsServletFilter.doFilter(StreamsServletFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.marvelution.jenkins.plugins.jira.filter.ApplinksServletFilter.doFilter(ApplinksServletFilter.java:91) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.marvelution.jenkins.plugins.jira.oauth.OAuthFilter.doFilter(OAuthFilter.java:77) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at
[JIRA] [rebuild] (JENKINS-23195) Rebuild Plugin with textarea
Tony WRZOS created JENKINS-23195 Rebuild Plugin with textarea Issue Type: Bug Assignee: ragesh_nair Components: rebuild Created: 26/May/14 3:53 PM Description: When the job is rebuilt thanks to the rebuild plugin and when a parameter comes from a textarea (multiline), each CR is turned to a simple space. This can affect Shell scripts intended to process multiline parameters. Project: Jenkins Priority: Minor Reporter: Tony WRZOS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [mask-passwords] (JENKINS-14687) Password is exposed through browser option view page source
Daniel Beck reopened JENKINS-14687 Password is exposed through browser option view page source Fix does not apply to global Jenkins config password form. Change By: Daniel Beck (26/May/14 3:55 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23186) Got conflicting probe from ourselves warning message on Jenkins startup
Oleg Nenashev resolved JENKINS-23186 as Not A Defect Got conflicting probe from ourselves warning message on Jenkins startup Seems you have misconfigured the network loopback. Useful links: http://www.spigotmc.org/threads/got-conflicting-probe-from-ourselves.5390/ http://stackoverflow.com/questions/2095/which-ipv6-address-should-i-use-for-bonjour Code: http://jmdns.sourceforge.net/clover/javax/jmdns/impl/DNSRecord.html Change By: Oleg Nenashev (26/May/14 4:37 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [slave-setup] (JENKINS-15582) Slave Setup Plugin fails with an exception
Oleg Nenashev updated JENKINS-15582 Slave Setup Plugin fails with an exception Fixed the component Change By: Oleg Nenashev (26/May/14 4:47 PM) Assignee: KohsukeKawaguchi Component/s: slave-setup Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-15467) Build History Extension Point
Oleg Nenashev updated JENKINS-15467 Build History Extension Point Fixed the component Change By: Oleg Nenashev (26/May/14 4:48 PM) Component/s: core Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [build-user-vars] (JENKINS-14490) Build User Variables should be accessible from Post-Build Actions
Oleg Nenashev updated JENKINS-14490 Build User Variables should be accessible from Post-Build Actions Fixed the component Change By: Oleg Nenashev (26/May/14 4:52 PM) Component/s: build-user-vars Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [eggplant] (JENKINS-14810) Multiple eggplant plugins in the same project cause incorrect log interpretation
Oleg Nenashev updated JENKINS-14810 Multiple eggplant plugins in the same project cause incorrect log interpretation Fixed the component Change By: Oleg Nenashev (26/May/14 4:51 PM) Component/s: eggplant Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ec2] (JENKINS-17892) Duplicate instances (orphaned) on ec2
Oleg Nenashev updated JENKINS-17892 Duplicate instances (orphaned) on ec2 Change By: Oleg Nenashev (26/May/14 4:53 PM) Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [summary_report] (JENKINS-17572) plugin fails to create tabs in some cases
Oleg Nenashev updated JENKINS-17572 plugin fails to create tabs in some cases Fixed the component Change By: Oleg Nenashev (26/May/14 4:54 PM) Component/s: summary_report Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [mantis] (JENKINS-19748) No Mantis Site found in Matrix config job
Oleg Nenashev updated JENKINS-19748 No Mantis Site found in Matrix config job Change By: Oleg Nenashev (26/May/14 4:57 PM) Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [analysis-core] (JENKINS-17062) TrendGraph Returns 500 NoClassDefFoundError org/joda/time/LocalDate
Oleg Nenashev updated JENKINS-17062 TrendGraph Returns 500 NoClassDefFoundError org/joda/time/LocalDate Fixed components Change By: Oleg Nenashev (26/May/14 4:56 PM) Assignee: UlliHafner Component/s: analysis-core Component/s: warnings Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ldap] (JENKINS-8152) LDAP config error
Oleg Nenashev updated JENKINS-8152 LDAP config error Fixed the component Change By: Oleg Nenashev (26/May/14 4:59 PM) Component/s: ldap Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-7192) Use multiple SCM sources
Oleg Nenashev resolved JENKINS-7192 as Fixed Use multiple SCM sources Multiple SCMs Plugin resolves the case Change By: Oleg Nenashev (26/May/14 5:01 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-6520) Case insensitivity option for authorization
Oleg Nenashev resolved JENKINS-6520 as Fixed Case insensitivity option for authorization Change By: Oleg Nenashev (26/May/14 5:02 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-4853) Expand variables in E-mail Notification Recipients
Oleg Nenashev resolved JENKINS-4853 as Fixed Expand variables in E-mail Notification Recipients Use Mail-Ext plugin for such case Change By: Oleg Nenashev (26/May/14 5:04 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-3921) Node provisioning fails when only tied nodes available and untied jobs are waiting to run
Oleg Nenashev resolved JENKINS-3921 as Cannot Reproduce Node provisioning fails when only tied nodes available and untied jobs are waiting to run The issue seems to work well on test installations Change By: Oleg Nenashev (26/May/14 5:06 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [r] (JENKINS-23196) Add script repositories to R plug-in
Bruno P. Kinoshita updated JENKINS-23196 Add script repositories to R plug-in Change By: Bruno P. Kinoshita (26/May/14 5:08 PM) Description: From:https://groups.google.com/forum/#!topic/biouno-developers/RK805kzCPf4 AddabilitytoretrieveremotescriptsfromwithinJenkins.TheScriptlerplug-inhasasimpleandintuitiveinterface.Wecanuseitasbasis.Offthetopofmyhead,Ithinkwecouldsupportthefollowingscriptrepositories:-GitHubrepository-HTTPwebsiteProbablyitwouldhaveacommoninterface,andusefileextensionstofilter,oroptionallyaJSONfile. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [r] (JENKINS-23196) Add script repositories to R plug-in
Bruno P. Kinoshita created JENKINS-23196 Add script repositories to R plug-in Issue Type: New Feature Assignee: Bruno P. Kinoshita Components: r Created: 26/May/14 5:07 PM Description: Add ability to retrieve remote scripts from within Jenkins. The Scriptler plug-in has a simple and intuitive interface. We can use it as basis. Off the top of my head, I think we could support the following script repositories: GitHub repository HTTP website Probably it would have a common interface, and use file extensions to filter, or optionally a JSON file. Project: Jenkins Priority: Minor Reporter: Bruno P. Kinoshita This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23191) NPE in downstream jobs
kutzi updated JENKINS-23191 NPE in downstream jobs This is in the normal downstream configuration of Jenkins and not in the Downstream-Ext plugin. Therefore changing component to core Change By: kutzi (26/May/14 5:31 PM) Component/s: core Component/s: downstream-ext This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-7192) Use multiple SCM sources
Daniel Beck commented on JENKINS-7192 Use multiple SCM sources Oleg: Multiple SCM Plugin looks a bit like a hack. An overhaul of the core SCM api (including real support for multi-module checkouts in repo browsers) might be a good idea. That being said, I've not used it in production how well does it really work? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-7192) Use multiple SCM sources
Oleg Nenashev commented on JENKINS-7192 Use multiple SCM sources It works... eventually Actually, the behavior depends on the plugin, because the current version does not support the "newInstance" method (see https://github.com/jenkinsci/multiple-scms-plugin/pull/4). Other basic checkout polling methods work well, but I'm almost sure that there're many bugs for more complex cases (like workspace cleanup hooks or various ItemListeners). In general, the plugin stills a hack. I confirm that the plugin works for Subversion, Perforce (fixed in the latest version), FileSCM and Git (for primitive configurations). BTW, the plugin requires the accurate configuration. Otherwise, there's a high risk of workspace collisions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [nodeofflinenotification] (JENKINS-23197) When entering offline reason for a node, it should be prefixed with a date+time stamp
Yaniv Kaul created JENKINS-23197 When entering offline reason for a node, it should be prefixed with a date+time stamp Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: nodeofflinenotification Created: 26/May/14 7:50 PM Description: When a user enters a comment on why he/she moved a node to offline, it'd be great if it'll be automatically prefixed with a data+time stamp: 'Took node offline for investigation of bug 1234' would be: '26-May-14 19:00 - Took node offline for investigation of bug 1234' (Of course, username is also welcome!) Project: Jenkins Labels: offline Priority: Minor Reporter: Yaniv Kaul This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [build-pipeline] (JENKINS-23151) Execute shell window not saved properly
Donato Tagliabue commented on JENKINS-23151 Execute shell window not saved properly I have the same problem (with Jenkins 1.563, on RHEL6, browser Chrome), not present in older releases (e.g. 1.540). If you click on "apply" in the configuration page, then on "save" it seems to work always, instead, by using directly the "save" button, textarea contents sometimes is lost. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23151) Execute shell build step text not saved properly
Daniel Beck
updated JENKINS-23151
Execute shell build step text not saved properly
Change By:
Daniel Beck
(26/May/14 9:14 PM)
Summary:
Executeshell
window
buildsteptext
notsavedproperly
Affects Version/s:
current
Description:
WhenIcreateasimpleprojectandaddExecuteshelltask,aftersave,thetaskcontentsareempty.config.xmlontheserverisemptytoo:{code}hudson.tasks.Shellcommand//hudson.tasks.Shell{code}Wheneditingtheconfigasecondtime,thecontentsaresavedproperly.Eachconsecutiveaddofshelltaskrequiresasecondedit.Whenusinginheritanceplugin,thereisnowaytoworkaroundthebug,sinceeacheditcreatesnewrevision,andallshelltasksareempty.Itestediton1.563and
1564
1.564
Component/s:
core
Component/s:
build-pipeline
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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-23151) Execute shell build step text not saved properly
Daniel Beck assigned JENKINS-23151 to Daniel Beck Execute shell build step text not saved properly Change By: Daniel Beck (26/May/14 9:15 PM) Assignee: DanielBeck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23151) Execute shell build step text not saved properly
Daniel Beck commented on JENKINS-23151 Execute shell build step text not saved properly Introduced in 1.561. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-21459) Jenkins don't run jobs from queue (there are available executors)
Francois Pilote commented on JENKINS-21459 Jenkins dont run jobs from queue (there are available executors) I was able to reproduce this bug on jenkins 1.556. The problem was one of my project had a "lastSuccessfulBuild" file that was corrupted from a computer reset. (Windows Server 2008 R2) I manually recreated the file with a valid number and saved it. This modification got the queue and the builds going. The exception that caught my attention was the following : Caught exception evaluating: it.lastSuccessfulBuild.ARTIFACTS in /job/Dev_OnCommit/. Reason: java.lang.reflect.InvocationTargetException It was this project that the file was corrupted. I attached the faulty file even though it is probably not interesting. (only 3 bytes) FYI, we have a big jenkins setup (200+ jobs, 12+slaves (mac, pc, win, unix...)) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-21459) Jenkins don't run jobs from queue (there are available executors)
Francois Pilote updated JENKINS-21459 Jenkins dont run jobs from queue (there are available executors) Change By: Francois Pilote (26/May/14 9:26 PM) Attachment: lastSuccessfulBuild__broken This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-21459) Jenkins don't run jobs from queue (there are available executors)
Francois Pilote edited a comment on JENKINS-21459 Jenkins dont run jobs from queue (there are available executors) I was able to reproduce this bug on jenkins 1.556. The problem was one of my project had a "lastSuccessfulBuild" file that was corrupted from a computer reset. (Windows Server 2008 R2) I manually recreated the file with a valid number and saved it. This modification got the queue and the builds going. The exception that caught my attention was the following : Caught exception evaluating: it.lastSuccessfulBuild.ARTIFACTS in /job/Dev_OnCommit/. Reason: java.lang.reflect.InvocationTargetException It was this project that the file was corrupted. I attached the faulty file even though it is probably not interesting. (only 3 bytes) You can probably reproduce the bug with this file. FYI, we have a big jenkins setup (200+ jobs, 12+slaves (mac, pc, win, unix...)) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-9597) Autocomplete box in text boxes is not selectable using the enter key
Ulli Hafner commented on JENKINS-9597 Autocomplete box in text boxes is not selectable using the enter key Can also verify that this still does not work for textboxes using Firefox auto complete feature. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
