[JIRA] (JENKINS-14233) NPE when using the [Choice] option of the [This build is parameterized] functionality
Vassilena Treneva assigned JENKINS-14233 to Unassigned NPE when using the [Choice] option of the [This build is parameterized] functionality I am moving the bug as advised by domi Change By: Vassilena Treneva (29/Jun/12 5:59 AM) Assignee: domi 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
[JIRA] (JENKINS-14233) NPE when using the [Choice] option of the [This build is parameterized] functionality
Vassilena Treneva updated JENKINS-14233 NPE when using the [Choice] option of the [This build is parameterized] functionality Change By: Vassilena Treneva (29/Jun/12 5:59 AM) Component/s: core Component/s: nodelabelparameter 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
[JIRA] (JENKINS-14233) NPE when using the [Choice] option of the [This build is parameterized] functionality
Vassilena Treneva updated JENKINS-14233 NPE when using the [Choice] option of the [This build is parameterized] functionality Attaching the actual configuration and a screenshot with the provided parameters before I hit Save and get the exception. Let me know if further info is needed. Change By: Vassilena Treneva (29/Jun/12 6:01 AM) Attachment: BeforeSave.jpg Attachment: config.xml 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
[JIRA] (JENKINS-14253) Discard Old Builds does not remove builds from Matrix-Axes
Matthias Kraft created JENKINS-14253 Discard Old Builds does not remove builds from Matrix-Axes Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 29/Jun/12 7:46 AM Description: We are experiencing a strange behavior of our Matrix projects. Say you have a Free-Style project "Foo" preparing sources, then triggering a Matrix project "Bar" which builds from these sources on various slave machines. Both projects are configured to only keep the latest 10 builds. Looking on the project pages only the latest 10 builds are visible. Same in the project directories (e.g. jobs/Bar/builds). But when you look into the project pages from the slaves, as well as into the sub directories (e.g. jobs/Bar/configurations/axis-label/someslave/builds), all builds ever done are still there. This seems to happen only to Matrix projects called by upstream projects. Standalone Matrix projects seem also been cleaned up in their sub directories. As the Foo-project's build are not kept, clicking on an old build's trigger link within Bar's someslave project page only leads to a 404. Environment: SUSE Linux Enterprise Server 11.1 (x86_64); JDK 1.6.0_26; Jenkins 1.447.1 Project: Jenkins Priority: Major Reporter: Matthias Kraft 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
[JIRA] (JENKINS-14254) Possible inconsistent checkouts if using multiple modules and post-commit-hook resp. RevisionParameter
kutzi commented on JENKINS-14254 Possible inconsistent checkouts if using multiple modules and post-commit-hook resp. RevisionParameter Not sure how to fix this, but the description in the wiki should be adapted to remove ?rev=$REV from the example or at least issue a warning that it can lead to problems with multiple modules. Also we could issue a warning in the build log if a job has multiple modules AND more than one of those have SVN changes AND only SOME of them have a revisionparameter specified. For a general solution on how to ensure consistent checkouts, if only some modules have revisionparameter: I think that would be very difficult. 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
[JIRA] (JENKINS-10835) Add support for JaCoCo coverage results
Mickael Istria resolved JENKINS-10835 as Fixed Add support for JaCoCo coverage results @Jose: you should use the jacoco plugin which is already available in version 0.1. See Ognjen's comment for useful links on this topic. Change By: Mickael Istria (29/Jun/12 8:23 AM) Status: Open Resolved Assignee: KohsukeKawaguchi OgnjenBubalo 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
[JIRA] (JENKINS-14135) NPE
Karsten Brandt commented on JENKINS-14135 NPE Hello Carsten, I've repeated my tests with your workspace, but there is also no error occurred. All looks fine and no error message pops up. Please, could you try to remove all files from your workspace (step by step) until this error will not occur any more? Or vice versa, start with an empty workspace (only your result.sc should be there) and then add file by file to your workspace. If you have find the culprit, you can send him to us. So we can improve the robustness of this plugin. In case of non success the failure seems to be in your environment. Then send us detailed information like version of used jenkins server, installed plugins (with version information) and so on. Have you tried this also with sloccount plugin version 1.7? Good luck, Karsten 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
[JIRA] (JENKINS-10835) Add support for JaCoCo coverage results
Mickael Istria commented on JENKINS-10835 Add support for JaCoCo coverage results Link to Jacoco reports plugin: https://wiki.jenkins-ci.org/display/JENKINS/JaCoCo+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
[JIRA] (JENKINS-14013) Create a public instance of Jenkins using OpenShift cloud
Mickael Istria commented on JENKINS-14013 Create a public instance of Jenkins using OpenShift cloud You could also ask for build of Jacoco plugin in nemo.sonarsource.org. This service for OSS projects provides you a Jenkins instance @CloudBees + reports in a Sonar. 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
[JIRA] (JENKINS-14135) NPE
Carsten Otto commented on JENKINS-14135 NPE It works with 1.7. Can you tell me how I can manually test this? I have no idea how to remove files from my workspace after a build and before running the plugin. Some way to test this in my shell would be nice. 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
[JIRA] (JENKINS-14248) DiskUsage dont show values.
vjuranek
commented on JENKINS-14248
DiskUsage dont show values.
Hi,
could you please run following script via Jenkins script console ($JENKINS_URL/script):
jenkins.model.Jenkins.instance.getItem("MONITOR-SERVER").getAction(hudson.plugins.disk_usage.ProjectDiskUsageAction.class).getDiskUsage().getBuildUsage()
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
[JIRA] (JENKINS-13844) Emulate clean checkout by... does not work with 1.7 subversion repositories
Denis Eperonnier commented on JENKINS-13844 Emulate clean checkout by... does not work with 1.7 subversion repositories Same for me using SVN server 1.5, Jenkins 1.472 + SVN 1.42 plugin, SVN WC 1.7 Issue occurs on a WinXP 32bit slave 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
[JIRA] (JENKINS-14135) NPE
Karsten Brandt commented on JENKINS-14135 NPE Copy your sloccount output file into a separate folder and set your workspace accordingly. For example: The new created folder is: /tmp/jenkins_test And the complete path to the sloccount file is: /tmp/jenkins_test/result.sc Set your workspace to: /tmp/jenkins_test Your test job should have no build actions. Only the sloccount output file shall be processed! Therefore, don't forget to set the search pattern for the sloccount file accordingly. Now, you should have a clean test environment... 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
[JIRA] (JENKINS-14135) NPE
Karsten Brandt edited a comment on JENKINS-14135 NPE Copy your sloccount output file into a separate folder and set your workspace accordingly. For example: The new created folder is: /tmp/jenkins_test And the complete path to the sloccount file is: /tmp/jenkins_test/result.sc Set your workspace to: /tmp/jenkins_test Your test job should have no build actions. Only the sloccount output file shall be processed! Therefore, don't forget to set the search pattern for the sloccount file accordingly. The search pattern should be: result.sc Now, you should have a clean test environment... 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
[JIRA] (JENKINS-14135) NPE
Karsten Brandt commented on JENKINS-14135 NPE Hello Carsten, I've an another idea. Has your real jenkins project a long build history? If so, please, create a new jenkins job for tests. So, we can exclude problems caused by older builds from other plugin versions. Regards, Karsten 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
[JIRA] (JENKINS-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
aristedes commented on JENKINS-13835 E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request I found the cause of one of the enormous confusions with this plugin for me. If you have a matrix build, then: on the server (not the slave) at the unguessable path of /jobs/jobname/configurations/axis-foo/bar/axis-foo1/bar1/subversion.credentials you will find the old cached credentials. In all my testing trying to solve the original problems with svnkit upgrade, I changed the user and reset the password. It would have been great if somewhere jenkins would have reported which user it was trying to use. Also, deleting the job from the client, doesn't clear the credentials buried against every axis on the server. Why are they on every axis? 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
[JIRA] (JENKINS-14135) NPE
Carsten Otto commented on JENKINS-14135 NPE Maybe a multithreading problem? I see that you recently introduced a field "report" (that triggers the NPE). Maybe it is necessary to mark this using "volatile"? The effects of the constructor might not yet be visible when invoke() runs. 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
[JIRA] (JENKINS-14234) RuntimeException when using [Label] option in [This build is parameterized]
Vassilena Treneva resolved JENKINS-14234 as Fixed RuntimeException when using [Label] option in [This build is parameterized] Seems that the issue is resolved by the new versions of the two plugs. Thank you Change By: Vassilena Treneva (29/Jun/12 11:31 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
[JIRA] (JENKINS-14135) NPE
Carsten Otto commented on JENKINS-14135 NPE I see that this job only works an master and fails on other nodes. Maybe the issue is that "report" is transient, but you do need serialization for the object that is passed to the node? I have no idea how plugins work, but this makes a bit of sense to me. 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
[JIRA] (JENKINS-10184) wrong timestamps in build timeline
evernat commented on JENKINS-10184 wrong timestamps in build timeline I also reproduce the issue with Jenkins 1.440. In /systeminfo, I have user.timezone = Europe/Paris (UTC+1). In the build history, there is a build at "14:36:22" (in June) but in the timeline, the same build is displayed at "13:36:22" as shown in the tooltip (BAD). And also, in the build history, there is another build at "15:21:25" (in January) and in the timeline, the same build is displayed at "15:21:25" as shown in the tooltip (GOOD). So it seems to be an issue of daylight saving time, and in the same timeline some builds are bad and others are good. In 1, I see that java.util.TimeZone.getDefault().getRawOffset() is used. Perhaps, java.util.TimeZone.getDefault().getOffset(date.getTime()) should be used instead for each date, or the timezone of the dates could be changed on the server before sending the JSON of the timeline data to the client. 1 https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/model/BuildTimelineWidget/control.jelly#L42 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
[JIRA] (JENKINS-14256) buildout builder:cannot download zc.buildout from behind a firewall from pypi.python.org
Karsten Schwarz updated JENKINS-14256 buildout builder:cannot download zc.buildout from behind a firewall from pypi.python.org Change By: Karsten Schwarz (29/Jun/12 12:22 PM) Labels: 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
[JIRA] (JENKINS-14256) buildout builder:cannot download zc.buildout from behind a firewall from pypi.python.org
Karsten Schwarz created JENKINS-14256 buildout builder:cannot download zc.buildout from behind a firewall from pypi.python.org Issue Type: Bug Assignee: Unassigned Components: shiningpanda Created: 29/Jun/12 12:21 PM Description: When using a buildout builder in shiningpanda plugin, one of the steps which is executed is downloading zc.buildout from pypi.python.org. Unfortunately when this is executed from behind a firewall which expects authentification, this does not work (see below) The bootstrap.py script used in setting up the environment seem to provide several parameter (e.g. --download-base) for changing the download server to a local pypi server. Making these available as configuration parameter would help to solve the problem Building in workspace /var/hudson/8282/work/jobs/FrontARENA/workspace workspace $ /bin/ksh -xe /var/tmp/hudson2537037190294754109.sh + echo /var/hudson/8282/work/jobs/FrontARENA/workspace, /var/hudson/8282/work/jobs/FrontARENA/workspace, workspace $ /nfs/seu_tools/sol/python/2.6.7-64bit/bin/python /var/hudson/8282/work/plugins/shiningpanda/WEB-INF/classes/jenkins/plugins/shiningpanda/workspace/virtualenv.py --distribute /var/hudson/8282/work/shiningpanda/jobs/7613aa0d/buildouts/5868ae89 PYTHONHOME is set. You must activate the virtualenv before using it New python executable in /var/hudson/8282/work/shiningpanda/jobs/7613aa0d/buildouts/5868ae89/bin/python Installing distribute.done. Installing pip...done. $ ln -s /nfs/seu_tools/sol/python/2.6.7-64bit/lib/libhistory.so /var/hudson/8282/work/shiningpanda/jobs/7613aa0d/buildouts/5868ae89/lib/libhistory.so $ ln -s /nfs/seu_tools/sol/python/2.6.7-64bit/lib/libhistory.so.6 /var/hudson/8282/work/shiningpanda/jobs/7613aa0d/buildouts/5868ae89/lib/libhistory.so.6 $ ln -s /nfs/seu_tools/sol/python/2.6.7-64bit/lib/libreadline.so /var/hudson/8282/work/shiningpanda/jobs/7613aa0d/buildouts/5868ae89/lib/libreadline.so $ ln -s /nfs/seu_tools/sol/python/2.6.7-64bit/lib/libreadline.so.6 /var/hudson/8282/work/shiningpanda/jobs/7613aa0d/buildouts/5868ae89/lib/libreadline.so.6 $ ln -s /nfs/seu_tools/sol/python/2.6.7-64bit/lib/libsqlite3.so /var/hudson/8282/work/shiningpanda/jobs/7613aa0d/buildouts/5868ae89/lib/libsqlite3.so $ ln -s /nfs/seu_tools/sol/python/2.6.7-64bit/lib/libsqlite3.so.0 /var/hudson/8282/work/shiningpanda/jobs/7613aa0d/buildouts/5868ae89/lib/libsqlite3.so.0 $ ln -s /nfs/seu_tools/sol/python/2.6.7-64bit/lib/libsqlite3.so.0.8.6 /var/hudson/8282/work/shiningpanda/jobs/7613aa0d/buildouts/5868ae89/lib/libsqlite3.so.0.8.6 $ ln -s /nfs/seu_tools/sol/python/2.6.7-64bit/lib/libtcl8.5.so /var/hudson/8282/work/shiningpanda/jobs/7613aa0d/buildouts/5868ae89/lib/libtcl8.5.so $ ln -s /nfs/seu_tools/sol/python/2.6.7-64bit/lib/libtk8.5.so /var/hudson/8282/work/shiningpanda/jobs/7613aa0d/buildouts/5868ae89/lib/libtk8.5.so workspace $ /var/hudson/8282/work/shiningpanda/jobs/7613aa0d/buildouts/5868ae89/bin/python /var/hudson/8282/work/plugins/shiningpanda/WEB-INF/classes/jenkins/plugins/shiningpanda/workspace/bootstrap.py -c buildout.cfg --distribute Download error on http://pypi.python.org/simple/zc.buildout/: Errno 128 Network is unreachable Some packages may not be found! Download error on http://pypi.python.org/simple/zc.buildout/: Errno 128 Network is unreachable Some packages may not be found! Couldn't find index page for 'zc.buildout' (maybe misspelled?) Download error on http://pypi.python.org/simple/: Errno 128 Network is unreachable Some packages may not be found! Download error on http://pypi.python.org/simple/zc.buildout/: Errno 128 Network is unreachable Some packages may not be found! Download error on http://pypi.python.org/simple/zc.buildout/: Errno 128 Network is unreachable Some packages may not be found! Couldn't find index page for 'zc.buildout' (maybe misspelled?) Download error on http://pypi.python.org/simple/: Errno 128 Network is unreachable Some
[JIRA] (JENKINS-14232) EnvInject/Parameterized trigger not handling properties file with logical lines
Gregory Boissinot commented on JENKINS-14232 EnvInject/Parameterized trigger not handling properties file with logical lines Firstly, it seems there is a bug in the envinject plguin. If you look at the jobslist variable in the Injected environment, you should have only one value. It is the current bug. Could you check in your environment? 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
[JIRA] (JENKINS-14248) DiskUsage dont show values.
vjuranek commented on JENKINS-14248 DiskUsage dont show values. Do you have any builds there? It seems that the disk usage run (project action exists), but it seems that the size of the project is 0 (and therefore it shows "-" in overview table) 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
[JIRA] (JENKINS-14248) DiskUsage dont show values.
Mauricio Fenoglio commented on JENKINS-14248 DiskUsage dont show values. Yes I have For example the task CMS-MONITOR-SERVER ls from $JENKINS_HOME/jobs/CMS-MONITOR-SERVER/builds lrwxrwxrwx 1 cms cms 19 2012-06-28 12:44 18 - 2012-06-28_12-44-16 lrwxrwxrwx 1 cms cms 19 2012-06-28 13:10 19 - 2012-06-28_13-10-06 lrwxrwxrwx 1 cms cms 19 2012-06-28 14:44 20 - 2012-06-28_14-44-00 drwxr-xr-x 3 cms cms 4096 2012-06-28 12:44 2012-06-28_12-44-16 drwxr-xr-x 3 cms cms 4096 2012-06-28 13:10 2012-06-28_13-10-06 drwxr-xr-x 3 cms cms 4096 2012-06-28 14:44 2012-06-28_14-44-00 drwxr-xr-x 3 cms cms 4096 2012-06-28 16:16 2012-06-28_16-15-16 drwxr-xr-x 3 cms cms 4096 2012-06-29 00:02 2012-06-29_00-01-14 lrwxrwxrwx 1 cms cms 19 2012-06-28 16:15 21 - 2012-06-28_16-15-16 lrwxrwxrwx 1 cms cms 19 2012-06-29 00:01 22 - 2012-06-29_00-01-14 Anything else you think should check? 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
[JIRA] (JENKINS-14257) Saving job configuration looses slave defintion
Jose Sa created JENKINS-14257 Saving job configuration looses slave defintion Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 29/Jun/12 2:51 PM Description: In jenkins v1.472 when saving an existing job that had definitions of specific slaves where to run the job, it looses that definition. Had to revert back to previous version 1.467. Environment: Jenkins v1.472 Project: Jenkins Priority: Critical Reporter: Jose Sa 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
[JIRA] (JENKINS-14240) Changlelog is missing user names
Lars Kruse commented on JENKINS-14240 Changlelog is missing user names Scheduled to be included in our next release 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
[JIRA] (JENKINS-14239) Sometimes CCUCM finds baselines in other masterships
Lars Kruse commented on JENKINS-14239 Sometimes CCUCM finds baselines in other masterships Scheduled to be released in next release (July) 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
[JIRA] (JENKINS-13944) Missing hyperlink type tag in Clearcase does not fail the build
Lars Kruse commented on JENKINS-13944 Missing hyperlink type tag in Clearcase does not fail the build Scheduled to be implemented in next release: The job shall be unstable in the situation described. 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
[JIRA] (JENKINS-13944) Missing hyperlink type tag in Clearcase does not fail the build
Lars Kruse assigned JENKINS-13944 to Christian Wolfgang Missing hyperlink type tag in Clearcase does not fail the build Change By: Lars Kruse (29/Jun/12 3:58 PM) Assignee: ChristianWolfgang 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
[JIRA] (JENKINS-14232) EnvInject/Parameterized trigger not handling properties file with logical lines
SCM/JIRA link daemon commented on JENKINS-14232 EnvInject/Parameterized trigger not handling properties file with logical lines Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/envinject/service/PropertiesLoader.java http://jenkins-ci.org/commit/envinject-plugin/3e05be8be28ed213858e97df30bd7db71aa7d789 Log: Fix JENKINS-14232 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
[JIRA] (JENKINS-14232) EnvInject/Parameterized trigger not handling properties file with logical lines
Gregory Boissinot resolved JENKINS-14232 as Fixed EnvInject/Parameterized trigger not handling properties file with logical lines EnvInject 1.57 should solve the problem Change By: Gregory Boissinot (29/Jun/12 4:40 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
[JIRA] (JENKINS-9242) JIRA: adding a label create an exception
evernat updated JENKINS-9242 JIRA: adding a label create an exception Change By: evernat (29/Jun/12 5:13 PM) Labels: testing 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
[JIRA] (JENKINS-9242) JIRA: adding a label create an exception
evernat updated JENKINS-9242 JIRA: adding a label create an exception Change By: evernat (29/Jun/12 5:13 PM) Labels: testing 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
[JIRA] (JENKINS-14261) Builds hanging right before e-mail notifications are sent out - Mercurial
Robert Cronk commented on JENKINS-14261 Builds hanging right before e-mail notifications are sent out - Mercurial Here are three thread dumps during a single hang: threadDump #1 Executor #-1 for master : executing driver-smoketest.linux #1235 "Executor #-1 for master : executing driver-smoketest.linux #1235" Id=374602 Group=main BLOCKED on winstone.classLoader.WebappClassLoader@77ce3fc5 owned by "pool-3-thread-1820" Id=406115 at winstone.classLoader.WebappClassLoader.loadClass(WebappClassLoader.java:48) - blocked on winstone.classLoader.WebappClassLoader@77ce3fc5 at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at javax.xml.parsers.FactoryFinder.getProviderClass(FactoryFinder.java:109) at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:144) at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:231) at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:125) at org.apache.commons.digester.Digester.getFactory(Digester.java:490) at org.apache.commons.digester.Digester.getParser(Digester.java:693) at org.apache.commons.digester.Digester.getXMLReader(Digester.java:899) at org.apache.commons.digester.Digester.parse(Digester.java:1631) at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:49) at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:24) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:832) at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:806) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:358) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1419) at hudson.model.User.getProjects(User.java:409) at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:100) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:530) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:396) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:273) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:265) at hudson.plugins.emailext.ExtendedEmailPublisher.access$100(ExtendedEmailPublisher.java:69) at hudson.plugins.emailext.ExtendedEmailPublisher$1.endBuild(ExtendedEmailPublisher.java:600) at hudson.matrix.MatrixBuild$MatrixBuildExecution.post2(MatrixBuild.java:381) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1513) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:287) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66) threadDump #2 Executor #-1 for master : executing driver-smoketest.linux #1235 "Executor #-1 for master : executing driver-smoketest.linux #1235" Id=374602 Group=main RUNNABLE at java.lang.Throwable.getStackTraceElement(Native Method) at java.lang.Throwable.getOurStackTrace(Throwable.java:608) - locked java.lang.Throwable@7b0035af at java.lang.Throwable.getStackTrace(Throwable.java:599) at org.apache.commons.logging.impl.Jdk14Logger.log(Jdk14Logger.java:89) at org.apache.commons.logging.impl.Jdk14Logger.debug(Jdk14Logger.java:114) at org.apache.commons.beanutils.BeanUtilsBean.populate(BeanUtilsBean.java:814) at org.apache.commons.beanutils.BeanUtils.populate(BeanUtils.java:433) at org.apache.commons.digester.SetPropertiesRule.begin(SetPropertiesRule.java:251) at org.apache.commons.digester.Rule.begin(Rule.java:152) at org.apache.commons.digester.Digester.startElement(Digester.java:1361) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:504) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1340) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2732) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:625) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488) at
[JIRA] (JENKINS-9364) Add support for tokens from the token-macro plug-in
Jim Searle commented on JENKINS-9364 Add support for tokens from the token-macro plug-in Sorry, I was wrong. The email does get sent, but I'd still like to have the option to shut this off since it shows a huge error message in the console. 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
[JIRA] (JENKINS-13790) Subversion externals fail
Jay Beeckman commented on JENKINS-13790 Subversion externals fail Can we get an update on this? It has twice caused me to load the plugin, upgrade my workspaces, and have to revert them back because it doesn't work properly. 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
[JIRA] (JENKINS-14263) TestLink Plugin: Jenkins reports build failure when test case is failed
Karthik T created JENKINS-14263 TestLink Plugin: Jenkins reports build failure when test case is failed Issue Type: Patch Affects Versions: current Assignee: Jørgen Tjernø Components: jenkins-plugin-runtime, testlink Created: 29/Jun/12 6:44 PM Description: I'm building QA environment where test cases can be managed in TestLink and automated tests can be executed using Jenkins. I have followed instructions in 'Jenkins TestLink Plug-in Tutorial' to execute automated tests. http://tupilabs.com/books/jenkins-testlink-plugin-tutorial/en/ Jenkins successfully exectuted 'Test Current time' test case and its status is marked as 'Passed' in TestLink When 'Test Current time' fails, it results in build failure (see Jenkins console output below) and failure is not reported to TestLink. --- T E S T S --- Running jenkins.plugins.testlink.examples.TestCurrentTime Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.563 sec FAILURE! Results : Failed tests: testCurrentTime(jenkins.plugins.testlink.examples.TestCurrentTime): expected:true but was:false Tests run: 1, Failures: 1, Errors: 0, Skipped: 0 INFO INFO BUILD FAILURE INFO INFO Total time: 53.719s INFO Finished at: Thu Jun 21 16:31:01 EDT 2012 INFO Final Memory: 124M/247M INFO ERROR Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.10:test (default-test) on project jenkins-testlink-plugin-tutorial: There are test failures. ERROR ERROR Please refer to C:\Jenkin\jobs\testMaven\workspace\target\surefire-reports for the individual test results. ERROR - Help 1 ERROR ERROR To see the full stack trace of the errors, re-run Maven with the -e switch. ERROR Re-run Maven using the -X switch to enable full debug logging. ERROR ERROR For more information about the errors and possible solutions, please read the following articles: ERROR Help 1 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException Build step 'Invoke top-level Maven targets' marked build as failure Finished: FAILURE Environment: Found on Windows; it may be found in other platforms as well Project: Jenkins Labels: plugins jenkins testlink Priority: Major Reporter: Karthik T 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
[JIRA] (JENKINS-9242) JIRA: adding a label create an exception
evernat resolved JENKINS-9242 as Duplicate JIRA: adding a label create an exception Change By: evernat (29/Jun/12 8:11 PM) Status: Open Resolved Resolution: Duplicate 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
[JIRA] (JENKINS-10193) JDK Auto-Install does not allow me to select a version
evernat commented on JENKINS-10193 JDK Auto-Install does not allow me to select a version I do not see the "attached screenshot". Can you confirm that the issue it still there with recent versions? 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
[JIRA] (JENKINS-14135) NPE
Carsten Otto edited a comment on JENKINS-14135 NPE I see that this job only works on master and fails on other nodes. Maybe the issue is that "report" is transient, but you do need serialization for the object that is passed to the node? I have no idea how plugins work, but this makes a bit of sense to me. 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
[JIRA] (JENKINS-10193) JDK Auto-Install does not allow me to select a version
malachid resolved JENKINS-10193 as Fixed JDK Auto-Install does not allow me to select a version With v1.443 this does not appear to be a problem any more. Marking it resolved. Change By: malachid (29/Jun/12 8:32 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
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
jieryn commented on JENKINS-13114 dropdown views taskbar: error when saving jenkins config page You can try the latest snapshot here: https://jenkins.ci.cloudbees.com/job/plugins/job/dropdown-viewstabbar/lastSuccessfulBuild/org.jenkins-ci.plugins$dropdown-viewstabbar-plugin/artifact/org.jenkins-ci.plugins/dropdown-viewstabbar-plugin/1.6-SNAPSHOT/dropdown-viewstabbar-plugin-1.6-SNAPSHOT.hpi 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
[JIRA] (JENKINS-14264) Breadcrumb: the link to the lastBuild console is missing in the popup for a maven job
evernat updated JENKINS-14264 Breadcrumb: the link to the lastBuild console is missing in the popup for a maven job Change By: evernat (29/Jun/12 8:56 PM) Description: WhenlookingintothepopupinthebreadcrumbofthelastBuildofafreestylejob (withant) ,thereisalinktotheconsoleofthelastbuild(GOOD).Seeforexample,thepopupofthebreadcrumbinhttps://buildhive.cloudbees.com/job/cgeo/job/c-geo-opensource/lastBuild/AndthereisalsoalinktothelastBuildconsoleinthepopupofthelastBuildpermalinkinthisjobpage(GOOD).Seeforexample,thefirstattachedscreenshot.Butwhenusingamavenjob,thereisnolinktotheconsoleofthelastbuildinthebreadcrumbofthelastBuildpage(BAD).Seeforexample,thepopupofthebreadcrumbinhttps://buildhive.cloudbees.com/job/Atmosphere/job/atmosphere/lastBuild/Andinthejobpageofthesamemavenjob,thereisnolinktothelastBuildconsoleinthepopupofthelastBuildpermalinkinthesamejobpage(BAD).Seeforexampe,thesecondattachedscreenshot. 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
[JIRA] (JENKINS-14264) Breadcrumb: the link to the lastBuild console is missing in the popup for a maven job
evernat created JENKINS-14264 Breadcrumb: the link to the lastBuild console is missing in the popup for a maven job Issue Type: Bug Assignee: Unassigned Attachments: BAD.png, good.png Components: core Created: 29/Jun/12 8:56 PM Description: When looking into the popup in the breadcrumb of the lastBuild of a freestyle job (with ant), there is a link to the console of the last build (GOOD). See for example, the popup of the breadcrumb in https://buildhive.cloudbees.com/job/cgeo/job/c-geo-opensource/lastBuild/ And there is also a link to the lastBuild console in the popup of the lastBuild permalink in this job page (GOOD). See for example, the first attached screenshot. But when using a maven job, there is no link to the console of the last build in the breadcrumb of the lastBuild page (BAD). See for example, the popup of the breadcrumb in https://buildhive.cloudbees.com/job/Atmosphere/job/atmosphere/lastBuild/ And in the job page of the same maven job, there is no link to the lastBuild console in the popup of the lastBuild permalink in the same job page (BAD). See for exampe, the second attached screenshot. Project: Jenkins Labels: breadcrumb Priority: Major Reporter: evernat 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
[JIRA] (JENKINS-10177) Add URL for latest console
evernat commented on JENKINS-10177 Add URL for latest console The link to lastBuild is available in the permalinks at the bottom of the job page. For example, http://example.com/jenkins/job/my-job/lastBuild/ And the link to the last build console is in fact available at the left of the lastBuild page. Or with a recent Jenkins in the popup menu of the lastBuild link, when using a free style job with ant, but not when using a maven job. There is now an issue for the link in the popup of the lastBuild for a maven job: JENKINS-14264 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
[JIRA] (JENKINS-10177) Add URL for latest console
evernat resolved JENKINS-10177 as Not A Defect Add URL for latest console Change By: evernat (29/Jun/12 9:01 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
[JIRA] (JENKINS-12331) Util.createSymlink() doesn't work as expected if symlink should be created in a different directory
SCM/JIRA link daemon commented on JENKINS-12331 Util.createSymlink() doesnt work as expected if symlink should be created in a different directory Code changed in jenkins User: Christoph Kutzinski Path: core/src/test/java/hudson/UtilTest.java http://jenkins-ci.org/commit/jenkins/181d7dab54ede392b312433d0b7b3663ed902ed0 Log: Create unit test for Util.isSymlink JENKINS-12331 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
[JIRA] (JENKINS-12315) Location of the temporary file Maven Global Settings incompatible with release: prepare
SCM/JIRA link daemon commented on JENKINS-12315 Location of the temporary file Maven Global Settings incompatible with release: prepare Code changed in jenkins User: imod Path: maven-plugin/src/main/java/hudson/maven/settings/SettingsProviderUtils.java http://jenkins-ci.org/commit/jenkins/b5644ea25bb7bb49233bc950e199253cf72cb52f Log: FIXED JENKINS-12315 Location of the temporary file 'Maven Global Settings' incompatible with release: prepare 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
[JIRA] (JENKINS-12177) Zero executors on master is no longer valid
SCM/JIRA link daemon commented on JENKINS-12177 Zero executors on master is no longer valid Code changed in jenkins User: OHTAKE Tomohiro Path: core/src/main/resources/jenkins/model/MasterBuildConfiguration/config.groovy http://jenkins-ci.org/commit/jenkins/7534dc1d498b31cf4957a9841461851fa2773fe1 Log: FIXED JENKINS-12177 Zero executors on master should be valid 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
[JIRA] (JENKINS-12177) Zero executors on master is no longer valid
SCM/JIRA link daemon commented on JENKINS-12177 Zero executors on master is no longer valid Code changed in jenkins User: vjuranek Path: core/src/main/resources/jenkins/model/MasterBuildConfiguration/config.groovy http://jenkins-ci.org/commit/jenkins/eae53ce7467a97d749616f0954056e22494c165a Log: Merge pull request #346 from ohtake/zero-executors-master JENKINS-12177 Zero executors on master is no longer valid 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
[JIRA] (JENKINS-11353) Recognize test results from eviware:maven-soapui-plugin
SCM/JIRA link daemon commented on JENKINS-11353 Recognize test results from eviware:maven-soapui-plugin Code changed in jenkins User: puug Path: maven-plugin/src/main/java/hudson/maven/reporters/SurefireArchiver.java http://jenkins-ci.org/commit/jenkins/35c48cfcf563ad4429b51f7c920ee34159d8b4e9 Log: FIXED JENKINS-11353 Now recognises test results created by the maven-soap-ui 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
[JIRA] (JENKINS-7096) User is created even if invalid or missing information is typed
SCM/JIRA link daemon commented on JENKINS-7096 User is created even if invalid or missing information is typed Code changed in jenkins User: Michael Clarke Path: changelog.html core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java http://jenkins-ci.org/commit/jenkins/255a3e6dd67d91e74541293bf7d3ea696b01b6c1 Log: JENKINS-7096 - Stop users being created in memory if registration fails 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
[JIRA] (JENKINS-12357) Infinite loop or invalid next execution with crontab DoW=7
SCM/JIRA link daemon commented on JENKINS-12357 Infinite loop or invalid next execution with crontab DoW=7 Code changed in jenkins User: OHTAKE Tomohiro Path: core/src/main/java/hudson/scheduler/CronTab.java core/src/test/java/hudson/scheduler/CronTabDayOfWeekLocaleTest.java core/src/test/java/hudson/scheduler/CronTabTest.java http://jenkins-ci.org/commit/jenkins/20249e4adc4abaf3c81cd864331508cf68b8777b Log: FIXED JENKINS-12357 Crontab#ceil may stuck in an infinite loop or may return an incorrect value if day of week is 7 (=0, Sunday) To use @Test(timeout), inheritance from TestCase should be removed 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
[JIRA] (JENKINS-11353) Recognize test results from eviware:maven-soapui-plugin
SCM/JIRA link daemon resolved JENKINS-11353 as Fixed Recognize test results from eviware:maven-soapui-plugin Change By: SCM/JIRA link daemon (29/Jun/12 9:36 PM) Status: InProgress 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
[JIRA] (JENKINS-12388) Crontab @yearly and @anually are never triggered in 1.448 RC
SCM/JIRA link daemon commented on JENKINS-12388 Crontab @yearly and @anually are never triggered in 1.448 RC Code changed in jenkins User: OHTAKE Tomohiro Path: core/src/test/java/hudson/scheduler/CronTabEventualityTest.java http://jenkins-ci.org/commit/jenkins/240c381bb867873da8dc4984acc199b243aea48e Log: FIXED JENKINS-12388 Add tests for JENKINS-12388 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
[JIRA] (JENKINS-12889) Jenkins Workspace presents Run a build even when Builds are Disabled
SCM/JIRA link daemon commented on JENKINS-12889 Jenkins Workspace presents Run a build even when Builds are Disabled Code changed in jenkins User: Erik Lindblad Path: core/src/main/resources/hudson/model/AbstractItem/noWorkspace.jelly http://jenkins-ci.org/commit/jenkins/4f44e613e826f476d861d83df6370d2ea976bcdd Log: Fixes JENKINS-12889 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
[JIRA] (JENKINS-12622) Browser is launched with an error page at end of install
SCM/JIRA link daemon commented on JENKINS-12622 Browser is launched with an error page at end of install Code changed in jenkins User: Sami Tikka Path: changelog.html osx/scripts/postinstall-launchd osx/scripts/postinstall-launchd-jenkins http://jenkins-ci.org/commit/jenkins/eae3e3d284cb41b4366f7fcd0d29fe104083d426 Log: osx: Fix for JENKINS-12622 - opening browser too early 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
[JIRA] (JENKINS-14261) Builds hanging right before e-mail notifications are sent out - Mercurial
Devin Barbieri commented on JENKINS-14261 Builds hanging right before e-mail notifications are sent out - Mercurial This is what I have been seeing as well, so I am linking the ticket I created to this: https://issues.jenkins-ci.org/browse/JENKINS-13295 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
[JIRA] (JENKINS-8580) Upgrade Selenium Grid Plugin to Selenium Grid 2.0
apgray reopened JENKINS-8580 Upgrade Selenium Grid Plugin to Selenium Grid 2.0 Failing on Firefox 13.0.1. Please also see defect JENKINS-14207 Change By: apgray (30/Jun/12 12:29 AM) 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
[JIRA] (JENKINS-14265) Matching should be done fuzzily and not just substring matching
Jørgen Tjernø commented on JENKINS-14265 Matching should be done fuzzily and not just substring matching https://github.com/jenkinsci/keyboard-shortcuts-plugin/pull/1 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
[JIRA] (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp
Kohsuke Kawaguchi resolved JENKINS-11073 as Fixed copy artifact fails on windows XP slaves due to failing to set a timestamp I think this is a manifestation of the same issue that caues JENKINS-11251. I claim this change in remoting fixes this. This commit will be a part of 1.473. Notice that all the problem reports in this bug is about remoting. Due to the asynchrony in the read/write operations in remoting vs closure calls, it was possible that the attempt to set the timestamp happens before the file is fully is written (or even before the write starts at all.) Change By: Kohsuke Kawaguchi (30/Jun/12 1:05 AM) Status: Reopened Resolved Assignee: AlanHarder KohsukeKawaguchi 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
[JIRA] (JENKINS-14265) Matching should be done fuzzily and not just substring matching
SCM/JIRA link daemon commented on JENKINS-14265 Matching should be done fuzzily and not just substring matching Code changed in jenkins User: Jørgen P. Tjernø Path: src/main/webapp/js/keyboard-shortcuts.js http://jenkins-ci.org/commit/keyboard-shortcuts-plugin/4f0bca6fe0e9007323cd04d9d8c35d3c9f50b71b Log: JENKINS-14265 Match filter fuzzily. 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
