[JIRA] [junit-plugin] (JENKINS-10234) Junit result archiver getting stuck for a long time in concurrent builds
Henrik Skupin commented on JENKINS-10234 Junit result archiver getting stuck for a long time in concurrent builds There is version 1.565.3 LTS to be scheduled for Oct 1st. Not sure when fixes are taking into consideration for LTS releases. Anything else beside the keyword we could try to get it in? The next major version bump for LTS will happen end of Oct, where this might be 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-13153) "Upgrade Automatically" does not seem to work on Windows
Kristoffer Peterhänsel commented on JENKINS-13153 "Upgrade Automatically" does not seem to work on Windows Not a clue. I no longer work at the place where we had that installation. And don't really have anywhere to replicate the setup either. This message is automatically generated by JIRA. 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] [pretested-integration] (JENKINS-24907) HTML formatting in build description
Bue Petersen created JENKINS-24907 HTML formatting in build description Issue Type: Bug Assignee: Praqma Support Attachments: Screenshot from 2014-09-29 130618.png Components: pretested-integration Created: 29/Sep/14 11:09 AM Description: "" HTML tag is shown in build description in some cases. Environment: pretested-integration plugin 2.1.1 Project: Jenkins Priority: Trivial Reporter: Bue Petersen This message is automatically generated by JIRA. 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] [promoted-builds] (JENKINS-24908) Variable acceptance jenkins system user with Promote
Guillaume Sanchez created JENKINS-24908 Variable acceptance jenkins system user with Promote Issue Type: Bug Assignee: Unassigned Attachments: with_ANONYMOUS_user.png, with_SYSTEM_user.png Components: promoted-builds Created: 29/Sep/14 11:11 AM Description: Hi , Since my Windows Service, the Promote performer is alone is via the SYSTEM user (before it was ANONYMOUS ) while the parameters passed to the ant script are ignored ! I have to manually restart the Promote for the settings to take effect . The ANT script did not change , only versions JENKINS and " promote- builds" have been updated Thx Project: Jenkins Labels: plugin jenkins Priority: Major Reporter: Guillaume Sanchez This message is automatically generated by JIRA. 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] [pretested-integration] (JENKINS-24907) HTML formatting in build description ( our case 12074 )
Jens Brejner updated JENKINS-24907 HTML formatting in build description ( our case 12074 ) Change By: Jens Brejner (29/Sep/14 11:14 AM) Summary: HTML formatting in build description ( our case 12074 ) This message is automatically generated by JIRA. 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] [pretested-integration] (JENKINS-24907) HTML formatting in build description ( our case 12074 )
Jens Brejner commented on JENKINS-24907 HTML formatting in build description ( our case 12074 ) Have you checked against this issue https://issues.jenkins-ci.org/browse/JENKINS-22028 ? This message is automatically generated by JIRA. 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] [promoted-builds] (JENKINS-24908) Variable acceptance jenkins system user with Promote
Guillaume Sanchez updated JENKINS-24908 Variable acceptance jenkins system user with Promote Change By: Guillaume Sanchez (29/Sep/14 11:16 AM) Description: Hi ,Since my Windows Service, the Promote performer is alone is via the SYSTEM user (before it was ANONYMOUS ) while the parameters passed to the ant script are ignored !I have to manually restart the Promote for the settings to take effect .The ANT script did not change , only versions JENKINS and " promote- builds" have been updatedThx Jenkins : v1.581Promote-build : v2.18 This message is automatically generated by JIRA. 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] [pretested-integration] (JENKINS-24909) Source branch not checked against "Branch Specifier"
Bue Petersen created JENKINS-24909 Source branch not checked against "Branch Specifier" Issue Type: Bug Assignee: Praqma Support Components: pretested-integration Created: 29/Sep/14 11:19 AM Description: The Pretested Integration plugin uses 'Branch Specifier' from the Git plugin as source branch, and 'Integration branch' field in the Pretested Integration plugin as destination. When the integration job uses polling, the job only runs on branches that matches the "Branch Specifier", so only those are integrated. When job is started in another way, eg. by upstream job with at Git commit SHA passed, it may try to integrate other branches (the one the passed git commit SHA lives on). The Pretested Integration plugin must never try to integrate a branch that does not match the source patterin in 'Branch specifier'. Reproduce the problem: job1: poll repository, branch specifier any branch. starts job1 with paramter git commit that was build job2: branch specifier "origin*/ready_", integrate branch: 'master' If job1 sees master, job2 to tries to integrate master (but fails - master can never be integrated to master). If job1 sees branch 'this-branch-should-not-integrate', it triggers job2 which tries to integration 'this-branch-should-not-integrate' though it does not match 'Branch Specifier' of job2. Environment: pretested-integration-plug 2.1.1 Project: Jenkins Priority: Major Reporter: Bue Petersen This message is automatically generated by JIRA. 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] [pretested-integration] (JENKINS-24909) Source branch not checked against "Branch Specifier" ( our case 12075)
Bue Petersen updated JENKINS-24909 Source branch not checked against "Branch Specifier" ( our case 12075) Change By: Bue Petersen (29/Sep/14 11:23 AM) Summary: Source branch not checked against "Branch Specifier" ( our case 12075) This message is automatically generated by JIRA. 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] [ownership-plugin] (JENKINS-24475) Managing ownership not possible
SCM/JIRA link daemon resolved JENKINS-24475 as Fixed Managing ownership not possible Change By: SCM/JIRA link daemon (29/Sep/14 11:58 AM) Status: In Progress 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] [ec2] (JENKINS-19956) Error launching slave using jenkins-ec2 plugin
Arcadiy Ivanov commented on JENKINS-19956 Error launching slave using jenkins-ec2 plugin I can confirm exactly the same issue with version 1.24, AMI ami-0c842d64 on VPC. This message is automatically generated by JIRA. 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] [ownership-plugin] (JENKINS-24475) Managing ownership not possible
SCM/JIRA link daemon commented on JENKINS-24475 Managing ownership not possible Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/security/authorizeproject/OwnershipAuthorizeProjectStrategy.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/userFilters/AccessRightsFilter.java http://jenkins-ci.org/commit/ownership-plugin/ff1ef42857904efe7ed886c0f39ed48a0f50a5b3 Log: [FIXED JENKINS-24475] - Properly handle UsernameNotFoundException on impersonation This change allows to avoid non-existent users introduced since 1.564.1. The change also handles a possible issue in OwnershipAuthorizeProjectStrategy. Signed-off-by: Oleg Nenashev This message is automatically generated by JIRA. 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] [ownership-plugin] (JENKINS-24475) Managing ownership not possible
SCM/JIRA link daemon commented on JENKINS-24475 Managing ownership not possible Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/OwnershipDescription.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPlugin.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/OwnershipItemListener.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/security/authorizeproject/OwnershipAuthorizeProjectStrategy.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/AbstractOwnershipHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/HTMLFormatter.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/OwnershipDescriptionHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/UserCollectionFilter.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/UserStringFormatter.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/UserWrapper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/userFilters/AccessRightsFilter.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/userFilters/IUserFilter.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/userFilters/UserComparator.java http://jenkins-ci.org/commit/ownership-plugin/0b1dac28f29d31b544cf2778c93c25c64a6770a5 Log: Merge pull request #27 from synopsys-arc-oss/JENKINS-24475 JENKINS-24475 and refactoring Compare: https://github.com/jenkinsci/ownership-plugin/compare/0581a8055ffd...0b1dac28f29d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-19956) Error launching slave using jenkins-ec2 plugin
Arcadiy Ivanov commented on JENKINS-19956 Error launching slave using jenkins-ec2 plugin Authenticating as ec2-user take over connection Executing init script ERROR: Error during SCP transfer. java.io.IOException: Error during SCP transfer. at com.trilead.ssh2.SCPClient.put(SCPClient.java:523) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launch(EC2UnixLauncher.java:108) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:101) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:228) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.io.IOException: Remote scp terminated unexpectedly. at com.trilead.ssh2.SCPClient.readResponse(SCPClient.java:50) at com.trilead.ssh2.SCPClient.sendBytes(SCPClient.java:140) at com.trilead.ssh2.SCPClient.put(SCPClient.java:519) ... 8 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-19956) Error launching slave using jenkins-ec2 plugin
Arcadiy Ivanov edited a comment on JENKINS-19956 Error launching slave using jenkins-ec2 plugin Authenticating as ec2-user take over connection Executing init script ERROR: Error during SCP transfer. java.io.IOException: Error during SCP transfer. at com.trilead.ssh2.SCPClient.put(SCPClient.java:523) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launch(EC2UnixLauncher.java:108) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:101) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:228) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.io.IOException: Remote scp terminated unexpectedly. at com.trilead.ssh2.SCPClient.readResponse(SCPClient.java:50) at com.trilead.ssh2.SCPClient.sendBytes(SCPClient.java:140) at com.trilead.ssh2.SCPClient.put(SCPClient.java:519) ... 8 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-19956) Error launching slave using jenkins-ec2 plugin
Arcadiy Ivanov updated JENKINS-19956 Error launching slave using jenkins-ec2 plugin Change By: Arcadiy Ivanov (29/Sep/14 12:01 PM) Environment: Jenkins Version: 1.525 , 1.565.1 EC2 Version: 1.18 , 1.24 This message is automatically generated by JIRA. 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] [ownership-plugin] (JENKINS-24475) Managing ownership not possible
Oleg Nenashev updated JENKINS-24475 Managing ownership not possible Sorry for a long resolution delay. Too many business trips. The issue has been caused by "unknown" user, which became invalid in several core's Security Realms. I've attached the SNAPSHOT version of the plugin with the fix. Please confirm it works on your installation. Change By: Oleg Nenashev (29/Sep/14 12:09 PM) Attachment: ownership.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-24676) Region list not being populated when keys are entered
Arcadiy Ivanov commented on JENKINS-24676 Region list not being populated when keys are entered FYI, this can also happen if AWS keys are correct, but IAM is used and permissions in the policy are lacking. The exception then looks like this: WARNING: Error while serving http://ci.labs.dev.servicemesh.com:8080/descriptorByName/hudson.plugins.ec2.AmazonEC2Cloud/fillRegionItems java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865)
[JIRA] [credentials-binding] (JENKINS-24910) Username/password to support separate env variables
William Bernardet created JENKINS-24910 Username/password to support separate env variables Issue Type: Improvement Assignee: Jesse Glick Components: credentials-binding Created: 29/Sep/14 12:16 PM Description: Currently the plugin will generate a single environment variable based on the name give set as this: =username:password Would it be possible to have an option to split it into two distinct environment variables: _USERNAME=username _PASSWORD=password This would ease the usage of the plugin as most of the tool requiring a username password would ask them separatly. Project: Jenkins Priority: Minor Reporter: William Bernardet This message is automatically generated by JIRA. 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-14332) Repeated channel/timeout errors from Jenkins slave
Oleg Nenashev assigned JENKINS-14332 to Unassigned Repeated channel/timeout errors from Jenkins slave Change By: Oleg Nenashev (29/Sep/14 12:16 PM) Assignee: Oleg Nenashev This message is automatically generated by JIRA. 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-24645) Portions of config go missing
Oleg Nenashev commented on JENKINS-24645 Portions of config go missing @Chris, Any updates? This message is automatically generated by JIRA. 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] [prioritysorter] (JENKINS-24911) NullpointerException in AdvancedQueueSorterQueueListener and AdvancedQueueSorter on startup
Marcus Philip created JENKINS-24911 NullpointerException in AdvancedQueueSorterQueueListener and AdvancedQueueSorter on startup Issue Type: Bug Assignee: Magnus Sandberg Components: prioritysorter Created: 29/Sep/14 12:34 PM Description: NullPointerExceptions during startup. They are caught by calling class, so not major but still, we do not want to log warnings for normal things that can happen. There is a null check in AdvancedQueueSorterQueueListener.onEnterBuildable() but not in the other three event methods in the class. In AdvancedQueueSorter I see newer code that might have fixed this? Sep 29, 2014 10:13:58 AM hudson.model.Queue$BlockedItem enter WARNING: QueueListener failed while processing hudson.model.Queue$BlockedItem:hudson.model.FreeStyleProject@470c5677[alo_integration_build]:471 java.lang.NullPointerException at jenkins.advancedqueue.sorter.AdvancedQueueSorterQueueListener.onEnterBlocked(AdvancedQueueSorterQueueListener.java:61) at hudson.model.Queue$BlockedItem.enter(Queue.java:1712) at hudson.model.Queue.load(Queue.java:372) at hudson.model.Queue.init(Queue.java:2075) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Sep 29, 2014 11:05:45 AM hudson.model.Queue$LeftItem enter WARNING: QueueListener failed while processing hudson.model.Queue$LeftItem:hudson.model.FreeStyleProject@185eede4[Build-tivotool_Chips]:495 java.lang.NullPointerException at jenkins.advancedqueue.sorter.AdvancedQueueSorter.onLeft(AdvancedQueueSorter.java:131) at jenkins.advancedqueue.sorter.AdvancedQueueSorterQueueListener.onLeft(AdvancedQueueSorterQueueListener.java:47) at hudson.model.Queue$LeftItem.enter(Queue.java:1884) at hudson.model.Queue.onStartExecuting(Queue.java:914) at hudson.model.Executor.run(Executor.java:207) Environment: Jenkins ver. 1.565 Priority Sorter Plugin 2.6 Project: Jenkins Labels: nullpointer Priority: Minor 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] [core] (JENKINS-15283) The node does not return back online as there is enough disk space again
Alexander Gnuschenko commented on JENKINS-15283 The node does not return back online as there is enough disk space again Hello! Sorry, i miss message 02/Sep/14 8:39 AM, and discover it only when recive mail notification with message from 22/Sep/14 8:55 PM. The problem solved with slave version 2.43 (and problem was in version afaik 2.41, or similar.) 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] [git] (JENKINS-24833) Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds
Loren Klingman
commented on JENKINS-24833
Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds
Digging through source code
Crap4J returns false on failure https://svn.jenkins-ci.org/trunk/hudson/plugins/crap4j/src/main/java/hudson/plugins/crap4j/Crap4JPublisher.java
if (0 == reports.length) {
log(logger, "No crap4j report files were found. Configuration error?");
return false;
}
Where xUnit returns true and sets the build result to failure
https://github.com/jenkinsci/xunit-plugin/blob/a0ad57db81ef5a91162dbfa7190a1a8bcb838edd/src/main/java/org/jenkinsci/plugins/xunit/XUnitProcessor.java#L83
GitPublisher is looking at the build result:
https://github.com/jenkinsci/git-plugin/blob/cebb9da131fa6c9e07ec9e6ff71ec89aa58fdd6f/src/main/java/hudson/plugins/git/GitPublisher.java#L203
Theoretically the false result is canContinue:
https://github.com/jenkinsci/jenkins/blob/a197999c6c57ad761f7242b9f6b28c0333175601/core/src/main/java/hudson/model/AbstractBuild.java#L781
But in actuality all build steps run even if one fails (though a final result of false is reported):
https://github.com/jenkinsci/jenkins/blob/a197999c6c57ad761f7242b9f6b28c0333175601/core/src/main/java/hudson/model/AbstractBuild.java#L724
It looks like their is absolutely no way that git-publish could know that Crap4J failed unless Crap4J changes the build result like all the other plugins.
Thanks for your help in testing things and helping me narrow this to a point that I could find the actual problem.
I'll reference this in a Crap4J bug. I would try to fix it since it should be a one line change, but that plugin is still on an old SVN structure, and I'm not familiar with building Jenkins plugins from scratch.
This message is automatically generated by JIRA.
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-24645) Portions of config go missing
Chris Suich commented on JENKINS-24645 Portions of config go missing Hey @Oleg - sorry for the quiet period. We haven't encountered the issue since I filed this bug. If you'd like, I can close the issue and re-open it if we run into it again. This message is automatically generated by JIRA. 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] [promoted-builds] (JENKINS-24908) Variable acceptance jenkins system user with Promote
Guillaume Sanchez updated JENKINS-24908 Variable acceptance jenkins system user with Promote Change By: Guillaume Sanchez (29/Sep/14 12:46 PM) Description: Hi , ==> FIX with promote-builds-plugin v2.15(downgrade) <== Since my Windows Service, the Promote performer is alone is via the SYSTEM user (before it was ANONYMOUS ) while the parameters passed to the ant script are ignored !I have to manually restart the Promote for the settings to take effect .The ANT script did not change , only versions JENKINS and " promote- builds" have been updatedThxJenkins : v1.581Promote-build : v2.18 This message is automatically generated by JIRA. 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] [crap4j] (JENKINS-24912) Crap4J does not correctly fail the build when reporting fails
Loren Klingman
created JENKINS-24912
Crap4J does not correctly fail the build when reporting fails
Issue Type:
Bug
Assignee:
dlindner
Components:
crap4j
Created:
29/Sep/14 12:47 PM
Description:
For more details see this thread:
https://issues.jenkins-ci.org/browse/JENKINS-24833
When Crap4J has a failure and can't find the report files, it returns false instead of setting build status to build.FAILURE. This results in Jenkins eventually recognizing a failed build, but allows all other post build steps to run including steps that are only supposed to run with a successful build. I think this should be a one line fix to add:
build.setResult(Result.FAILURE);
and then return true instead of false.
Crap4J returns false on failure https://svn.jenkins-ci.org/trunk/hudson/plugins/crap4j/src/main/java/hudson/plugins/crap4j/Crap4JPublisher.java
if (0 == reports.length) { log(logger, "No crap4j report files were found. Configuration error?"); return false; }
Where xUnit returns true and sets the build result to failure
https://github.com/jenkinsci/xunit-plugin/blob/a0ad57db81ef5a91162dbfa7190a1a8bcb838edd/src/main/java/org/jenkinsci/plugins/xunit/XUnitProcessor.java#L83
GitPublisher is looking at the build result to determine a successful result or not:
https://github.com/jenkinsci/git-plugin/blob/cebb9da131fa6c9e07ec9e6ff71ec89aa58fdd6f/src/main/java/hudson/plugins/git/GitPublisher.java#L203
Theoretically the false result is canContinue:
https://github.com/jenkinsci/jenkins/blob/a197999c6c57ad761f7242b9f6b28c0333175601/core/src/main/java/hudson/model/AbstractBuild.java#L781
But in actuality all build steps run even if one fails (though a final result of false is reported):
https://github.com/jenkinsci/jenkins/blob/a197999c6c57ad761f7242b9f6b28c0333175601/core/src/main/java/hudson/model/AbstractBuild.java#L724
It looks like their is absolutely no way that git-publish could know that Crap4J failed unless Crap4J changes the build result when it has a failure.
Environment:
System Properties
Name ↓ Value
executable-war /usr/share/jenkins/jenkins.war
file.encoding UTF-8
file.encoding.pkg sun.io
file.separator /
hudson.diyChunking true
java.awt.graphicsenv sun.awt.X11GraphicsEnvironment
java.awt.headless true
java.awt.printerjob sun.print.PSPrinterJob
java.class.path /usr/share/jenkins/jenkins.war
java.class.version 50.0
java.endorsed.dirs /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/endorsed
java.ext.dirs /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/ext:/usr/java/packages/lib/ext
java.home /usr/lib/jvm/java-6-openjdk-amd64/jre
java.io.tmpdir /tmp
java.library.path /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib
java.runtime.name OpenJDK Runtime Environment
java.runtime.version 1.6.0_32-b32
java.specification.name Java Platform API Specification
java.specification.vendor Sun Microsystems Inc.
java.specification.version 1.6
java.vendor Sun Microsystems Inc.
java.vendor.url http://java.sun.com/
java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi
java.version 1.6.0_32
java.vm.info mixed mode
java.vm.name OpenJDK 64-Bit Server VM
java.vm.specification.name Java Virtual Machine Specification
java.vm.specification.vendor Sun Microsystems Inc.
java.vm.specification.version 1.0
java.vm.vendor Sun Microsystems Inc.
java.vm.version 23.25-b01
jna.platform.library.path /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib
line.separator
mail.smtp.sendpartial true
mail.smtps.sendpartial true
os.arch amd64
os.name Linux
os.version 3.2.0-60-generic
path.separator :
sun.arch.data.model 64
sun.boot.class.path /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/resources.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/rt.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/sunr
[JIRA] [core] (JENKINS-24645) Portions of config go missing
Oleg Nenashev resolved JENKINS-24645 as Cannot Reproduce Portions of config go missing OK, please re-open it if you hit it again. In any case, job-config-history will save you much time if it appears. Change By: Oleg Nenashev (29/Sep/14 12:51 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. 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] [crap4j] (JENKINS-24833) Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds
Mark Waite updated JENKINS-24833 Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds Change By: Mark Waite (29/Sep/14 1:06 PM) Component/s: crap4j Component/s: git This message is automatically generated by JIRA. 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] [plot] (JENKINS-23856) Plots from CSV files do not work with matrix / multi-configuration builds
Sebastian Schuberth resolved JENKINS-23856 as Duplicate Plots from CSV files do not work with matrix / multi-configuration builds https://issues.jenkins-ci.org/browse/JENKINS-24666 Change By: Sebastian Schuberth (29/Sep/14 1:42 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [plot] (JENKINS-23856) Plots from CSV files do not work with matrix / multi-configuration builds
Sebastian Schuberth edited a comment on JENKINS-23856 Plots from CSV files do not work with matrix / multi-configuration builds Got fixed in the duplicate issue. This message is automatically generated by JIRA. 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] [prioritysorter] (JENKINS-24618) Absolute priority not working
Jay Berkenbilt commented on JENKINS-24618 Absolute priority not working I'm finding priorities ignored in absolute mode as well. I did essentially the same test: vanilla install of Jenkins with only the priority queue sorter, one executor, three jobs that sleep. I see the same thing: jobs are run in fifo order. I would love to know what configuration area Markus had and whether Thomas Westling is still seeing the problem. I'm running 1.565.2 (LTS) and plugin 2.8. This message is automatically generated by JIRA. 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] [customtools-plugin] (JENKINS-24853) custom tools plugin doesn't work with matrix job
Oleg Nenashev updated JENKINS-24853 custom tools plugin doesn't work with matrix job Seems that the old configuration has been loaded for the job after the plugin's update. PR with the fix:https://github.com/jenkinsci/customtools-plugin/pull/22 This message is automatically generated by JIRA. 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] [customtools-plugin] (JENKINS-24853) custom tools plugin doesn't work with matrix job
Oleg Nenashev started work on JENKINS-24853 custom tools plugin doesn't work with matrix job Change By: Oleg Nenashev (29/Sep/14 1:54 PM) Status: Open In Progress This message is automatically generated by JIRA. 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] [customtools-plugin] (JENKINS-24853) custom tools plugin doesn't work with matrix job
SCM/JIRA link daemon commented on JENKINS-24853 custom tools plugin doesn't work with matrix job Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/cloudbees/jenkins/plugins/customtools/CustomToolInstallWrapper.java http://jenkins-ci.org/commit/customtools-plugin/41037bb1332f319860561d6cee4126927e244407 Log: [FIXED JENKINS-24853] - Handle null multiConfigOptions Signed-off-by: Oleg Nenashev This message is automatically generated by JIRA. 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] [customtools-plugin] (JENKINS-24853) custom tools plugin doesn't work with matrix job
SCM/JIRA link daemon resolved JENKINS-24853 as Fixed custom tools plugin doesn't work with matrix job Change By: SCM/JIRA link daemon (29/Sep/14 1:57 PM) Status: In Progress 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] [customtools-plugin] (JENKINS-24853) custom tools plugin doesn't work with matrix job
SCM/JIRA link daemon commented on JENKINS-24853 custom tools plugin doesn't work with matrix job Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/cloudbees/jenkins/plugins/customtools/CustomToolInstallWrapper.java http://jenkins-ci.org/commit/customtools-plugin/c061810db486bb7e5a4d41bad1a041f43bf05682 Log: Merge pull request #22 from synopsys-arc-oss/JENKINS-24853 [FIXED JENKINS-24853] - Handle null multiConfigOptions Compare: https://github.com/jenkinsci/customtools-plugin/compare/6f337351a745...c061810db486 This message is automatically generated by JIRA. 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-23966) Master labels is disappeared in case system configuration has been changed
Oleg Nenashev assigned JENKINS-23966 to Unassigned Master labels is disappeared in case system configuration has been changed Change By: Oleg Nenashev (29/Sep/14 1:59 PM) Assignee: Oleg Nenashev This message is automatically generated by JIRA. 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-23966) Master labels is disappeared in case system configuration has been changed
Oleg Nenashev commented on JENKINS-23966 Master labels is disappeared in case system configuration has been changed Forgot to remove the assignment This message is automatically generated by JIRA. 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] [prioritysorter] (JENKINS-24618) Absolute priority not working
Markus commented on JENKINS-24618 Absolute priority not working I had global priorities set up in http://jenkins:8080/advanced-build-queue/. These priorities overrules the job specific priorities. This message is automatically generated by JIRA. 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-23657) user.gif icon background is not transparent
SCM/JIRA link daemon resolved JENKINS-23657 as Fixed user.gif icon background is not transparent Change By: SCM/JIRA link daemon (29/Sep/14 2:11 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23657) user.gif icon background is not transparent
SCM/JIRA link daemon commented on JENKINS-23657 user.gif icon background is not transparent Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/OwnershipAction.java http://jenkins-ci.org/commit/ownership-plugin/9ddad5301781cb4b807612a8598018d4f878fcb5 Log: [FIXED JENKINS-23657] - Switch from user.gif to user.png Signed-off-by: Oleg Nenashev This message is automatically generated by JIRA. 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-24110) NPE in hudson.model.Executor when a task creates null Executable
Oleg Nenashev resolved JENKINS-24110 as Fixed NPE in hudson.model.Executor when a task creates null Executable Fixed in jenkins-1.577. I've marked the issue as lts-candidate Change By: Oleg Nenashev (29/Sep/14 2:16 PM) Status: In Progress 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] [matrix-project] (JENKINS-18164) Matrix Jobs Do Not Get Run When Updating a Dynamic Axis
Oleg Nenashev commented on JENKINS-18164 Matrix Jobs Do Not Get Run When Updating a Dynamic Axis The issue in the core has been released in jenkins-1.577 A PR for JENKINS-19179 (https://github.com/jenkinsci/matrix-project-plugin/pull/5) should resolve this issue 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] [ssh] (JENKINS-24913) SSH Plugin displays password parameter values unencrypted in log
Pietro Descombes created JENKINS-24913 SSH Plugin displays password parameter values unencrypted in log Issue Type: Bug Assignee: Unassigned Components: ssh Created: 29/Sep/14 2:24 PM Description: When running a parameterized build of type Execute shell script on remote host using ssh, it logs in the console output all the parameters that are used in the script with their values. This is a problem with Password Parameter types, they should be hidden. This is a serious security issue, passwords must never be logged anywhere. Project: Jenkins Priority: Critical Reporter: Pietro Descombes This message is automatically generated by JIRA. 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] [prioritysorter] (JENKINS-24618) Absolute priority not working
Tomas Westling commented on JENKINS-24618 Absolute priority not working I still see the problem come and go, both with the advanced and the old priority mechanism. When I debug the plugin, everything works like it should, so I haven't been able to get any closer to what the problem is. This message is automatically generated by JIRA. 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 updated JENKINS-24873 Wrong number of new warnings Change By: Sergey Ryazantsev (29/Sep/14 2:51 PM) Environment: Jenkins v. 1.554.2PMD Plugin v. 3.38. Static Code Analysis Collector Plugin Plugins v. 1.58 This message is automatically generated by JIRA. 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] [pretested-integration] (JENKINS-24907) HTML formatting in build description ( our case 12074 )
Daniel Beck edited a comment on JENKINS-24907 HTML formatting in build description ( our case 12074 ) This is the bug, as it assumes the current formatter is HTML: https://github.com/jenkinsci/pretested-integration-plugin/blob/master/src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge.java#L226 The plugin should probably add a build badge rather than updating the description. This message is automatically generated by JIRA. 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] [pretested-integration] (JENKINS-24907) HTML formatting in build description ( our case 12074 )
Daniel Beck commented on JENKINS-24907 HTML formatting in build description ( our case 12074 ) This is the bug, as it assumes the current formatter is HTML: https://github.com/jenkinsci/pretested-integration-plugin/blob/master/src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge.java#L226 This message is automatically generated by JIRA. 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] [debian-package-builder] (JENKINS-24906) Debian package LTS v1.565.2 has corrupt jenkins.war
Daniel Beck resolved JENKINS-24906 as Not A Defect Debian package LTS v1.565.2 has corrupt jenkins.war Please file this issue with the Debian project. FWIW, this is deliberate: https://issues.jenkins-ci.org/browse/JENKINS-24864?focusedCommentId=211927&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-211927 Change By: Daniel Beck (29/Sep/14 3:19 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. 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] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Shane Gannon edited a comment on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials I'm hitting this issue even though it is marked as resolved. Or potentially another problem with the same symptoms. The Subversion Plugin on our Jenkins is version 2.4.3 and "installed" 2.3. We have all our jobs configured with additional credentials like so Repository URL: https://mysvn.com/trunk@$SVN_REVISION Credentials: MyCreds Additional Credentials Realm: https://mysvn.com Credentials: MyCreds The problem occurs every time one of our svn externals change. e.g. Old SVN External: ^/sibling_of_trunk/path/to/code@191319 nativeapp New SVN External: ^/sibling_of_trunk/path/to/code@191325 nativeapp The next build will be fine. But these symptoms have been reported above. Yet the problem persists for me. What did I miss? PS: Apologies if I'm asking a question that's been posted. The thread above is difficult to follow. This message is automatically generated by JIRA. 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] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Shane Gannon commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials I'm hitting this issue even though it is marked as resolved. Or potentially another problem with the same symptoms. The Subversion Plugin on our Jenkins is version 2.4.3 and "installed" 2.3. We have all our jobs configured with additional credentials like so Repository URL: https://mysvn.com/trunk@$SVN_REVISION Credentials: MyCreds Additional Credentials Realm: https://mysvn.com Credentials: MyCreds The problem occurs every time one of our svn externals change. e.g. Old SVN External: ^/sibling_of_trunk/path/to/code@191319 nativeapp New SVN External: ^/sibling_of_trunk/path/to/code@191325 nativeapp The following build will be fine. But these symptoms have been reported above. Yet the problem persists for me. What did I miss? PS: Apologies if I'm asking a question that's been posted. The thread above is difficult to follow. This message is automatically generated by JIRA. 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] [debian-package-builder] (JENKINS-24906) Debian package LTS v1.565.2 has corrupt jenkins.war
Sam Gleske commented on JENKINS-24906 Debian package LTS v1.565.2 has corrupt jenkins.war I believe this is an incorrect response to this issue. I installed the Debian package from http://pkg.jenkins-ci.org/debian-stable/ In no way is the debian project involved with Jenkins packaging the corrupt war. I implore you to re-open this issue and investigate. It works when I download the jenkins.war from http://mirrors.jenkins-ci.org/war-stable/latest/jenkins.war It does not work when using jenkins.war provided by the Jenkins built Debian package. This message is automatically generated by JIRA. 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 created JENKINS-24914 Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc) Issue Type: Bug Assignee: Unassigned Components: core Created: 29/Sep/14 3:55 PM Description: Jenkins.doQuietDown(boolean block, int timeout) blocks as long as there are jobs running. This is not what it says in the documentation and a less useful behavior in my point of view. boolean block usage="Block until the system really quiets down and no builds are running" int timeout usage="If non-zero, only block up to the specified number of milliseconds" I suggest the implementation should do what it says in the doc, i.e. only wait timeout, then return even though jobs are still running. This error should be easily exposed by a unit test... Environment: Jenkins ver. 1.565 Project: Jenkins Priority: Minor 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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Eric Düll updated JENKINS-23924 New div layout breaks Radiator view It almost works. I have upgraded to the latest Jenkins (jenkins-1.582.war) and to the latest Radiator View Plugin (1.19). The result is as shown in the attached screenshot. I have used FF 24.6.0 and Chrome 37.0.2062.120 m. Can anyone please review that and hopefully reopen the issue. Change By: Eric Düll (29/Sep/14 3:56 PM) Attachment: JENKINS-23924_brokenUI.gif This message is automatically generated by JIRA. 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] [debian-package-builder] (JENKINS-24906) Debian package LTS v1.565.2 has corrupt jenkins.war
Sam Gleske reopened JENKINS-24906 Debian package LTS v1.565.2 has corrupt jenkins.war Change By: Sam Gleske (29/Sep/14 3:47 PM) Resolution: Not A Defect 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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Eric Düll edited a comment on JENKINS-23924 New div layout breaks Radiator view It almost works. I have upgraded to the latest Jenkins (jenkins-1.582.war) and to the latest Radiator View Plugin (1.19). The result is as shown in the attached screenshot (JENKINS-23924_brokenUI.gif). I have used FF 24.6.0 and Chrome 37.0.2062.120 m. Can anyone please review that and hopefully reopen the issue. This message is automatically generated by JIRA. 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] [debian-package-builder] (JENKINS-24906) Debian package LTS v1.565.2 has corrupt jenkins.war
Daniel Beck updated JENKINS-24906 Debian package LTS v1.565.2 has corrupt jenkins.war Change By: Daniel Beck (29/Sep/14 3:56 PM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory] (JENKINS-24915) Extremely slow startup with template-project in combination with jobConfigHistory
Marcus Philip created JENKINS-24915 Extremely slow startup with template-project in combination with jobConfigHistory Issue Type: Bug Assignee: Mirko Friedenhagen Components: jobconfighistory, template-project Created: 29/Sep/14 4:14 PM Description: Startup takes 30 min for a Jenkins installation with ~1000 jobs where most of them is using template builders or publishers of template-project plugin when you have jobConfigHistory plugins. All jobs are loaded by Jenkins at start up. OK so far. But the template-project loops on all jobs again, and updates (twice!) every job that has template builders or publishers. Combined with a slow and questionable sleep implementation in jobConfigHistory this is disastrous for start up time. There may be a lot of other plugins listening to job config save events, so there could be other combinations that is poisonous. Note that load, disk, and CPU usage is low, we're mostly just waiting. I think the main problem is in template-project, but the jobConfigHistory should probably change algorithm as well. 500 ms is a very long time in computer world. 30 ms is probably more reasonable number. "Jenkins initialization thread" prio=10 tid=0x7f6708883000 nid=0x5fa9 sleeping[0x7f66fdcc4000] java.lang.Thread.State: TIMED_WAITING (sleeping) at java.lang.Thread.sleep(Native Method) at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewHistoryDir(FileHistoryDao.java:217) at hudson.plugins.jobConfigHistory.FileHistoryDao.getRootDir(FileHistoryDao.java:118) at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewHistoryEntry(FileHistoryDao.java:406) at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewHistoryEntryAndCopyConfig(FileHistoryDao.java:248) at hudson.plugins.jobConfigHistory.FileHistoryDao.saveItem(FileHistoryDao.java:264) at hudson.plugins.jobConfigHistory.JobConfigHistorySaveableListener.onChange(JobConfigHistorySaveableListener.java:29) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:81) at hudson.model.AbstractItem.save(AbstractItem.java:462) - locked <0x0007a2cee670> (a hudson.model.FreeStyleProject) at hudson.model.Job.save(Job.java:166) - locked <0x0007a2cee670> (a hudson.model.FreeStyleProject) at hudson.model.AbstractProject.save(AbstractProject.java:303) - locked <0x0007a2cee670> (a hudson.model.FreeStyleProject) at hudson.model.Job.removeProperty(Job.java:498) at hudson.model.Job.removeProperty(Job.java:511) at hudson.plugins.templateproject.ItemListenerImpl.onLoaded(ItemListenerImpl.java:42) at jenkins.model.Jenkins.(Jenkins.java:863) Environment: Jenkins ver. 1.565 Project: Jenkins Priority: Critical 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] [debian-package-builder] (JENKINS-24906) Debian package LTS v1.565.2 has corrupt jenkins.war
Richard Mortimer commented on JENKINS-24906 Debian package LTS v1.565.2 has corrupt jenkins.war The contents of the changelog should be available for viewing via zless /usr/share/doc/jenkins/changelog.gz This message is automatically generated by JIRA. 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] [debian-package-builder] (JENKINS-24906) Debian package LTS v1.565.2 has corrupt jenkins.war
Richard Mortimer commented on JENKINS-24906 Debian package LTS v1.565.2 has corrupt jenkins.war I don't see any corruption in the Debian package. The md5sums are correct compared against downloaded war files and the information contained within the .deb. Are you sure that you have the right version installed? $ mkdir /tmp/jenkins $ cd /tmp/jenkins $ wget http://pkg.jenkins-ci.org/debian-stable/binary/jenkins_1.565.2_all.deb $ mkdir jenkins_1.565.2_all $ dpkg-deb -R jenkins_1.565.2_all.deb jenkins_1.565.2_all $ wget http://mirrors.jenkins-ci.org/war-stable/latest/jenkins.war $ wget -O jenkins-1.565.2.war http://mirrors.jenkins-ci.org/war-stable/1.565.2/jenkins.war $ md5sum jenkins.war jenkins-1.565.2.war jenkins_1.565.2_all/usr/share/jenkins/jenkins.war e53d793e42d1686ab103960dbd17979a jenkins.war e53d793e42d1686ab103960dbd17979a jenkins-1.565.2.war e53d793e42d1686ab103960dbd17979a jenkins_1.565.2_all/usr/share/jenkins/jenkins.war $ grep jenkins.war jenkins_1.565.2_all/DEBIAN/md5sums e53d793e42d1686ab103960dbd17979a usr/share/jenkins/jenkins.war This message is automatically generated by JIRA. 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] [pretested-integration] (JENKINS-24907) HTML formatting in build description ( our case 12074 )
Bue Petersen commented on JENKINS-24907 HTML formatting in build description ( our case 12074 ) Yes - agree, I would just suggest plain text. The formatter could also be markdown or something else... build badge is a good suggestion. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [debian-package-builder] (JENKINS-24906) Debian package LTS v1.565.2 has corrupt jenkins.war
Daniel Beck commented on JENKINS-24906 Debian package LTS v1.565.2 has corrupt jenkins.war Right, sorry about that. Could you explain why the checksum of jenkins-common, which appears to be (part of) the Debian packaged Jenkins, is relevant? This message is automatically generated by JIRA. 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] [ssh] (JENKINS-24913) SSH Plugin displays password parameter values unencrypted in log
Daniel Beck commented on JENKINS-24913 SSH Plugin displays password parameter values unencrypted in log Could you explain how you configured the build step or build wrapper to include passwords? This message is automatically generated by JIRA. 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] [debian-package-builder] (JENKINS-24906) Debian package LTS v1.565.2 has corrupt jenkins.war
Richard Mortimer commented on JENKINS-24906 Debian package LTS v1.565.2 has corrupt jenkins.war I just spotted Daniel's comment about jenkins-common. The fact that /var/lib/dpkg/info/jenkins-common.md5sums exists suggests that it is the Debian distribution package that is installed and not the upstream packaged version. This is confirmed by checking the Debian distribution .deb file $ wget http://ftp.uk.debian.org/debian/pool/main/j/jenkins/jenkins-common_1.565.2-2_all.deb s$ mkdir jenkins-common_1.565.2-2_all $ dpkg-deb -R jenkins-common_1.565.2-2_all.deb jenkins-common_1.565.2-2_all $ md5sum jenkins-common_1.565.2-2_all/usr/share/jenkins/jenkins.war 2cc48f1f0341b8c54659e0af73cc3115 jenkins-common_1.565.2-2_all/usr/share/jenkins/jenkins.war $ grep jenkins.war jenkins-common_1.565.2-2_all/DEBIAN/control md5sums $ grep jenkins.war jenkins-common_1.565.2-2_all/DEBIAN/md5sums 2cc48f1f0341b8c54659e0af73cc3115 usr/share/jenkins/jenkins.war Conclusion this is a Debian project issue and not a Jenkins upstream issue. This message is automatically generated by JIRA. 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] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Daniel Beck commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Shane: Seems to be unrelated AFAICT. Could you file a new issue? This message is automatically generated by JIRA. 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] [debian-package-builder] (JENKINS-24906) Debian package LTS v1.565.2 has corrupt jenkins.war
Sam Gleske commented on JENKINS-24906 Debian package LTS v1.565.2 has corrupt jenkins.war The checksum as part of debian packaged jenkins is relevant because the checksum matches my installed war. So that means my war didn't corrupt after the fact. The checksum from the war is different than what is [provided as a direct download][1]. When I overwrite /usr/share/jenkins/jenkins.war with the [direct download war][1] and restart jenkins /etc/init.d/jenkins restart... our instance behaves normally once again. I don't know the build/packaging process so it's entirely possible that the jenkins package is different in how it builds so the checksum will always be different than direct download jenkins. However, I opened this report because our instance of jenkins is broken when using the package version of jenkins.war and not broken when using the direct download version. [1]: http://mirrors.jenkins-ci.org/war-stable/latest/jenkins.war This message is automatically generated by JIRA. 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) At first glace the code looks fairly straightforward and correct https://github.com/jenkinsci/jenkins/blob/stable/core/src/main/java/jenkins/model/Jenkins.java#L2881 So you're specifying e.g. block=true timeout=1 for the CLI command, and it waits for much longer than 10 seconds? This message is automatically generated by JIRA. 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] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Shane Gannon commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Can do Daniel - sorry about the confusion This message is automatically generated by JIRA. 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-13153) "Upgrade Automatically" does not seem to work on Windows
Daniel Beck resolved JENKINS-13153 as Incomplete "Upgrade Automatically" does not seem to work on Windows Thanks for the update Kristoffer! Resolving as incomplete as no information about the issue in recent Jenkins versions is known. (there were a few improvements to jenkins.exe since this was filed, so I have reason to believe this may have been fixed) If this happens in a recent (no older than six weeks) version of Jenkins, please just file a new issue. Thanks! Change By: Daniel Beck (29/Sep/14 5:07 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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Baptiste Mathus commented on JENKINS-23924 New div layout breaks Radiator view Thanks for the feedback. Weird. I checked on Jenkins 1.580 with many browsers, could you please check if it works better for you with 1.580 so that we can narrow the scope of that issue? Could you please also test with a recent version of Firefox to see if the issue is still present with recent ones? And finally if you can propose a patch like some above, that might also help fix the issue correctly. 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-19899) Add Build Now and Configure Project links to all pages within a job
Dale King commented on JENKINS-19899 Add Build Now and Configure Project links to all pages within a job Yes, Daniel I am aware of the faulty logic underlying the decision to not put these links on sub pages of the job, but restating that faulty logic does not make it valid. They are not completely different objects, they are sub objects of each other. Sure there should be some differentiation in the links between the actions to take at the job level and the sub page level but that does not justify removing the job level links. And no having to do target practice to hit that tiny little triangle to open up a submenu to then see the actions and click yet again is not good enough. Any level of usability testing would show that Build Now and Configure are the most often used actions taken on any job, followed by see the console of the latest build. Luckily we have plugins like extra columns which lets up put those actions directly on the dashboard but navigating within a job to these actions is still a pain. This message is automatically generated by JIRA. 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-19899) Add Build Now and Configure Project links to all pages within a job
Dale King edited a comment on JENKINS-19899 Add Build Now and Configure Project links to all pages within a job Yes, Daniel I am aware of the faulty logic underlying the decision to not put these links on sub pages of the job, but restating that faulty logic does not make it valid. They are not completely different objects, they are sub objects of each other. Sure there should be some differentiation in the links between the actions to take at the job level and the sub page level but that does not justify removing the job level links. And no, having to do target practice to hit that tiny little triangle to open up a submenu to then see the actions and click yet again is not good enough. Any level of usability testing would show that Build Now and Configure are the most often used actions taken on any job, followed by see the console of the latest build. Luckily we have plugins like extra columns which lets up put those actions directly on the dashboard but navigating within a job to these actions is still a pain. This message is automatically generated by JIRA. 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] [job-dsl-plugin] (JENKINS-22708) JobDSL Plugin can produce never ending jobs (resource leak)
Daniel Spilker commented on JENKINS-22708 JobDSL Plugin can produce never ending jobs (resource leak) Will be fixed in 1.26. This message is automatically generated by JIRA. 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] [job-dsl-plugin] (JENKINS-22708) JobDSL Plugin can produce never ending jobs (resource leak)
Daniel Spilker resolved JENKINS-22708 as Fixed JobDSL Plugin can produce never ending jobs (resource leak) Change By: Daniel Spilker (29/Sep/14 5:58 PM) Status: Open Resolved Assignee: Justin Ryan Daniel Spilker 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-19899) Add Build Now and Configure Project links to all pages within a job
Daniel Beck commented on JENKINS-19899 Add Build Now and Configure Project links to all pages within a job faulty logic That's a nice claim, but nothing you write actually shows it's wrong. You wouldn't add 'Manage Jenkins' or 'Edit View' to a build, just because they're (great) grand children of the respective View and Jenkins objects, would you? Where I was imprecise (and may have misunderstood your request) is that I'm referring to the side panel, which contains actions related to the current object. It makes no sense to put these there, because you're not building or configuring an existing build. Options I could think of which keep the side panel clean and still make these easier to reach: Sectioned side panel which would make it clear that these belong to a different object. E.g. as sub-items of 'Back to Project' which could get a different label (e.g. named after the project) Adding icon links to (a possible bigger) bread crumb bar, e.g. build action icon next to the context menu triangle. This would clearly associate the action with the object it's related to. This message is automatically generated by JIRA. 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] [robot-plugin] (JENKINS-24868) Add the ability for robot plugin graph to show only failed tests
Jussi Malinen commented on JENKINS-24868 Add the ability for robot plugin graph to show only failed tests Have you tried to "zoom to changes"? That should highlight the most significant changes. The main results view has currently unfortunately a broken "zoom to changes" and "show full graph" links, but the upcoming version should fix 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] [robot-plugin] (JENKINS-24688) Broken robot framework summary in job list
Jussi Malinen assigned JENKINS-24688 to Jussi Malinen Broken robot framework summary in job list Change By: Jussi Malinen (29/Sep/14 6:20 PM) Assignee: jpiironen Jussi Malinen This message is automatically generated by JIRA. 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] [robot-plugin] (JENKINS-24688) Broken robot framework summary in job list
Jussi Malinen resolved JENKINS-24688 as Fixed Broken robot framework summary in job list Change By: Jussi Malinen (29/Sep/14 6:20 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-24916) Link to robot log from individual tests and suites
Jussi Malinen created JENKINS-24916 Link to robot log from individual tests and suites Issue Type: Bug Assignee: Jussi Malinen Components: robot-plugin Created: 29/Sep/14 6:21 PM Description: It would be very helpful to be able to jump directly to the robot log from jenkins test view. Project: Jenkins Priority: Major Reporter: Jussi Malinen This message is automatically generated by JIRA. 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] [robot-plugin] (JENKINS-24916) Link to robot log from individual tests and suites
Jussi Malinen updated JENKINS-24916 Link to robot log from individual tests and suites Change By: Jussi Malinen (29/Sep/14 6:22 PM) Issue Type: Bug New Feature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-22708) JobDSL Plugin can produce never ending jobs (resource leak)
SCM/JIRA link daemon commented on JENKINS-22708 JobDSL Plugin can produce never ending jobs (resource leak) Code changed in jenkins User: Daniel Spilker Path: docs/Home.md http://jenkins-ci.org/commit/job-dsl-plugin/bc55db2f4737cd73ff64815bbd3f455d41ce71fa Log: mention fix for JENKINS-22708 in release notes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-24917) Default background-color: #FFF on tables and table elements isn't overridden by build-pipeline background-color
milki mlk created JENKINS-24917 Default background-color: #FFF on tables and table elements isn't overridden by build-pipeline background-color Issue Type: Bug Assignee: Unassigned Attachments: pipeline-old.png, pipeline.png Components: build-pipeline Created: 29/Sep/14 6:40 PM Description: With the change https://issues.jenkins-ci.org/browse/JENKINS-24625 (https://github.com/jenkinsci/jenkins/commit/2753fac18d6ead74d8f446abcebda659eab29155), all the table elements retain a background-color: #FFF While each individual buildcard has a table class (PENDING, ABORTED, etc) that overrides it's background-color, the td that the table belongs in has a background-color: #FFF that isn't overridden. For example: tr.build-pipeline - td #build-# - table.build-card.rounded.SUCCESS table.SUCCESS sets a background-color of #1bd130. However, has a background-color: #FFF from style.css tr.build-pipeline itself also retains the same background-color: #FFF I've attached a sample of the pipeline with and without the background-color: #fff disabled. This color change is undesirable and makes it very difficult to read the pipeline now. Project: Jenkins Priority: Major Reporter: milki mlk This message is automatically generated by JIRA. 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-18034) Gradle plugin does not handle spaces in Jenkins install location
Daniel Beck updated JENKINS-18034 Gradle plugin does not handle spaces in Jenkins install location Artifactory plugin assumes there are no spaces in the temp dir: https://github.com/jenkinsci/artifactory-plugin/blob/master/src/main/java/org/jfrog/hudson/gradle/ArtifactoryGradleConfigurator.java#L398 http://javadoc.jenkins-ci.org/hudson/FilePath.html#createTextTempFile%28java.lang.String,%20java.lang.String,%20java.lang.String,%20boolean%29 Workaround: provide a different java.io.tmpdir. Change By: Daniel Beck (29/Sep/14 6:46 PM) Assignee: Gregory Boissinot yossis Component/s: artifactory Component/s: gradle This message is automatically generated by JIRA. 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
Harald Albers commented on JENKINS-24551 Docker URL contains invalid version information created PR #15 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-24917) Default background-color: #FFF on tables and table elements isn't overridden by build-pipeline background-color
milki mlk updated JENKINS-24917 Default background-color: #FFF on tables and table elements isn't overridden by build-pipeline background-color Change By: milki mlk (29/Sep/14 6:52 PM) Description: With the change from Jenkins 1.581 - https://issues.jenkins-ci.org/browse/JENKINS-24625 (https://github.com/jenkinsci/jenkins/commit/2753fac18d6ead74d8f446abcebda659eab29155), all the table elements retain a background-color: #FFFWhile each individual buildcard has a table class (PENDING, ABORTED, etc) that overrides it's background-color, the td that the table belongs in has a background-color: #FFF that isn't overridden.For example:tr.build-pipeline - td #build-# - table.build-card.rounded.SUCCESStable.SUCCESS sets a background-color of #1bd130. However, has a background-color: #FFF from style.csstr.build-pipeline itself also retains the same background-color: #FFFI've attached a sample of the pipeline with and without the background-color: #fff disabled.This color change is undesirable and makes it very difficult to read the pipeline now. cppcheck https://issues.jenkins-ci.org/browse/JENKINS-24834 has similarly needed to patch their templates for this change in core. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11598) Updating Plugins from plugins mirror and own update-center.json does not work
Daniel Beck commented on JENKINS-11598 Updating Plugins from plugins mirror and own update-center.json does not work Is this still a problem? I mean, sure, the signature will not match if you patch the JSON data without fixing the signature, but that's a security measure. To disable this check, set the undocumented Java system property hudson.model.DownloadService.noSignatureCheck as described on this page: https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties Other than that, maybe this helps? It allows you to import different keys so you can actually sign your update center metadata so Jenkins can verify the signature. https://wiki.jenkins-ci.org/display/JENKINS/UpdateSites+Manager+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] [docker-build-step] (JENKINS-24551) Docker URL contains invalid version information
Harald Albers started work on JENKINS-24551 Docker URL contains invalid version information Change By: Harald Albers (29/Sep/14 6:56 PM) Status: Open In Progress This message is automatically generated by JIRA. 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
Harald Albers updated JENKINS-24551 Docker URL contains invalid version information Change By: Harald Albers (29/Sep/14 6:55 PM) Priority: Critical Minor Assignee: vjuranek Harald Albers This message is automatically generated by JIRA. 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-9922) Only select available LTS upgrades after upgrading from non-LTS version
Daniel Beck commented on JENKINS-9922 Only select available LTS upgrades after upgrading from non-LTS version Appears to just be an issue with the update center data being outdated (as the returned data is different based on the Jenkins version requesting it). Jenkins should probably invalidate the cache after a core update. This message is automatically generated by JIRA. 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-10316) Running Jenkins 1.409.1 and do not get option to do anything but downgrade to previous version
Daniel Beck resolved JENKINS-10316 as Cannot Reproduce Running Jenkins 1.409.1 and do not get option to do anything but downgrade to previous version Resolving because of the age of this issue (I doubt you can still provide additional information to investigate the cause ). Please file a new issue if this occurs again on recent Jenkins versions. Change By: Daniel Beck (29/Sep/14 7:04 PM) Status: In Progress Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. 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-24918) Filenames of archived artifacts become garbled when they contain non-ascii characters
Lars Lykke created JENKINS-24918 Filenames of archived artifacts become garbled when they contain non-ascii characters Issue Type: Bug Assignee: Unassigned Components: core Created: 29/Sep/14 7:08 PM Description: My steps to reproduce is to 1) Check out files from our SCM (StarTeam plugin) 2) Verify files containing special characters are correct in the workspace (which they are) 3) After the files have been archived using the standard Archive Artifacts Post build step, the filenames containing special chars have been garbled. So files are retrieved correctly from SCM but get their filename garbled upon archiving. In my particular case the filenames contain the characters 'æ', 'ø' and 'å'. These are the chars being garbled by the archiving step. I've been searching for a way of testing whether or not I could influence the setting via some sort of startup parameter to Jenkins but with no luck in finding such. Is this just because I've failed to supply the right locale setting or encoding? Master is a Windows 7 pc. Slave is also Windows 7. I tried changing the checkout and archiving task to run on the master instead of the slave. The filenames were then no longer garbled!? So I guess this comes down to some sort of setting different on the machines? Java version perhaps? Environment: Master (Windows 7, Jenkins v. 1.581) Slave (Windows 7) Project: Jenkins Labels: archiving artifacts unicode Priority: Minor Reporter: Lars Lykke This message is automatically generated by JIRA. 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-6095) Selecting a particular branch to build while pressing 'build now'
Daniel Beck resolved JENKINS-6095 as Incomplete Selecting a particular branch to build while pressing 'build now' No response to comment asking for clarification so resolving as Incomplete. Seems best solved using build parameters. Change By: Daniel Beck (29/Sep/14 7:14 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] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Lars Lykke commented on JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ I'm seeing the same issue with Jenkins v. 1.581 (Master, Windows 7). My slaves are Windows 7/Windows 2012 machines with jenkins running as a service on them. Retrieving artifacts from upstream job takes a very long time (approx. 7 min for 750 MB ~ 100MB/min). The slaves are connected using JNLP agent Archiving artifacts is about the same: 12 min. for 2 GB. How can I provide additional information which might help in resolving this issue? This message is automatically generated by JIRA. 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] [groovy] (JENKINS-24870) "/" in script parameters becomes "\" (Regression in 1.21)
SCM/JIRA link daemon commented on JENKINS-24870 "/" in script parameters becomes "\" (Regression in 1.21) Code changed in jenkins User: Vojtech Juranek Path: src/main/java/hudson/plugins/groovy/Groovy.java src/test/java/hudson/plugins/groovy/PluginTest.java http://jenkins-ci.org/commit/groovy-plugin/a5512cc32f111adb15724ea86644824a3e92 Log: [FIXED JENKINS-24870] Use placeholder for executable when parsing parameters This message is automatically generated by JIRA. 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] [groovy] (JENKINS-24870) "/" in script parameters becomes "\" (Regression in 1.21)
SCM/JIRA link daemon resolved JENKINS-24870 as Fixed "/" in script parameters becomes "\" (Regression in 1.21) Change By: SCM/JIRA link daemon (29/Sep/14 7:46 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [checkstyle] (JENKINS-17287) Provide support for ScalaStyle warnings
Ulli Hafner commented on JENKINS-17287 Provide support for ScalaStyle warnings Can you please provide a link to such a project and the build command line I need to start? (I don't use Scala on my own so...) This message is automatically generated by JIRA. 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-24919) Gerrit Trigger Plugin - Build Current Patchset Only - leave workspace in a bad state if it interrupts a fetch
Tony Bridges created JENKINS-24919 Gerrit Trigger Plugin - Build Current Patchset Only - leave workspace in a bad state if it interrupts a fetch Issue Type: Bug Assignee: rsandell Components: core, gerrit-trigger Created: 29/Sep/14 7:50 PM Description: If "build current patchset only" is enabled and the system issues a cancel to a job that is currently fetching from gerrit, the locks are not cleared on the workspace. The next job to run on that workspace will fail as it detects the previous fetch is still in progress. We see this when a developer uploads two patchsets within a minute of each other, and the gerrit fetch operation takes 3+ minutes. Workaround is to disable the feature. The Cancel operation should reset any active locks. Environment: Windows 2k8 Jenkins 1.554 LTS, Gerrit Trigger 2.11.1 Project: Jenkins Priority: Major Reporter: Tony Bridges This message is automatically generated by JIRA. 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] [warnings] (JENKINS-22386) Warnings Plugin cannot show details for MSBuild warnings
Ulli Hafner commented on JENKINS-22386 Warnings Plugin cannot show details for MSBuild warnings I think nobody is working on a solution up to now. If you are interested in helping please let me know... This message is automatically generated by JIRA. 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] [ivy] (JENKINS-24893) Ivy Plugin: Perform a build link is broken
SCM/JIRA link daemon commented on JENKINS-24893 Ivy Plugin: Perform a build link is broken Code changed in jenkins User: Kevin Formsma Path: src/main/resources/hudson/ivy/IvyModuleSet/modules.jelly src/main/resources/hudson/ivy/IvyModuleSet/modules.properties http://jenkins-ci.org/commit/ivy-plugin/55fbe3d16252cc18e13b198be52f525a1944afb9 Log: Merge pull request #16 from mcupak/build-link [fixed JENKINS-24893] fixed the link to schedule a build Compare: https://github.com/jenkinsci/ivy-plugin/compare/a0f6060f6159...55fbe3d16252 This message is automatically generated by JIRA. 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.
