[JIRA] [core] (JENKINS-5318) Allow default view at user level
Oleg Nenashev commented on JENKINS-5318 Allow default view at user level Feel free to contribute 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-24924) Gerrit trigger is not wokring with Maven Projects
rin_ne resolved JENKINS-24924 as Not A Defect Gerrit trigger is not wokring with Maven Projects Change By: rin_ne (01/Oct/14 6:13 AM) 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] [gerrit-trigger] (JENKINS-24924) Gerrit trigger is not wokring with Maven Projects
rin_ne commented on JENKINS-24924 Gerrit trigger is not wokring with Maven Projects I can configure MavenProject with Gerrit Trigger. Of course its job can be triggered by gerrit events. I'm setting Jenkins 1.581 and GT 2.11.1 (The same as you prepared) If you have correctly introduced GT to your Jenkins, you can see "Gerrit Trigger" option in Build Trigger section on Job 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] [pmd] (JENKINS-24873) Wrong number of new warnings
Sergey Ryazantsev commented on JENKINS-24873 Wrong number of new warnings Hello, Ulli. What kind of properties you are talking about? 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-24914) Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc)
Marcus Philip commented on JENKINS-24914 Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc) Indeed. That's it. Never put currentTimeMillis() in an int... Maybe a unit test for this... I did a search through jenkins core and could not find any other incorrect usage of System.currentTimeMillis(). 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-22137) Broken feature: Check non-reviewed patchsets
rin_ne commented on JENKINS-22137 Broken feature: Check non-reviewed patchsets In addition, all processes are done by listener thread. It would be serious issue on system. 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-11779) Gerrit-plugin modifies ant command line which is not compatible on windows
rin_ne commented on JENKINS-11779 Gerrit-plugin modifies ant command line which is not compatible on windows You can pass all parameters to ant via file (using '-propertyfile' option) if you use the below plugin. https://wiki.jenkins-ci.org/display/JENKINS/Export+Parameters+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] [gerrit-trigger] (JENKINS-15074) Wrong type of quoting of gerrit parameters to Jenkins
rin_ne commented on JENKINS-15074 Wrong type of quoting of gerrit parameters to Jenkins On Windows, you should treat all GT parameters via file by using the below plugin. https://wiki.jenkins-ci.org/display/JENKINS/Export+Parameters+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] [gerrit-trigger] (JENKINS-16211) Gerrit Trigger GERRIT_PATCHSET_UPLOADER not support space in user name
rin_ne commented on JENKINS-16211 Gerrit Trigger GERRIT_PATCHSET_UPLOADER not support space in user name On Windows, you sould treat all parameters via file by using the below plugin. https://wiki.jenkins-ci.org/display/JENKINS/Export+Parameters+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-24914) Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc)
Daniel Beck edited a comment on JENKINS-24914 Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc) Too small (or rather too opaque) to unit test IMO. Fixed locally, will commit this week. 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-24914) Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc)
Daniel Beck commented on JENKINS-24914 Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc) Too small to unit test IMO. Fixed locally, will commit this week. 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] [global-build-stats] (JENKINS-24945) Very slow startup time (11 min) for GlobalBuildStats Plugin
Marcus Philip created JENKINS-24945 Very slow startup time (11 min) for GlobalBuildStats Plugin Issue Type: Improvement Assignee: Frédéric Camblor Components: global-build-stats Created: 01/Oct/14 7:33 AM Description: We have problems with slow startup of Global Build Stats Plugin. We have an installation with ~1000 jobs and around 50 builds kept per job. Big, but nothing extreme. Could this be due to some corrupted stats file that makes it read all builds of every job, or is it ALWAYS doing that at startup? I've seen some bad interactions between plugins, e.g. template-project and jobConfigHistory. Where combined they cause ridiculous amount of work. Excerpt from Jenkins logs. With plugin: INFO: Took 665401ms for item listener hudson.plugins.global_build_stats.GlobalBuildStatsPlugin$GlobalBuildStatsItemListener startup INFO: Took 718900ms for complete Jenkins startup Without plugin: INFO: Took 57859ms for complete Jenkins startup Environment: Jenkins ver. 1.565, global-build-stats: 1.3, Redhat 6, SAN fs with tiers (SSD, disk, ...) Project: Jenkins Labels: performance Priority: Major Reporter: Marcus Philip 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] [hp-application-automation-tools-plugin] (JENKINS-19374) issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run mach
Amit Bezalel updated JENKINS-19374 issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://Almserver:Portnumber/qcbin/TDConnectivity_index.html the clean script for alm client installations (removes all alm client installations from the machine) Change By: Amit Bezalel (01/Oct/14 7:39 AM) Attachment: cleanAlmClient.bat 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] [hp-application-automation-tools-plugin] (JENKINS-19374) issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run mach
Amit Bezalel commented on JENKINS-19374 issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://Almserver:Portnumber/qcbin/TDConnectivity_index.html You can use the script i attached to remove old alm client installations from the machine, then install the alm client by using commons=true or TDConnectivity_index.html (according to alm version). Regards, Amit. 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] [docker-build-step] (JENKINS-24551) Docker URL contains invalid version information
vjuranek resolved JENKINS-24551 as Fixed Docker URL contains invalid version information Should be fixed by PR #15, thanks to Harald Albers. Change By: vjuranek (01/Oct/14 7:42 AM) 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 -- 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] [hp-application-automation-tools-plugin] (JENKINS-23303) always prompt tdconnection_index.html when runing between alrm11 and uft 11.5(QTP11.5)?
Amit Bezalel commented on JENKINS-23303 always prompt tdconnection_index.html when runing between alrm11 and uft 11.5(QTP11.5)? Hi, The machine that should be installed with commons=true or tdconnection_index is the machine that will run UFT, so if you have a slave configured - you should install it on the slave and not on the server machine. (this is the machine you should check connectivity to ALM server from as well) If you are on the correct machine and still have problems, you should try to clean old alm client installations, in this case please use the cleaning script i have attached to JENKINS-19374. 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] [buildgraph-view] (JENKINS-19470) Build Graph not displaying
David Caro commented on JENKINS-19470 Build Graph not displaying I've fetched the code, modified it and made it 'work' again. I had to require some classes from the builflow plugin to make it work so I don't think is the best solution (I'm not a java developer either). We have been heavily using my modified version for a couple weeks without issues so far, you can find it here: https://github.com/david-caro/buildgraph-view https://github.com/david-caro/build-flow-plugin Feel free to fork and clean up The issue that I think it's happening is that it's not detecting properly the parent relation for flow jobs because it's not properly resolving the class, and instead of injecting it it's just using the local definition (if that makes any sense). 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] [jacoco] (JENKINS-19916) Confusing failure mode when no classes found by classPattern
Markus Schlegel commented on JENKINS-19916 Confusing failure mode when no classes found by classPattern I assume, I have the same problem here. I get the error: ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception java.lang.IllegalStateException: basedir C:\Jenkins\jobs\Trunk_TestCoverage\builds\2014-10-01_09-16-20\jacoco\classes does not exist at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550) at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584) at hudson.plugins.jacoco.ExecutionFileLoader.analyzeStructure(ExecutionFileLoader.java:128) at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:137) at hudson.plugins.jacoco.JacocoReportDir.parse(JacocoReportDir.java:102) at hudson.plugins.jacoco.JacocoBuildAction.loadRatios(JacocoBuildAction.java:291) at hudson.plugins.jacoco.JacocoBuildAction.load(JacocoBuildAction.java:273) at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:371) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1770) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) after the build was otherwise successful. I am using the enhanced project's settings to reuse the workspace of a our main job. Maybe this is related to this kind of setup? 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] [jacoco] (JENKINS-19916) Confusing failure mode when no classes found by classPattern
Markus Schlegel edited a comment on JENKINS-19916 Confusing failure mode when no classes found by classPattern I assume, I have the same problem here. I get the error: ... BUILD SUCCESSFUL Total time: 25 minutes 35 seconds Archiving artifacts Recording test results [JaCoCo plugin] Collecting JaCoCo coverage data... [JaCoCo plugin] antbuild/test-reports/*.exec;antbuild/all;source/java/**; locations are configured [JaCoCo plugin] Number of found exec files: 0 [JaCoCo plugin] Saving matched execfiles: [JaCoCo plugin] Saving matched class directories: [JaCoCo plugin] Saving matched source directories: [JaCoCo plugin] Loading inclusions files.. [JaCoCo plugin] inclusions: [] [JaCoCo plugin] exclusions: [**/*Test*.class] ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception java.lang.IllegalStateException: basedir C:\Jenkins\jobs\Trunk_TestCoverage\builds\2014-10-01_09-16-20\jacoco\classes does not exist at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550) at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584) at hudson.plugins.jacoco.ExecutionFileLoader.analyzeStructure(ExecutionFileLoader.java:128) at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:137) at hudson.plugins.jacoco.JacocoReportDir.parse(JacocoReportDir.java:102) at hudson.plugins.jacoco.JacocoBuildAction.loadRatios(JacocoBuildAction.java:291) at hudson.plugins.jacoco.JacocoBuildAction.load(JacocoBuildAction.java:273) at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:371) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1770) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) after the build was otherwise successful. I am using the enhanced project's settings to reuse the workspace of a our main job. Maybe this is related to this kind of setup? 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] [jenkins-multijob-plugin] (JENKINS-24922) Jenkins importer in bamboo does not show all the build plans available on jenkins environment for migration.
Sravan Kumar updated JENKINS-24922 Jenkins importer in bamboo does not show all the build plans available on jenkins environment for migration. Change By: Sravan Kumar (01/Oct/14 8:08 AM) Priority: Critical Blocker 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] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582
Duncan Shepherd created JENKINS-24946 JUnit Tests Results fail to archive in V1.582 Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 01/Oct/14 8:24 AM Description: Stack trace has certain elements replaced with generic terms ERROR: Failed to archive test reports java.io.IOException: remote file operation failed: c:\jenkins_slave\workspace\Job Name at hudson.remoting.Channel@3c0156a0:Machine Name at hudson.FilePath.act(FilePath.java:914) at hudson.FilePath.act(FilePath.java:896) at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:129) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:141) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1770) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Reverting to pre 1.577 version (ie before JUnit was split out to a plugin) fault does not occur Environment: Jenkins 1.582 running as a service on Windows7, building on Slaves also running as services on Windows7 machines. JUnit Plugin 1.1 Project: Jenkins Priority: Minor Reporter: Duncan Shepherd 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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Marcus Linke commented on JENKINS-23924 New div layout breaks Radiator view The issue should be reopened at least. 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-24947) Allow the administrator to setup preventative node monitoring on a per node basis instead of 1 configuration for all nodes
Glenn Nieuwenhuyse created JENKINS-24947 Allow the administrator to setup preventative node monitoring on a per node basis instead of 1 configuration for all nodes Issue Type: New Feature Assignee: Unassigned Components: core Created: 01/Oct/14 8:39 AM Description: When Jenkins is used for handling multiple tasks like building and continuous integration. It is possible that Jenkins has different types of nodes to perform these separate tasks. Due to the difference in nature of these nodes machines there are also different limits with regards to the preventative node monitoring limits for disk space and temp space for each of these types of nodes. Therefore it would be very advantageous to be able to configure these limits for each of the nodes separately instead of configuring this at the global level. Environment: Jenkins version 1.582 Project: Jenkins Priority: Minor Reporter: Glenn Nieuwenhuyse 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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Baptiste Mathus commented on JENKINS-23924 New div layout breaks Radiator view @Marcus, please see my previous comment. If you can give all the details you can, that'd help. I just rechecked with dozens of projects here, and it works fine for me. I'm not gonna work on this if I can't reproduce it. As I already said Does it also work for you with Jenkins 1.580? Which browser/env (precise versions) Your jenkins version where it doesn't work. 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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Baptiste Mathus edited a comment on JENKINS-23924 New div layout breaks Radiator view @Marcus, please see my previous comment. If you can give all the details you can, that'd help. I just rechecked with dozens of projects here, and it works fine for me. I'm not gonna work on this if I can't reproduce it. As I already said Does it also work for you with Jenkins 1.580? Which browser/env (precise versions) Your jenkins version where it doesn't work. your radiator view plugin configuration: display stable jobs? Show as project? Which plugin version? And so on. 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-24550) When I update my Jenkins from 1.563 to 1.566 or later，my Internet Explorer gets warning：Your Internet Explorer appears to be set to a non-defalut 'Document Mode'
Christian Kaiser commented on JENKINS-24550 When I update my Jenkins from 1.563 to 1.566 or later，my Internet Explorer gets warning：Your Internet Explorer appears to be set to a non-defalut Document Mode Unfortunatelly for me there is no chance, I need to downgrade as well. It is irritating for our developers and we cannot change the browser. It would be great to have this fixed soon. 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-24947) Allow the administrator to setup preventative node monitoring on a per node basis instead of 1 configuration for all nodes
Daniel Beck commented on JENKINS-24947 Allow the administrator to setup preventative node monitoring on a per node basis instead of 1 configuration for all nodes Maybe also consider making the update interval (1 hr or manually triggered) configurable. 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-24550) When I update my Jenkins from 1.563 to 1.566 or later，my Internet Explorer gets warning：Your Internet Explorer appears to be set to a non-defalut 'Document Mode'
Daniel Beck commented on JENKINS-24550 When I update my Jenkins from 1.563 to 1.566 or later，my Internet Explorer gets warning：Your Internet Explorer appears to be set to a non-defalut Document Mode Which versions of IE are affected by this? Is it just IE6 () and IE8? 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] [global-build-stats] (JENKINS-24945) Very slow startup time (11 min) for GlobalBuildStats Plugin
Daniel Beck commented on JENKINS-24945 Very slow startup time (11 min) for GlobalBuildStats Plugin The plugin is from a time when Jenkins loaded all data into memory on startup. Now build records are retained as soft references and only loaded on demand. There's a chance you can make it better by adding more RAM/Xmx, but it's possible the plugin just doesn't work well with Jenkins 1.485+. Re JobConfigHistory, disable deduplication in the global options. It's expensive. 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] [jacoco] (JENKINS-19916) Confusing failure mode when no classes found by classPattern
Markus Schlegel commented on JENKINS-19916 Confusing failure mode when no classes found by classPattern It is not related to the reuse of the workspace. I changed the settings to let the job use it's own workspace and I get the same error. 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-24550) When I update my Jenkins from 1.563 to 1.566 or later，my Internet Explorer gets warning：Your Internet Explorer appears to be set to a non-defalut 'Document Mode'
Christian Kaiser commented on JENKINS-24550 When I update my Jenkins from 1.563 to 1.566 or later，my Internet Explorer gets warning：Your Internet Explorer appears to be set to a non-defalut Document Mode We are using IE8.0.7601* 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-24926) Connection to slave constantly breaks, java process can only be kill -9-ed
Johannes Wienke commented on JENKINS-24926 Connection to slave constantly breaks, java process can only be kill -9-ed This is a thread dump after trying to stop jenkins with the debian init script. The server webserver doesn't react anymore, but the process stays alive: http://pastebin.com/zRFgHSjJ 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-24550) When I update my Jenkins from 1.563 to 1.566 or later，my Internet Explorer gets warning：Your Internet Explorer appears to be set to a non-defalut 'Document Mode'
Daniel Beck commented on JENKINS-24550 When I update my Jenkins from 1.563 to 1.566 or later，my Internet Explorer gets warning：Your Internet Explorer appears to be set to a non-defalut Document Mode Let me rephrase: Is anyone experiencing this problem on a supported version of IE, or can this be resolved as Won't Fix? https://wiki.jenkins-ci.org/display/JENKINS/Browser+Compatibility+Matrix 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] [pmd] (JENKINS-24873) Wrong number of new warnings
Ulli Hafner commented on JENKINS-24873 Wrong number of new warnings Same type, filename, line, ... Currently all warnings are collected in a set which does not contain duplicates. 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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Marcus Linke commented on JENKINS-23924 New div layout breaks Radiator view I'm using latest Jenkins 1.582 and Radiator 1.19 here and tested with Firefox 32.0.3 and Chrome 37.0.2062.124 under MacOS 10.8.5. The only option that is enabled in the view is 'Use dark background'. The attached UI screenshot JENKINS_23924.jpg is taken with Firefox. 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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Eric Düll edited a comment on JENKINS-23924 New div layout breaks Radiator view @Baptiste: Sorry that I did not respond earlier. Does it also work for you with Jenkins 1.580? Can you please provide a download link? The homepage only points to http://mirrors.jenkins-ci.org/war/latest/jenkins.war (what is currently 1.582) Could you please also test with a recent version of Firefox to see if the issue is still present with recent ones? Due to company regulations we are sticked to the Firefox 24.x branch. I am using the version 24.6.0. from 10-Jun-2014 09:37. I will try another FF one (standalone) later. Anyhow: I tried it with Google chrome: Same result. Which browser/env (precise versions) FF 24.6.0 and Chrome 37.0.2062.120 m Your jenkins version where it doesn't work. 1.582 your radiator view plugin configuration: display stable jobs? Show as project? Which plugin version? And so on. Version: 1.19 Confguration Filter build queue: no Filter build executors: no Caption text: "" Caption size: 36 Recurse in subfolders: yes Use a regular _expression_ to include jobs into the view: ".*" Show stable builds?: no Show stable detail?: no Use Dark Background?: yes Show as Projects?: no Show build stability?: no 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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Marcus Linke updated JENKINS-23924 New div layout breaks Radiator view Screenshot Change By: Marcus Linke (01/Oct/14 9:32 AM) Attachment: JENKINS-23924.jpg 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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Eric Düll commented on JENKINS-23924 New div layout breaks Radiator view @Baptiste: Sorry that I did not respond earlier. Does it also work for you with Jenkins 1.580? Can you please provide a download link? The homepage only points to http://mirrors.jenkins-ci.org/war/latest/jenkins.war (what is currently 1.582) Could you please also test with a recent version of Firefox to see if the issue is still present with recent ones? Due to company regulations we are sticked to the Firefox 24.x branch. I am using the version 24.6.0. from 10-Jun-2014 09:37. I will try another FF one (standalone) later. Anyhow: I tried it with Google chrome: Same result. Which browser/env (precise versions) FF 24.6.0 and Chrome 37.0.2062.120 m Your jenkins version where it doesn't work. 1.582 *your radiator view plugin configuration: display stable jobs? Show as project? Which plugin version? And so on. Version: 1.19 Confguration Filter build queue: no Filter build executors: no Caption text: "" Caption size: 36 Recurse in subfolders: yes Use a regular _expression_ to include jobs into the view: ".*" Show stable builds?: no Show stable detail?: no Use Dark Background?: yes Show as Projects?: no Show build stability?: no 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] [gradle] (JENKINS-20180) Jenkins fails to save configuration if invoking gradle file with: net.sf.json.JSONException: JSONObject[useWrapper] is not a JSONObject
Daniel Spilker updated JENKINS-20180 Jenkins fails to save configuration if invoking gradle file with: net.sf.json.JSONException: JSONObject[useWrapper] is not a JSONObject This has not been an issue of the gradle-jpi-plugin (the Gradle plugin to build Jenkins plugins). Change By: Daniel Spilker (01/Oct/14 9:41 AM) Component/s: gradle-jpi-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] [envinject] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Wisen Tanasa commented on JENKINS-13348 EnvInject overriding WORKSPACE variable I'm hitting the same issue with EnvInject 1.89 and Jenkins 1.553. 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-24924) Gerrit trigger is not wokring with Maven Projects
Doron Shai reopened JENKINS-24924 Gerrit trigger is not wokring with Maven Projects of-course it is possible to add the Trigger to the Job configuration - but when doing so the job is not triggered Change By: Doron Shai (01/Oct/14 10:26 AM) Resolution: NotADefect 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] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
Doron Shai created JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects Issue Type: Bug Assignee: rsandell Components: gerrit-trigger, git Created: 01/Oct/14 10:32 AM Description: In Maven project when the trigger is set to Poll git SCM or Gerrit trigger the Git/Gerrit parameters are not part of the maven project environment Variables as they are in freestyle projects and Multijob Projects. i am refering to these environment Variables: GERRIT_EVENT_TYPE GERRIT_CHANGE_URL GERRIT_BRANCH GERRIT_CHANGE_OWNER_EMAIL GERRIT_CHANGE_SUBJECT GIT_COMMIT GIT_URL GIT_BRANCH Environment: Jenkins 1.581 GT 2.11.1 Git 2.2.6 Project: Jenkins Labels: plugin maven git gerrit Priority: Major Reporter: Doron Shai 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] [envinject] (JENKINS-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used
Doron Shai commented on JENKINS-14193 EnvInject doesnt pass variables defined in prebuild step if maven project is used Any estimation if this issue will be fixed and when? it is quite an annoying 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] [pmd] (JENKINS-24873) Wrong number of new warnings
SCM/JIRA link daemon commented on JENKINS-24873 Wrong number of new warnings Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/FilesParser.java src/main/java/hudson/plugins/analysis/core/ParserResult.java http://jenkins-ci.org/commit/analysis-core-plugin/1d1eb5b17cc4fa21043fe8332599b66ab1e17334 Log: Merge pull request #21 from sschuberth/master Fix checking for duplicate annotations. (Maybe related to JENKINS-24873). Compare: https://github.com/jenkinsci/analysis-core-plugin/compare/a5cae3ab9dfd...1d1eb5b17cc4 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] [artifactory] (JENKINS-24949) Artifactory plugin version 2.2.4 uses ivy-2.2.0.jar
Aleksey Alekseev created JENKINS-24949 Artifactory plugin version 2.2.4 uses ivy-2.2.0.jar Issue Type: Bug Assignee: yossis Components: artifactory Created: 01/Oct/14 11:12 AM Description: There is no way to change ivy library version, unless you changed file in library plugin library location. Please add this ability, because project that uses ivy 2.3 could not be build with current version of plugin. Project: Jenkins Labels: artifactory ivy Priority: Major Reporter: Aleksey Alekseev 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] [pmd] (JENKINS-24873) Wrong number of new warnings
Sergey Ryazantsev edited a comment on JENKINS-24873 Wrong number of new warnings Hello, Ulli. What kind of properties are you talking about? 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] [ws-cleanup] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
vjuranek commented on JENKINS-24824 Asynchronous cleanup not removing renamed workspace directories on slaves Hi, any idea how to reproduce it? Everything works fine on my machine. Do you use any "Advanced" options? If so, which one? What is the OS of the slave where ws is not deleted? 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] [ivytrigger] (JENKINS-24950) IvyTrigger not triggering when new snapshot is posted in same version
Ignace Martin created JENKINS-24950 IvyTrigger not triggering when new snapshot is posted in same version Issue Type: Bug Assignee: Gregory Boissinot Components: ivytrigger, ivyttrigger Created: 01/Oct/14 12:01 PM Description: The trigger is polling artifacts from Artifactory. When a new snapshot is posted for the same version (e.g. 1.0.0-SNAPSHOT), the trigger is not detecting it. Looking in the trigger log I get : ... Resolved dependency org.slf4j#slf4j-api;1.7.7 ... Resolved dependency my.company.app#meta.model;1.0.0-SNAPSHOT ... Resolved dependency org.apache.commons#commons-lang3;3.3.2 ... Checking comparison to previous recorded dependencies. Checking previous recording dependency org.slf4j#slf4j-api;1.7.7 ...Checking comparison to previous recorded artifacts. Checking previous recording dependency my.company.app#meta.model;1.0.0-SNAPSHOT ...Checking comparison to previous recorded artifacts. Checking previous recording dependency org.apache.commons#commons-lang3;3.3.2 ...Checking comparison to previous recorded artifacts. Looking at the code of the plugin, it seems to never enter in the isArtifactChanged function at the end of IvyTrigger.isDependencyChanged function. The log message "Checking previous recording artifact %s" is never shown ... Environment: Jenkins 1.581 IvyTrigger 0.32 Project: Jenkins Labels: plugin Priority: Major Reporter: Ignace Martin 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] [global-build-stats] (JENKINS-24951) NPE in at hudson.plugins.global_build_stats.model.JobBuildResultSharder.load(JobBuildResultSharder.java:140)
Walter Kacynski commented on JENKINS-24951 NPE in at hudson.plugins.global_build_stats.model.JobBuildResultSharder.load(JobBuildResultSharder.java:140) This error occurs every-time my Jenkins Master restarts. 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] [global-build-stats] (JENKINS-24951) NPE in at hudson.plugins.global_build_stats.model.JobBuildResultSharder.load(JobBuildResultSharder.java:140)
Walter Kacynski created JENKINS-24951 NPE in at hudson.plugins.global_build_stats.model.JobBuildResultSharder.load(JobBuildResultSharder.java:140) Issue Type: Bug Assignee: Frédéric Camblor Components: global-build-stats Created: 01/Oct/14 12:07 PM Description: Jenkins 1.554.2.2 Global Build Stats 1.3 Oct 1, 2014 7:57:16 AM hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver reloadPlugin SEVERE: Unable to read E:\Jenkins\global-build-stats.xml java.io.IOException: Unable to read E:\Jenkins\global-build-stats.xml at hudson.XmlFile.unmarshal(XmlFile.java:165) at hudson.Plugin.load(Plugin.java:239) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin.load(GlobalBuildStatsPlugin.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver.reloadPlugin(GlobalBuildStatsPluginSaver.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsBusiness.reloadPlugin(GlobalBuildStatsBusiness.java:382) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin$GlobalBuildStatsItemListener.onLoaded(GlobalBuildStatsPlugin.java:149) at jenkins.model.Jenkins.init(Jenkins.java:858) at hudson.model.Hudson.init(Hudson.java:82) at hudson.model.Hudson.init(Hudson.java:78) at hudson.WebAppMain$3.run(WebAppMain.java:222) Caused by: com.thoughtworks.xstream.converters.ConversionException: null : null Debugging information cause-exception : java.lang.NullPointerException cause-message : null class : hudson.plugins.global_build_stats.GlobalBuildStatsPlugin required-type : hudson.plugins.global_build_stats.GlobalBuildStatsPlugin converter-type : hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter path: /hudson.plugins.global_build_stats.GlobalBuildStatsPlugin line number : 2 version : not available --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189) at hudson.util.XStream2.unmarshal(XStream2.java:113) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173) at hudson.XmlFile.unmarshal(XmlFile.java:163) ... 9 more Caused by: java.lang.NullPointerException at java.util.ArrayList.addAll(ArrayList.java:472) at hudson.plugins.global_build_stats.model.JobBuildResultSharder.load(JobBuildResultSharder.java:140) at hudson.plugins.global_build_stats.xstream.migration.AbstractMigrator.readGlobalBuildStatsPOJO(AbstractMigrator.java:35) at hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter.unmarshal(GlobalBuildStatsXStreamConverter.java:159) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) ... 18 more Oct 1, 2014 7:57:16 AM hudson.WebAppMain$3 run INFO: Jenkins is fully up and running Project: Jenkins Priority: Major Reporter: Walter Kacynski This message is automatically generated by JIRA.
[JIRA] [ws-cleanup] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Tom Moore commented on JENKINS-24824 Asynchronous cleanup not removing renamed workspace directories on slaves The slaves are running on a VM that is running Windows 7 Enterprise, Service Pack 1.The slaves start their Jenkins connection via slave command line. Running as a Windows service is not an option as the build process must be subordinate to an active login session due to compiler restrictions. No advanced options were set. 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-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
Marnix Klooster commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported We also have this issue. We've seen several instances of this with 1.565.1, from India to a Jenkins master in the Netherlands. Never noticed anything like this with 1.532.2 which we were using before, or any older versions. Funnily enough, we also yesterday had an issue where a build (running on the NL Jenkins master) downloaded (in some Ant build step) a large binary from another Jenkins master running 1.456 (Server: Apache-Coyote/1.1) located in the Philippines, which also resulted in a partial download with no error. No idea what to make of this, but perhaps this helps. Cannot yet reproduce the problem using ab, but haven't yet let it run for a longer period of time... 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-24924) Gerrit trigger is not wokring with Maven Projects
rin_ne commented on JENKINS-24924 Gerrit trigger is not wokring with Maven Projects See my comment again. I already confirmed GT configured job is correctly triggered by gerrit event. 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-24924) Gerrit trigger is not wokring with Maven Projects
rin_ne resolved JENKINS-24924 as Not A Defect Gerrit trigger is not wokring with Maven Projects Change By: rin_ne (01/Oct/14 12:47 PM) Status: Reopened 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] [artifactdeployer] (JENKINS-18333) Cleanup plugin doesn't work with artifact deployer - the clean up order is wrong
Gigi Lentini commented on JENKINS-18333 Cleanup plugin doesnt work with artifact deployer - the clean up order is wrong Hi, any news about that? I have seen trough the comments in the main page a workaround could be to use the 'deploy artifacts' build step, but I don't have it in the list (using Jenkins 1.565.1 and latest plugin version). Cheers! 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-24924) Gerrit trigger is not wokring with Maven Projects
rin_ne edited a comment on JENKINS-24924 Gerrit trigger is not wokring with Maven Projects See my comment again. I already confirmed GT configured job is correctly triggered by gerrit event. Please configure GT with the below parameters then test again. Project Path: ** Branch Path: ** 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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Eric Düll
edited a comment on JENKINS-23924
New div layout breaks Radiator view
Have a look at the following css:
style.css (line 121)
body, table, form, input, td, th, p, textarea, select {
--remove background-color and it looks better.
}
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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Eric Düll
edited a comment on JENKINS-23924
New div layout breaks Radiator view
Have a look at the following css:
style.css (line 121)
body, table, form, input, td, th, p, textarea, select {
--remove "background-color" and it looks better.
}
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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Eric Düll
commented on JENKINS-23924
New div layout breaks Radiator view
Have a look at the following css:
style.css (line 121)
body, table, form, input, td, th, p, textarea, select {
--remove background-color and it looks better.
}
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] [testlink] (JENKINS-23265) TestLink plugin indicates test case as not run and TestLink is not updated with build status
Robert Grzeskowiak commented on JENKINS-23265 TestLink plugin indicates test case as not run and TestLink is not updated with build status Problem still exists on Jenkins 1.576. 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] [testlink] (JENKINS-24424) TestLink Plugin - Does not show Execution Status
Robert Grzeskowiak commented on JENKINS-24424 TestLink Plugin - Does not show Execution Status It is the same issue as is in JENKINS-23265 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] [jenkins-reviewbot] (JENKINS-19642) ReviewBot plugin fails after 'apply patch'
Dan Albu commented on JENKINS-19642 ReviewBot plugin fails after apply patch I successfully implemented a POC on my build systems and all ok now.The plugin still needs more implementations but is god for start 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] [sbt] (JENKINS-24952) Wrong umask
m g created JENKINS-24952 Wrong umask Issue Type: Bug Assignee: uzilan Components: sbt Created: 01/Oct/14 1:32 PM Description: Error when using sbt native packager with SBT: `sbt debian:packageBin` https://gist.github.com/mgosk/2f648a877c29b367f6aa Temporary I solve problem by setting default 0022 umask in /etc/defaults/jenkins Environment: ubuntu 14.01 Project: Jenkins Priority: Minor Reporter: m g 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] [accurev] (JENKINS-21604) Accurev plugin builds .accurev in job config directories
Walter Kacynski commented on JENKINS-21604 Accurev plugin builds .accurev in job config directories Setting ACCUREV_HOME on the Master and slaves fixes this problem. The only downside of this is that more than one login can't be used for accurev operations. For our site, this is not currently a 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] [accurev] (JENKINS-22765) configuring a job shows an accurev syntax output in the master
Walter Kacynski closed JENKINS-22765 as Fixed configuring a job shows an accurev syntax output in the master Plugin version .6.30 seems to address this problem. Change By: Walter Kacynski (01/Oct/14 2:06 PM) Status: Open Closed 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-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
Daniel Beck commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported Does the same issue occur for files stored in /userContent ? 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] [parameterized-trigger] (JENKINS-18486) When providing multiple jobs to run, support running them one after another and not all together
Edd Grant commented on JENKINS-18486 When providing multiple jobs to run, support running them one after another and not all together +1 It would be a really useful feature to be able to trigger downstream parameterised jobs serially, plus also optionally being able to decide not to continue if any of those jobs fail. 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] [jacoco] (JENKINS-23588) JaCoCo Plugin creates unreadable coverage report
Markus Schlegel updated JENKINS-23588 JaCoCo Plugin creates unreadable coverage report Guys, Attached two screenshots from the exactly same build. One that shows Emmas view to the code coverage metrics and another one showing Jacoco's view. The emma metrics have been built out of the Jacoco coverage result using an xslt stylesheet. As you can see (I hope you see it) the view given by emma is much more readable than jacoco's view. I would even say that Jacoco's views is completely unusable. Change By: Markus Schlegel (01/Oct/14 2:35 PM) Attachment: Jenkins-Emma.png Attachment: Jenkins-Jacoco.png 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] [parameterized-trigger] (JENKINS-18486) When providing multiple jobs to run, support running them one after another and not all together
Edd Grant edited a comment on JENKINS-18486 When providing multiple jobs to run, support running them one after another and not all together +1 It would be a really useful feature to be able to trigger downstream parameterised jobs serially, plus also optionally being able to decide not to continue if any of those jobs fail. edit: - I've just realised that this can be achieved by "Trigger/ Call builds on other projects" which allows exactly the configuration I was after: block/ don't block, fail conditionally etc. So please feel free to discount my +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 -- 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-23222) Build hung on archiving artifacts: IllegalAccessError
David Ishee commented on JENKINS-23222 Build hung on archiving artifacts: IllegalAccessError Still having this problem periodically with 1.565.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] [cygpath] (JENKINS-20364) Failed to locate cygwin installation
Neeme Praks commented on JENKINS-20364 Failed to locate cygwin installation I'm also having this problem (at least from the description, it looks similar). I tracked it down to difference between 32bit JVM vs 64bit JVM. The plugin was consistently failing with 32bit JVM (Java 7) and it works with 64bit JVM. My environment: 64-bit Windows 7 (6.1.7601 Service Pack 1 Build 7601) 64-bit JVM: java version "1.7.0_40" Java(TM) SE Runtime Environment (build 1.7.0_40-b43) Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode) 32-bit JVM: java version "1.7.0_40" Java(TM) SE Runtime Environment (build 1.7.0_40-b43) Java HotSpot(TM) Client VM (build 24.0-b56, mixed mode, sharing) If I open registry editor, then I can see that "HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup" key exists. Other options that cygpath plugin tried to locate do not exist. All options: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin\setup HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygnus Solutions\Cygwin\mounts v2\/ HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/ (so, the third should succeed) The problem is the "access" flag that is passed to "RegOpenKeyEx" API call: it has the value for READ_ONLY (0x20019) but should also contain either 0x0100 (KEY_WOW64_64KEY) or 0x0200 (KEY_WOW64_32KEY), depending on the running JVM (either 32bits or 64bits). The relevant part in RegistryKey class: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/util/jna/RegistryKey.java#L217 Useful reading: http://windowsitpro.com/systems-management/whats-wow6432node-under-hkeylocalmachinesoftware-registry-subkey http://msdn.microsoft.com/en-us/library/windows/desktop/aa384129(v=vs.85).aspx Also, I'm not sure the change made in JENKINS-7303 actually fixes anything (did someone test this?). The "Wow6432Node" subkey seems to be implementation detail of Windows registry and the application code should not care about it. Instead, it should use the relevant access bit (as described above). Also, my tests have shown that with current code, 64bit JVM running on 64bit Windows can access "HKEY..WARE\Cygwin\setup". The problem is with 32bit JVM running on 64bit Windows: it looks up "HKEY..WARE\Cygwin\setup" but Windows translates that into "HKEY..WARE\Wow6432Node\Cygwin\setup" (which is missing). And, when it tries to access "HKEY..WARE\Wow6432Node\Cygwin\setup", Windows probably translates that into "HKEY..WARE\Wow6432Node\Wow6432Node\Cygwin\setup" which is also missing. So 32bit JVM running on 64bit Windows has no access to "HKEY..WARE\Cygwin\setup" unless it specifies the special KEY_WOW64_64KEY flag. I'm not sure if the other scenario of 64bit JVM running on 64bit Windows trying to look up "HKEY..WARE\Wow6432Node\Cygwin\setup" works or KEY_WOW64_32KEY flag should be used instead (covering the case when "HKEY..WARE\Cygwin\setup" is missing but "HKEY..WARE\Wow6432Node\Cygwin\setup" exists). Should probably test that. 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] [plugin] (JENKINS-7303) Could not find cygpath on Win64 machine
Neeme Praks commented on JENKINS-7303 Could not find cygpath on Win64 machine I added a comment under JENKINS-20364, but it is somewhat relevant also for this issue, so I'm copying parts of it here. I'm not sure the change made here actually fixes anything (did someone test this?). The "Wow6432Node" subkey seems to be implementation detail of Windows registry and the application code should not care about it. Instead, it should use the relevant access bit (as described above). Also, my tests have shown that with current code, 64bit JVM running on 64bit Windows can access "HKEY..WARE\Cygwin\setup". The problem is with 32bit JVM running on 64bit Windows: it looks up "HKEY..WARE\Cygwin\setup" but Windows translates that into "HKEY..WARE\Wow6432Node\Cygwin\setup" (which is missing). And, when it tries to access "HKEY..WARE\Wow6432Node\Cygwin\setup", Windows probably translates that into "HKEY..WARE\Wow6432Node\Wow6432Node\Cygwin\setup" which is also missing. So 32bit JVM running on 64bit Windows has no access to "HKEY..WARE\Cygwin\setup" unless it specifies the special KEY_WOW64_64KEY flag. I'm not sure if the other scenario of 64bit JVM running on 64bit Windows trying to look up "HKEY..WARE\Wow6432Node\Cygwin\setup" works or KEY_WOW64_32KEY flag should be used instead (covering the case when "HKEY..WARE\Cygwin\setup" is missing but "HKEY..WARE\Wow6432Node\Cygwin\setup" exists). Should probably test that. Useful reading: http://windowsitpro.com/systems-management/whats-wow6432node-under-hkeylocalmachinesoftware-registry-subkey http://msdn.microsoft.com/en-us/library/windows/desktop/aa384129(v=vs.85).aspx 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] [plugin] (JENKINS-7303) Could not find cygpath on Win64 machine
Neeme Praks edited a comment on JENKINS-7303 Could not find cygpath on Win64 machine I added a comment under JENKINS-20364, but it is somewhat relevant also for this issue, so I'm copying parts of it here. I'm not sure the change made in JENKINS-7303 actually fixes anything (did someone test this?). The "Wow6432Node" subkey seems to be implementation detail of Windows registry and the application code should not care about it. Instead, it should use the relevant access bit (as described above). Also, my tests have shown that with current code, 64bit JVM running on 64bit Windows can access "HKEY..WARE\Cygwin\setup". The problem is with 32bit JVM running on 64bit Windows: it looks up "HKEY..WARE\Cygwin\setup" but Windows translates that into "HKEY..WARE\Wow6432Node\Cygwin\setup" (which is missing). And, when it tries to access "HKEY..WARE\Wow6432Node\Cygwin\setup", Windows probably translates that into "HKEY..WARE\Wow6432Node\Wow6432Node\Cygwin\setup" which is also missing. So 32bit JVM running on 64bit Windows has no access to "HKEY..WARE\Cygwin\setup" unless it specifies the special KEY_WOW64_64KEY flag. I'm not sure if the other scenario of 64bit JVM running on 64bit Windows trying to look up "HKEY..WARE\Wow6432Node\Cygwin\setup" works or KEY_WOW64_32KEY flag should be used instead (covering the case when "HKEY..WARE\Cygwin\setup" is missing but "HKEY..WARE\Wow6432Node\Cygwin\setup" exists). Should probably test that. Useful reading: http://windowsitpro.com/systems-management/whats-wow6432node-under-hkeylocalmachinesoftware-registry-subkey http://msdn.microsoft.com/en-us/library/windows/desktop/aa384129(v=vs.85).aspx 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] [plugin] (JENKINS-7303) Could not find cygpath on Win64 machine
Neeme Praks edited a comment on JENKINS-7303 Could not find cygpath on Win64 machine I added a comment under JENKINS-20364, but it is somewhat relevant also for this issue, so I'm copying parts of it here. I'm not sure the change made in JENKINS-7303 actually fixes anything (did someone test this?). The "Wow6432Node" subkey seems to be implementation detail of Windows registry and the application code should not care about it. Instead, it should use the relevant access bit (as described above). Also, my tests have shown that with current code, 64bit JVM running on 64bit Windows can access "HKEY..WARE\Cygwin\setup". The problem is with 32bit JVM running on 64bit Windows: it looks up "HKEY..WARE\Cygwin\setup" but Windows translates that into "HKEY..WARE\Wow6432Node\Cygwin\setup" (which is missing). And, when it tries to access "HKEY..WARE\Wow6432Node\Cygwin\setup", Windows probably translates that into "HKEY..WARE\Wow6432Node\Wow6432Node\Cygwin\setup" which is also missing. So 32bit JVM running on 64bit Windows has no access to "HKEY..WARE\Cygwin\setup" unless it specifies the special KEY_WOW64_64KEY flag. I'm not sure if the other scenario of 64bit JVM running on 64bit Windows trying to look up "HKEY..WARE\Wow6432Node\Cygwin\setup" works or KEY_WOW64_32KEY flag should be used instead (covering the case when "HKEY..WARE\Cygwin\setup" is missing but "HKEY..WARE\Wow6432Node\Cygwin\setup" exists). Should probably test that. Assuming that the fix made here actually works (otherwise it would have been re-opened long ago), my second comment can be ignored 64bit JVM running on 64bit Windows looking up "HKEY..WARE\Wow6432Node\Cygwin\setup" probably works. The problem is that this fix does not work for 32bit JVM running on 64bit Windows (see my comment on JENKINS-20364 for details). Useful reading: http://windowsitpro.com/systems-management/whats-wow6432node-under-hkeylocalmachinesoftware-registry-subkey http://msdn.microsoft.com/en-us/library/windows/desktop/aa384129(v=vs.85).aspx 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] [plugin] (JENKINS-7303) Could not find cygpath on Win64 machine
Neeme Praks reopened JENKINS-7303 Could not find cygpath on Win64 machine Reopening as the solution does not work for 32bit JVM running on 64bit Windows. I'm not sure if this should be solved here or under JENKINS-20364. Feel free to resolve if JENKINS-20364 seems more appropriate. Change By: Neeme Praks (01/Oct/14 3:28 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] [git] (JENKINS-24786) Since 2.2.6, environment variables are not expanded in git publisher
Carlos Alexandre commented on JENKINS-24786 Since 2.2.6, environment variables are not expanded in git publisher I just rolled back to 2.2.4 because of this issue. It is confirmed working in 2.2.4. 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] (JENKINS-23606) Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits
Eric Tucker commented on JENKINS-23606 Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits Any updates? Noticed this bug myself 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] [pmd] (JENKINS-24873) Wrong number of new warnings
Ulli Hafner commented on JENKINS-24873 Wrong number of new warnings Do you have some warnings in the same line and 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] [p4] (JENKINS-24855) Build Review not working with Swarm
Paul Allen commented on JENKINS-24855 Build Review not working with Swarm It looks like the '=' is missing on the review attribute. It should read 'review=247': .../review/build?status=shelvedreview=247pass=... 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-10923) /safeRestart doesn't work on AIX
Daniel Beck resolved JENKINS-10923 as Incomplete /safeRestart doesnt work on AIX No response in several weeks to comment asking for updated information, so resolving as Incomplete. If this issue occurs on a recent version of Jenkins, please file a new issue. Change By: Daniel Beck (01/Oct/14 5:24 PM) 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] [copyartifact] (JENKINS-12379) Archive the artifacts should allow specifying the target artifacts path
Daniel Beck assigned JENKINS-12379 to Unassigned Archive the artifacts should allow specifying the target artifacts path I guess not. Change By: Daniel Beck (01/Oct/14 5:48 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] [p4] (JENKINS-24855) Build Review not working with Swarm
Michael Rose commented on JENKINS-24855 Build Review not working with Swarm Whoops! Looks like this was a solid PEBCAK case. Thanks for correcting me, it works fine now after making that change. 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] [gradle-jpi-plugin] (JENKINS-24298) Localizer is not generating Messages classes
Daniel Spilker closed JENKINS-24298 as Fixed Localizer is not generating Messages classes Fixed in 0.6.0. Change By: Daniel Spilker (01/Oct/14 6:10 PM) Status: Resolved Closed 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] [gradle-jpi-plugin] (JENKINS-21431) Build fails with newer versions of core
Daniel Spilker closed JENKINS-21431 as Fixed Build fails with newer versions of core Change By: Daniel Spilker (01/Oct/14 6:09 PM) Status: Resolved Closed 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] [gradle-jpi-plugin] (JENKINS-23603) instance-identity dependency is missing
Daniel Spilker closed JENKINS-23603 as Fixed instance-identity dependency is missing Fixed in 0.6.0. Change By: Daniel Spilker (01/Oct/14 6:10 PM) Status: Resolved Closed 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] [gradle-jpi-plugin] (JENKINS-19942) gradle/groovy plugin cannot build test task
Daniel Spilker closed JENKINS-19942 as Fixed gradle/groovy plugin cannot build test task Fixed in 0.6.0. Change By: Daniel Spilker (01/Oct/14 6:11 PM) Status: Resolved Closed 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] [gradle-jpi-plugin] (JENKINS-24808) PluginFirstClassLoader not supported by gradle-jpi-plugin
Daniel Spilker closed JENKINS-24808 as Fixed PluginFirstClassLoader not supported by gradle-jpi-plugin Fixed in 0.6.0. Change By: Daniel Spilker (01/Oct/14 6:10 PM) Status: Resolved Closed 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] [config-file-provider] (JENKINS-22939) Temporary config file should not be world-readable
Dominik Bartholdi commented on JENKINS-22939 Temporary config file should not be world-readable what would you expect? owner:read/write, group: read "chmod 0640"? (-rw-r) owner:read/write, group: nothing "chmod 0600"? (-rw--) I would go for option 1 - WDYT? 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] [config-file-provider] (JENKINS-22939) Temporary config file should not be world-readable
Dominik Bartholdi edited a comment on JENKINS-22939 Temporary config file should not be world-readable what would you expect? owner:read/write, group: read "chmod 0640"? (rw-r) owner:read/write, group: nothing "chmod 0600"? (rw--) I would go for option 1 - WDYT? 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] [mercurial] (JENKINS-24953) Filenames with accents cause the changelog to appear empty
Samuel Delisle created JENKINS-24953 Filenames with accents cause the changelog to appear empty Issue Type: Bug Assignee: Jesse Glick Components: mercurial Created: 01/Oct/14 6:34 PM Description: If a file with an accent (e.g. "é") is part of a list of changes, the changelog.xml file will be apparently unreadable. For example, the character "é" ends up as 0xE9 in the xml file. Jenkins then shows No changes. in the build information. By manually editing changelog.xml and replacing 0xE9 by "é", a simple refresh of the page shows the proper changes. Note that accents in changeset comments are handled correctly. I set the priority to "Major" because one of the consequences of this is that no e-mails are sent because it thinks there are no changes, therefore nobody made changes. The job console output shows: An attempt to send an e-mail to empty list of recipients, ignored. This can mean a build failure without notification (which was our case). Whether this is a minor or major loss of function depends on the usage, I guess. Environment: Jenkins 1.480.3 + Mercurial plugin 1.45 or Jenkins 1.565.2 + Mercurial plugin 1.50 Project: Jenkins Labels: mercurial encoding changelog Priority: Major Reporter: Samuel Delisle 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-19192) CLI login command fails on Windows
SCM/JIRA link daemon commented on JENKINS-19192 CLI login command fails on Windows Code changed in jenkins User: Jesse Glick Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/47c254aa32ef8f846f07a0200dee5b4bf10571c1 Log: JENKINS-19192 Using JNR 3.0.1 which includes JNR-FFI 1.0.7; 1.0.6 has the backported fix for Guava #1505, the root cause. So this upgrade ought to prevent a recurrence of the issue in case some other code refers to JNR from the CLI. (As yet untested, and we do not especially want to send JNR over the CLI channel anyway for performance reasons.) 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-21984) java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014
SCM/JIRA link daemon commented on JENKINS-21984 java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014 Code changed in jenkins User: Jesse Glick Path: test/src/test/java/hudson/model/UpdateSiteTest.java http://jenkins-ci.org/commit/jenkins/1d29041372aeb77cab5a6aa4ce758ba5133c2f51 Log: JENKINS-21984 Disabling cert check on updateDirectlyWithJson since the certificate is now expired, and it is no good to have a test which is known to start failing at a particular time in the future! (cherry picked from commit 334ce1be691c96ad63642c8301c4f0417a0705c3) 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-15156) Builds disappear from build history after completion
SCM/JIRA link daemon commented on JENKINS-15156 Builds disappear from build history after completion Code changed in jenkins User: Jesse Glick Path: test/src/test/groovy/hudson/model/AbstractProjectTest.groovy http://jenkins-ci.org/commit/jenkins/389a565de417170f586830ee9fa7a7ec9749fc68 Log: JENKINS-10615 AbstractProjectTest.testWorkspaceLock frequently fails on jenkins.ci due to InterruptedException in HudsonTestCase.setUp. Possibly because it is sorted after JENKINS-15156 testGetBuildAfterGC and the test suite times out. (cherry picked from commit 85e9e126773c0bb20a8529a2e6591dde17d7e209) 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] [concurrent-build] (JENKINS-10615) Workspaces seem to be removed prematurely on concurrent jobs
SCM/JIRA link daemon commented on JENKINS-10615 Workspaces seem to be removed prematurely on concurrent jobs Code changed in jenkins User: Jesse Glick Path: test/src/test/groovy/hudson/model/AbstractProjectTest.groovy http://jenkins-ci.org/commit/jenkins/389a565de417170f586830ee9fa7a7ec9749fc68 Log: JENKINS-10615 AbstractProjectTest.testWorkspaceLock frequently fails on jenkins.ci due to InterruptedException in HudsonTestCase.setUp. Possibly because it is sorted after JENKINS-15156 testGetBuildAfterGC and the test suite times out. (cherry picked from commit 85e9e126773c0bb20a8529a2e6591dde17d7e209) 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-24825) Missing build history moving a job when BuildDir is set to a custom location
Daniel Beck updated JENKINS-24825 Missing build history moving a job when BuildDir is set to a custom location Change By: Daniel Beck (01/Oct/14 6:58 PM) Labels: folders lts-candidate 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-11543) UTF-8 encoding issue of build parameters as soon as including File parameter
Daniel Beck updated JENKINS-11543 UTF-8 encoding issue of build parameters as soon as including File parameter Change By: Daniel Beck (01/Oct/14 6:58 PM) Labels: lts-candidate 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-24458) SomeAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
Daniel Beck updated JENKINS-24458 SomeAction doesnt have @ExportedBean so cannot write hudson.model.Actionable.actions Change By: Daniel Beck (01/Oct/14 6:58 PM) Labels: lts-candidate 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-23471) Channel reader thread consumes all CPUs
Daniel Beck updated JENKINS-23471 Channel reader thread consumes all CPUs Change By: Daniel Beck (01/Oct/14 6:59 PM) Labels: lts-candidate remoting 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-7478) Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type Execute Windows batch command
Daniel Beck updated JENKINS-7478 Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type Execute Windows batch command Change By: Daniel Beck (01/Oct/14 6:58 PM) Labels: lts-candidate 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-24614) unknown format type on console output
Daniel Beck updated JENKINS-24614 unknown format type on console output Change By: Daniel Beck (01/Oct/14 6:59 PM) Labels: lts-candidate 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.
