[JIRA] [compress-artifacts] (JENKINS-24430) It doesn't work anymore with latest update on Aug-26-2014
Paul Pacurar created JENKINS-24430 It doesn't work anymore with latest update on Aug-26-2014 Issue Type: Bug Assignee: Jesse Glick Components: compress-artifacts Created: 26/Aug/14 6:58 AM Description: It worked yesterday, but today, the folder containing the artifacts is not compress anymore. Jenkins warns at config page: Unreadable Data It is acceptable to leave unreadable data in these files, as Jenkins will safely ignore it. To avoid the log messages at Jenkins startup you can permanently delete the unreadable data by resaving these files using the button below. Type Name Error hudson.model.FreeStyleBuild ReleaseWebApplication #50 CannotResolveClassException: org.jenkinsci.plugins.compress_artifacts.CompressingArtifactManager hudson.model.FreeStyleBuild ReleaseWebApplication #51 CannotResolveClassException: org.jenkinsci.plugins.compress_artifacts.CompressingArtifactManager hudson.model.FreeStyleBuild ReleaseWebApplication #48 CannotResolveClassException: org.jenkinsci.plugins.compress_artifacts.CompressingArtifactManager hudson.model.FreeStyleBuild ReleaseWebApplication #47 CannotResolveClassException: org.jenkinsci.plugins.compress_artifacts.CompressingArtifactManager jenkins.model.ArtifactManagerConfiguration CannotResolveClassException: org.jenkinsci.plugins.compress_artifacts.CompressingArtifactManagerFactory Project: Jenkins Priority: Major Reporter: Paul Pacurar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs] (JENKINS-24429) CVSRoot is not accepted by CVS plugin
Frank Kaaijk created JENKINS-24429 CVSRoot is not accepted by CVS plugin Issue Type: Bug Assignee: Unassigned Components: cvs Created: 26/Aug/14 6:43 AM Description: Create a job that uses CVS. Set the CVSRoot to ":sspi:cvs@cvsserver:/SomeProduct" and execute the build. Following trace appears on the build output: Started by user Frank Kaaijk Building in workspace D:\Jenkins\workspace\Some Product FATAL: Unrecognized CVS Root: :sspi:cvs@cvsserver:/SomeProduct java.lang.IllegalArgumentException: Unrecognized CVS Root: :sspi:cvs@cvsserver:/Some Product at org.netbeans.lib.cvsclient.connection.ConnectionFactory.getConnection(ConnectionFactory.java:121) at hudson.scm.AbstractCvs.getCvsClient(AbstractCvs.java:364) at hudson.scm.AbstractCvs.getCvsClient(AbstractCvs.java:341) at hudson.scm.AbstractCvs.perform(AbstractCvs.java:241) at hudson.scm.AbstractCvs.checkout(AbstractCvs.java:211) at hudson.scm.CVSSCM.checkout(CVSSCM.java:346) at hudson.model.AbstractProject.checkout(AbstractProject.java:1251) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:605) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:514) at hudson.model.Run.execute(Run.java:1703) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43) This problem disappears when I downgrade to version 1.6. Environment: Windows 7 Professional Jenkins 1.560 CVSNT 2.0.51d Java version "1.8.0" CVS Plugin 2.11 and 2.12 (maybe others) Project: Jenkins Labels: exception Plugin CVS CVSRoot Priority: Major Reporter: Frank Kaaijk This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
Yoann Dubreuil commented on JENKINS-23693 Cannot delete workspace I pushed a patch and a pull request here: https://github.com/jenkinsci/ws-cleanup-plugin/pull/18 It fixes the NPE on our environment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-timeout] (JENKINS-7832) Hudson build time is calculated from the time job enters the queue while it should be when job actually starts to run
ikedam commented on JENKINS-7832 Hudson build time is calculated from the time job enters the queue while it should be when job actually starts to run I want to see how much time each steps of builds spend. Could you install Timestamper plugin, enable "Add timestamps to the Console Output" in your job, and attach a consple output that reproduces the problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
David Tanner commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception I can very easily create this null pointer error if there is nothing checked out using the git scm. As long as I have that set then there is a last build revision. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security] (JENKINS-24399) Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths)
Jesse Glick commented on JENKINS-24399 Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths) Directories should be blocked. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577
Alex Earl commented on JENKINS-24395 Fatal error with coming Jenkins ver. 1.577 It would be helpful if someone mentioned they were making changes so plugin developers knew. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24417) email-ext Content Token Reference help info: after first list, it repeats each item hundreds of times
Alex Earl commented on JENKINS-24417 email-ext Content Token Reference help info: after first list, it repeats each item hundreds of times Yes, this is 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] [email-ext] (JENKINS-24413) java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction
Alex Earl closed JENKINS-24413 as Duplicate java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction Change By: Alex Earl (26/Aug/14 3:02 AM) Status: Open Closed 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] [postbuild-task] (JENKINS-24418) Getting NullPointer exception while executing post build steps (after successful build)
sean head commented on JENKINS-24418 Getting NullPointer exception while executing post build steps (after successful build) Was running 1.577 and having sporadic issues. Reverting to 1.565 seems to have made them stop. I skipped 1.576 so I don't have any data for that release. A little more info about my setup: Master running on a dedicated ubuntu vm. 3 windows slaves (JNLP, 2x win7 64 bit, 1x win 8.1 64bit), 2x ubuntu slaves connected via swarm plugin, 6x osx slaves connected via swarm plugin (10.9.4, and 10.9.5). Heavy users of the matrix build system. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
David Tanner commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Following the lines that lead to the commit notifier I don't understand how this line gets null for the lastRevision. Can you please PM me the log from one of the failed builds? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24428) NullPointerException after Login
R. Tyler Croy moved JENKINS-24428 NullPointerException after Login Change By: R. Tyler Croy (26/Aug/14 2:47 AM) Project: Infrastructure Jenkins Key: INFRA JENKINS - 113 24428 Workflow: jira JNJira Component/s: core Component/s: ci This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24202) Pin Build at Label Does not Sync at the CL of the Label
Ryan Hummer resolved JENKINS-24202 as Fixed Pin Build at Label Does not Sync at the CL of the Label Looks good with 1.0.13 Change By: Ryan Hummer (26/Aug/14 2:29 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ui-changes] (JENKINS-24397) new responsive UI has issues with "longish" build display names
Daniel Beck commented on JENKINS-24397 new responsive UI has issues with "longish" build display names It's a bit hidden in the 'sidebar' change. The second issue linked is basically this one. Please be more specific about the 'All' view issue. Just file a new issue (preferably test first if it occurs on 1.577) with full description and screenshot, and we'll take a look. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23925) SSL weak ciphers
Daniel Beck resolved JENKINS-23925 as Won't Fix SSL weak ciphers No pressing need to implement this as a change in Java version is sufficient. Change By: Daniel Beck (26/Aug/14 2:41 AM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-failure-analyzer] (JENKINS-23409) Crashing api at depth > 0
milki mlk commented on JENKINS-23409 Crashing api at depth > 0 We use http://netmelody.org/ci-eye/ and with Jenkins 1.576 and 1.577, all calls from it are failing with the same error: Caused by: org.kohsuke.stapler.export.NotExportableException: class java.io.IOException doesn't have @ExportedBean so cannot write hudson.slaves.OfflineCause$ChannelTermination.cause This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21749) builds seem to hang forever and can't be canceled, but actually complete
Daniel Beck commented on JENKINS-21749 builds seem to hang forever and can't be canceled, but actually complete Hi Jay, not a problem. This is just housekeeping and can be reopened at any time if it turns out it's a real Jenkins issue – which in this case it doesn't seem to be, so let's leave it as it is. Thanks for following up! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23330) Spaces in project names are not encoded on IDs
Daniel Beck commented on JENKINS-23330 Spaces in project names are not encoded on IDs Does the Keyboard Plugin actually work with "valid" IDs? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-24386) Unity Test Tools package returns 2 or 3 for failed integration testing.
Mark McNeely commented on JENKINS-24386 Unity Test Tools package returns 2 or 3 for failed integration testing. No problem. I'm glad I could help and thanks for responding back about the issue! I would go with the first option as well. At best, it would make it future proof in case more exit codes were added for other meanings. If you need any more help from me then feel free to 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] [build-pipeline] (JENKINS-24423) Just created (but not yet saved) pipeline breaks Jenkins
Daniel Beck resolved JENKINS-24423 as Duplicate Just created (but not yet saved) pipeline breaks Jenkins Duplicates JENKINS-23363. Change By: Daniel Beck (26/Aug/14 2:06 AM) 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] [build-pipeline] (JENKINS-24423) Just created (but not yet saved) pipeline breaks Jenkins
dserodio created JENKINS-24423 Just created (but not yet saved) pipeline breaks Jenkins Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: build-pipeline Created: 25/Aug/14 8:06 PM Description: As soon as you create a Build Pipeline view, before saving it, the view's config.xml is invalid because it doesn't contain a tag. When you try to open Jenkins, without saving this partially configured view, it shows the error page with the following stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.565.jar!/hudson/model/View/index.jelly:42:43: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.565.jar!/lib/hudson/projectView.jelly:66:22: null at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795) 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.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrat
[JIRA] [promoted-builds] (JENKINS-8963) Remote API to create/delete/modify promotions
SCM/JIRA link daemon commented on JENKINS-8963 Remote API to create/delete/modify promotions Code changed in jenkins User: Jesse Glick Path: src/main/resources/hudson/plugins/promoted_builds/PromotedProjectAction/_api.jelly http://jenkins-ci.org/commit/promoted-builds-plugin/1c726a6a2585fcf3debfdac4796789e159164f3d Log: JENKINS-8963 Documentation of REST API (CRUD operations). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-8963) Remote API to create/delete/modify promotions
Jesse Glick commented on JENKINS-8963 Remote API to create/delete/modify promotions Not bothering with CLI commands, just doing REST API for now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24426) Jenkins version 1.575 killing processes at end of shell script
Daniel Beck resolved JENKINS-24426 as Not A Defect Jenkins version 1.575 killing processes at end of shell script Behaves as intended. See https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller for a description and solutions. Change By: Daniel Beck (26/Aug/14 1:56 AM) 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] [plugin] (JENKINS-24411) HP ALI plugin not available to download
Daniel Beck resolved JENKINS-24411 as Incomplete HP ALI plugin not available to download There is no such plugin in the jenkinsci organzation on Github, or listed in the wiki. Both HP plugins in the jenkinsci org and on Github are listed in the update center: hp-operations-orchestration-automation-execution-plugin hp-application-automation-tools-plugin Change By: Daniel Beck (26/Aug/14 2:18 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24407) missing weather icons (randomly?)
Daniel Beck updated JENKINS-24407 missing weather icons (randomly?) Speculatively assigning to Tom who wrote the icon tag. Would be interesting to know whether the working weather icons are percentages evenly dividable by 20. Change By: Daniel Beck (26/Aug/14 2:08 AM) Assignee: Tom FENNELLY This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24202) Pin Build at Label Does not Sync at the CL of the Label
dan tran commented on JENKINS-24202 Pin Build at Label Does not Sync at the CL of the Label any status on this fix? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24427) P4 Trust error show up when integrate Parameterize Trigger Plugin
dan tran commented on JENKINS-24427 P4 Trust error show up when integrate Parameterize Trigger Plugin this snippet my fix it server.addTrust( new TrustOptions().setAutoAccept( true ) ); This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-24422) Jenkins GitHub plugin unable to trigger the job upon git push, when I am passing " Repository URL " as build parameter value
suersh emmanni
created JENKINS-24422
Jenkins GitHub plugin unable to trigger the job upon git push, when I am passing " Repository URL " as build parameter value
Issue Type:
Improvement
Assignee:
Unassigned
Components:
github
Created:
25/Aug/14 7:55 PM
Description:
I have created parameterize build pipeline for my project.
And I am passing to Git Repository URL as one of the parameter.
However, I noticed that Jenkins GitHub plugin is unable to trigger the job upon git push, when I pass to Git Repository URL as parameter value.
I am seeing below Waring message in console log.
" WARNING: Could not match URL ${PROJECT_GIT_SSH_URL} " (obviously, it doesn't match the pattern matcher)
here is parameter PROJECT_GIT_SSH_URL
value g...@xyz.git
When I trigger my job manually it working fine...
Project:
Jenkins
Priority:
Major
Reporter:
suersh emmanni
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-failure-analyzer] (JENKINS-23409) Crashing api at depth > 0
Daryl Spartz commented on JENKINS-23409 Crashing api at depth > 0 Similar or same issue: http:///jenkins/computer/api/json works http:///jenkins/computer/api/json?depth=1 fails with: Stack trace javax.servlet.ServletException: org.kohsuke.stapler.export.NotExportableException: class java.io.IOException doesn't have @ExportedBean so cannot write hudson.slaves.OfflineCause$ChannelTermination.cause at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) 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$4.doDispatch(MetaClass.java:210) 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:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:751) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1666) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1653) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:91) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1653) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:114) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) 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:1653) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1653) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1653) at yjava.servlet.FilterChainInvoker$ServletFilterChainInvoker.invoke(FilterChainInvoker.java:49) at yjava.servlet.filter.BouncerFilter.doFilter(BouncerFilter.java:251) at yjava.servlet.filter.BouncerFilter.doFilter(BouncerFilter.java:117) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1645) at yjava.servlet.FilterChainInvoker$ServletFilterChainInvoker.invoke(FilterChainInvoker.java:49) at yjava.servlet.filter.SSLCrimeFilter.doFilter(SSLCrimeFilter.java:82) at yjava.servlet.filter.SSLCrimeFilter.doFilter(SSLCrimeFilter.java:47) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1636) at yjava.servlet.FilterChainInvoker$Serv
[JIRA] [postbuild-task] (JENKINS-24418) Getting NullPointer exception while executing post build steps (after successful build)
Daniel Beck resolved JENKINS-24418 as Cannot Reproduce Getting NullPointer exception while executing post build steps (after successful build) Issue needs to be reproduced in a recent Jenkins version. Use 1.565.x or 1.570+ with recent Maven project plugin. Change By: Daniel Beck (26/Aug/14 2:11 AM) 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] [promoted-builds] (JENKINS-8963) Remote API to create/delete/modify promotions
SCM/JIRA link daemon commented on JENKINS-8963 Remote API to create/delete/modify promotions Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/promoted_builds/JobPropertyImpl.java src/main/java/hudson/plugins/promoted_builds/PromotedProjectAction.java src/test/java/hudson/plugins/promoted_builds/RemoteApiTest.java http://jenkins-ci.org/commit/promoted-builds-plugin/98a79660b82648f21035c1359c7542bc99d2faef Log: [FIXED JENKINS-8963] Added REST API to create promotion processes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [reverse-proxy-auth] (JENKINS-24416) Reverse proxy auth is preventing SSH CLI access
Daniel Beck updated JENKINS-24416 Reverse proxy auth is preventing SSH CLI access Change By: Daniel Beck (26/Aug/14 1:58 AM) Component/s: cli This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24417) email-ext Content Token Reference help info: after first list, it repeats each item hundreds of times
m_broida created JENKINS-24417 email-ext Content Token Reference help info: after first list, it repeats each item hundreds of times Issue Type: Bug Assignee: Alex Earl Components: email-ext Created: 25/Aug/14 4:11 PM Description: Click the ? to open the email-ext Content Token Reference. Wait >15 seconds for help info to load. Scroll the list of tokens. After the header "Token Macro Plugin Tokens", each item is repeated hundreds of times. Then a few final items are listed. Environment: Jenkins 1.542, email-ext 2.36 Project: Jenkins Priority: Major Reporter: m_broida This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-24421) Github webhook throwing "Form too large"
Stuart Whelan commented on JENKINS-24421 Github webhook throwing "Form too large" I worked around this by adding -Dorg.eclipse.jetty.server.Request.maxFormContentSize=500 to my jenkins arguments, just before the -jar parameter. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [postbuild-task] (JENKINS-24418) Getting NullPointer exception while executing post build steps (after successful build)
sean head commented on JENKINS-24418 Getting NullPointer exception while executing post build steps (after successful build) I'm seeing something similar to this. Right before the post build steps run I get "FATAL: null java.lang.NullPointerException" In the console log for the job run, nothing related in the jenkins log. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-failure-analyzer] (JENKINS-23409) Crashing api at depth > 0
Daryl Spartz commented on JENKINS-23409 Crashing api at depth > 0 Sorry, versions where it fails: Jenkins ver. 1.576 Jenkins ver. 1.577 The URL works on Jenkins ver. 1.554.x This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud] (JENKINS-19987) Automatically determine VM IP address for SSH login
Michael Devey
commented on JENKINS-19987
Automatically determine VM IP address for SSH login
using pysphere for this.
#!/usr/bin/python
from pysphere import VIServer
server = VIServer()
server.connect(host, user, pass)
vm = server.get_vm_by_name(vmname)
ip = vm.get_property('ip_address')
print "IP address is " + ip
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [reverse-proxy-auth] (JENKINS-24415) Reverse proxy auth plugin v1.4.0 gives NullPointerException
Daniel Beck commented on JENKINS-24415 Reverse proxy auth plugin v1.4.0 gives NullPointerException issue is fixed on master: https://github.com/jenkinsci/reverse-proxy-auth-plugin/commit/a4e9f6afcb0020b97ac1921c457ebcf35852f31c Plugin just needs to be released. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Michal Turek commented on JENKINS-24076 Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) Hi, I will look at the issue, but I have no time for that at the moment. If you are really desperate, you can debug and fix the issue by yourself and create a pull request. The related code is org.jenkinsci.plugins.cppcheck.CppcheckResult.getDiff() for summary and diffCurrentAndPrevious() for details. Data of previous build comes from getPreviousResult(), I guess there should be loop to the builds history instead of single if condition. I have updated similar code in sloccount plugin, it may be the same. The report is initially parsed and stored in org.jenkinsci.plugins.cppcheck.CppcheckPublisher.perform(). Hope this will help for quick orientation in the code... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24417) email-ext Content Token Reference help info: after first list, it repeats each item hundreds of times
Daniel Beck commented on JENKINS-24417 email-ext Content Token Reference help info: after first list, it repeats each item hundreds of times What version of Token Macro plugin are you using? This should have been fixed in 1.9. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-18170) Remove issues on Github or stop using Jenkins Jira
dserodio closed JENKINS-18170 as Fixed Remove issues on Github or stop using Jenkins Jira Closing since, as Steve Hill said, "The wiki entry points to jenkinsci/build-pipeline-plugin, which doesn't have an issues tab." Change By: dserodio (25/Aug/14 7:58 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577
Jesse Glick resolved JENKINS-24395 as Fixed Fatal error with coming Jenkins ver. 1.577 Was fixed over a month ago in sources. You merely need to cut a new release. There is no need to change dependencies. Change By: Jesse Glick (25/Aug/14 7:45 PM) Status: Open Resolved Assignee: Alex Earl Jesse Glick 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] [reverse-proxy-auth] (JENKINS-24415) Reverse proxy auth plugin v1.4.0 gives NullPointerException
Lieuwe Hummel created JENKINS-24415 Reverse proxy auth plugin v1.4.0 gives NullPointerException Issue Type: Bug Assignee: Unassigned Components: reverse-proxy-auth Created: 25/Aug/14 3:23 PM Description: When updating the reverse proxy auth plugin to v1.4.0 on Jenkins v1.175 (tested with v1.3.3 as well) results in a NullPointerException, preventing me to do anything. Disabling security and reverting to v1.0.1 (the version i updated from) gives me access again, but I want to stay current with the updates. Project: Jenkins Labels: exception plugin Priority: Major Reporter: Lieuwe Hummel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [reverse-proxy-auth] (JENKINS-24415) Reverse proxy auth plugin v1.4.0 gives NullPointerException
Lieuwe Hummel commented on JENKINS-24415 Reverse proxy auth plugin v1.4.0 gives NullPointerException Stack trace java.lang.NullPointerException at org.eclipse.jetty.util.StringUtil.getBytes(StringUtil.java:383) at org.eclipse.jetty.io.ByteArrayBuffer.(ByteArrayBuffer.java:81) at org.eclipse.jetty.io.ByteArrayBuffer$CaseInsensitive.(ByteArrayBuffer.java:424) at org.eclipse.jetty.io.BufferCache$CachedBuffer.(BufferCache.java:134) at org.eclipse.jetty.io.BufferCache.lookup(BufferCache.java:101) at org.eclipse.jetty.http.HttpFields.getField(HttpFields.java:402) at org.eclipse.jetty.http.HttpFields.getStringField(HttpFields.java:431) at org.eclipse.jetty.server.Request.getHeader(Request.java:605) at org.jenkinsci.plugins.reverse_proxy_auth.ReverseProxySecurityRealm$1.doFilter(ReverseProxySecurityRealm.java:402) 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.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21437) Failed to update /computer/xxxxxxxxxxx/builds
SCM/JIRA link daemon resolved JENKINS-21437 as Fixed Failed to update /computer/xxx/builds Change By: SCM/JIRA link daemon (25/Aug/14 2:48 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] [promoted-builds] (JENKINS-8963) Remote API to create/delete/modify promotions
SCM/JIRA link daemon resolved JENKINS-8963 as Fixed Remote API to create/delete/modify promotions Change By: SCM/JIRA link daemon (25/Aug/14 6:30 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] [docker-build-step] (JENKINS-24414) Port bindings are ignored with Docker v1.2
Daniel Kerwin created JENKINS-24414 Port bindings are ignored with Docker v1.2 Issue Type: Bug Assignee: vjuranek Components: docker-build-step Created: 25/Aug/14 3:00 PM Description: Scenario: Start docker container that exposes port 80. Should be mapped to port 4000 on the host system. Port bindings config: 4000 80 Worked in previous versions. Results in a container similar to: abc12345as example/website-preview:latest "/usr/sbin/apache2 - 5 seconds ago Up 4 seconds80/tcp sad_lovelace Based on the config the mappings should look like this: 0.0.0.0:4000->80/tcp Environment: Docker Version 1.2 docker-build-step: 1.9 Project: Jenkins Priority: Critical Reporter: Daniel Kerwin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-8963) Remote API to create/delete/modify promotions
Jesse Glick assigned JENKINS-8963 to Jesse Glick Remote API to create/delete/modify promotions Change By: Jesse Glick (25/Aug/14 3:28 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24419) Builds fail/skip randomly without reason given.
David Koch
created JENKINS-24419
Builds fail/skip randomly without reason given.
Issue Type:
Bug
Assignee:
rsandell
Components:
core, multi-slave-config
Created:
25/Aug/14 4:46 PM
Description:
Hello,
We are experiencing an issue where Jenkins fails builds for no discernible reasons. Apparently, other people came across the same issue.
I quote from 2 relevant posts to jenkinsci-users: link 1, link 2.
We use DSL in a Build Flow project to trigger around 50 parallel builds on 2 slave nodes. However, some of the triggered jobs fail for no apparent reason. The only message in the Jenkins log file is:
Aug 20, 2014 12:38:41 AM hudson.model.Run execute
INFO: #9288 main build action completed: FAILURE
We trigger a parallel batch of roughly 30 parametrized MultiJobs. The triggering job and each of the phases of the MultiJob can run on one of 2 slave nodes. This is specified via the "Restrict where this job can run" option.
About 1 in 15 times a phase (mostly the first one) of the MultiJob is silently skipped. Jenkins simply states "Not Built" next to the job phase, that's it - the next phase proceeds even though according to the job setup it should only execute if the previous phase was successful.
This appears to be an issue using the MultiPhase job plugin + "Allow
Concurrent Builds" + "restrict where this job can be run", and is a blocking
issue for myself and my team. Any insight into a fix for this would be
greatly appreciated.
I have not been able to reproduce the problem using a basic build setup but for what it's worth I include the XML for what I used for testing. Below, DEBUG_SkippedBuilds is a BuildFlow job which triggers a MultiPhase job DEBUG_MultiJobProject which in turn runs a shell command and a job called DEBUG_FakeJobPhase.
"DEBUG_SkippedBuilds"
"build-flow-plugin@0.12">
Debug.
false
"rebuild@1.21">
false
"hudson.scm.NullSCM"/>
true
false
false
false
false
ignore(FAILURE){
parallel(
{ build("DEBUG_MultiJobProject", MY_ID: "01") },
{ build("DEBUG_MultiJobProject", MY_ID: "02") },
{ build("DEBUG_MultiJobProject", MY_ID: "03") },
{ build("DEBUG_MultiJobProject", MY_ID: "04") },
{ build("DEBUG_MultiJobProject", MY_ID: "05") },
{ build("DEBUG_MultiJobProject", MY_ID: "06") },
{ build("DEBUG_MultiJobProject", MY_ID: "07") },
{ build("DEBUG_MultiJobProject", MY_ID: "08") },
{ build("DEBUG_MultiJobProject", MY_ID: "09") },
{ build("DEBUG_MultiJobProject", MY_ID: "10") },
{ build("DEBUG_MultiJobProject", MY_ID: "11") },
{ build("DEBUG_MultiJobProject", MY_ID: "12") },
{ build("DEBUG_MultiJobProject", MY_ID: "13") },
{ build("DEBUG_MultiJobProject", MY_ID: "14") },
{ build("DEBUG_MultiJobProject", MY_ID: "15") },
{ build("DEBUG_MultiJobProject", MY_ID: "16") },
{ build("DEBUG_MultiJobProject", MY_ID: "17") },
{ build("DEBUG_MultiJobProject", MY_ID: "18") },
{ build("DEBUG_MultiJobProject", MY_ID: "19") },
{ build("DEBUG_MultiJobProject", MY_ID: "20") },
{ build("DEBUG_MultiJobProject", MY_ID: "21") },
{ build("DEBUG_MultiJobProject", MY_ID: "22") },
{ build("DEBUG_MultiJobProject", MY_ID: "23") },
{ build("DEBUG_MultiJobProject", MY_ID: "24") },
{ build("DEBUG_MultiJobProject", MY_ID: "25") },
{ build("DEBUG_MultiJobProject", MY_ID: "26") },
{ build("DEBUG_MultiJobProject", MY_ID: "27") },
{ build("DEBUG_MultiJobProject", MY_ID: "28") },
{ build("DEBUG_MultiJobProject", MY_ID: "29") },
{ build("DEBUG_MultiJobProject", MY_ID: "30") },
{ build("DEBUG_MultiJobProject", MY_ID: "31") },
{ build("DEBUG_MultiJobProject", MY_ID: "32") },
{ build("DEBUG_MultiJobProject", MY_ID: "33") },
{ build("DEBUG_MultiJobProject", MY_ID: "33") },
{ build("DEBUG_MultiJobProject", MY_ID: "34") },
{ build("DEBUG_MultiJobProject", MY_ID: "35") },
{ build("DEBUG_MultiJobProject", MY_ID: "36") },
{ build("DEBUG_MultiJobProject", MY_ID: "37") },
{ build("DEBUG_MultiJobProject", MY_ID: "38") },
{ build("DEBUG_MultiJobProject", MY_ID: "39") },
{ build("DEBUG_MultiJobProject
[JIRA] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
dogfood commented on JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL Integrated in jenkins_main_trunk #3646 [FIXED JENKINS-24316] Fixed unknown task icon src path construction (Revision 830a5e7f618a53a4ff3d1cad1127efc5fcc47601) Readd static resource path for task icons JENKINS-24316 (Revision 5b805fa16e240e3657a7f263eeef11281a393efa) Result = SUCCESS Jesse Glick : 830a5e7f618a53a4ff3d1cad1127efc5fcc47601 Files : test/src/test/resources/lib/layout/IconTest/03_testTask.jelly test/src/test/java/lib/layout/IconTest.java core/src/main/resources/lib/layout/task.jelly test/src/test/resources/lib/layout/IconTest/01_testIcons.jelly Jesse Glick : 5b805fa16e240e3657a7f263eeef11281a393efa Files : core/src/main/resources/lib/layout/task.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24406) 'Inject variables as a build step' resets slave's system path
lata kopalle created JENKINS-24406 'Inject variables as a build step' resets slave's system path Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: envinject Created: 25/Aug/14 10:18 AM Description: Using 'Inject variables as a build step', either through 'Properties File Path' or 'Properties Content', resets the system Path for subsequent build steps. Printing out the env before using this step matches the slave's system path variable, but after injecting variables as a build step, the new env printed shows a different path value, unsure where this new value is being set from, i couldn't map it to anything in our env, yet. The new path ofcourse messes with build environment. Environment: Jenkins Version: 1.532.1 EnvInject Plugin Version: 1.88 Slave: Windows 7 Master: RHEL 5.8 Project: Jenkins Priority: Major Reporter: lata kopalle This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Shannon Kerr commented on JENKINS-9104 Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed I just ran into this one for the first time as far as I can tell. I did a quick look back and see no other instances and I don't recall seeing this before. For now, I'll take no action. Daniel Beck or anyone else, please let me know if I can provide you with any information that could help in resolving this. Build env where we saw this error: MS Win 7 x64, VS2010 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21739) links to robot framework report files are invalid when inside a folder
jpiironen commented on JENKINS-21739 links to robot framework report files are invalid when inside a folder Sorry for the late reply. The fix by Régis is now merged to the master branch. Thank you so much for the contribution! We recently started working towards a new release, which should be expected soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-19378) git exclusion incorrectly excludes a commit author that was not in exclusion list
Curtis Wilson resolved JENKINS-19378 as Fixed git exclusion incorrectly excludes a commit author that was not in exclusion list We were able to workaround this by setting the "force polling from workspace" option Change By: Curtis Wilson (25/Aug/14 4:33 PM) Status: Open Resolved Assignee: Nicolas De Loof 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] [gitlab-hook] (JENKINS-24403) Cannot create jobs for branches under ldap authentication
Javier Palacios created JENKINS-24403 Cannot create jobs for branches under ldap authentication Issue Type: Bug Assignee: Unassigned Components: gitlab-hook Created: 25/Aug/14 9:34 AM Description: When the authentication realm is set to ldap plus 'authenticated users can do anything', the plugin is not able to create jobs for branches, giving the error below. SEVERE: anonymous is missing the Job/Create permission hudson.security.AccessDeniedException2: anonymous is missing the Job/Create permission I've tried to mimic the elevated_privilege block on job creation, but I've never get a different message (in particular, no reference to SYSTEM user). In fact, I guess that elevated_privilege does not work at all with that authentication configuration, because we have full read permisisons, and commenting out the privilege elevation code does not change the plugin behaviour. Project: Jenkins Priority: Blocker Reporter: Javier Palacios This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs] (JENKINS-24425) Using both NodeJS and Rbenv build environment plugins, rbenv is unable to create .rbenv.lock directory
Dsand Gathr created JENKINS-24425 Using both NodeJS and Rbenv build environment plugins, rbenv is unable to create .rbenv.lock directory Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Screen Shot 2014-08-25 at 5.29.17 PM.png, Screen Shot 2014-08-25 at 5.41.40 PM.png Components: nodejs, rbenv Created: 25/Aug/14 9:43 PM Description: When selecting 'Provide Node & npm bin/ folder to PATH' and 'rbenv build wrapper', the rbenv plugin is unable to create the .rbenv.lock directory. Look at screenshots for configuration and logs Environment: Both linux and mac(10.9.4), latest versions of nodejs and rbenv plugins Project: Jenkins Priority: Major Reporter: Dsand Gathr This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-8963) Remote API to create/delete/modify promotions
SCM/JIRA link daemon commented on JENKINS-8963 Remote API to create/delete/modify promotions Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/promoted_builds/PromotionProcess.java src/test/java/hudson/plugins/promoted_builds/RemoteApiTest.java http://jenkins-ci.org/commit/promoted-builds-plugin/2ceec77c9c12a7a5940b338045c35e59aab797ce Log: JENKINS-8963 Verify baseline functionality of GET/POST config.xml; be sure to pick up ACL from parent project, not Jenkins root. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-8963) Remote API to create/delete/modify promotions
Jesse Glick started work on JENKINS-8963 Remote API to create/delete/modify promotions Change By: Jesse Glick (25/Aug/14 3:28 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] [core] (JENKINS-21437) Failed to update /computer/xxxxxxxxxxx/builds
Jesse Glick assigned JENKINS-21437 to Jesse Glick Failed to update /computer/xxx/builds Change By: Jesse Glick (25/Aug/14 2:03 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21437) Failed to update /computer/xxxxxxxxxxx/builds
Jesse Glick updated JENKINS-21437 Failed to update /computer/xxx/builds Change By: Jesse Glick (25/Aug/14 2:04 PM) Labels: exception lts-candidate threads This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase] (JENKINS-10818) Clearcase plugin does not compile on JDK 7
SCM/JIRA link daemon commented on JENKINS-10818 Clearcase plugin does not compile on JDK 7 Code changed in jenkins User: Charles Simpson Path: pom.xml http://jenkins-ci.org/commit/snsnotify-plugin/a6defdae41257a65215fe2e8ce039e6d7ee4131b Log: Bump parent version Bump parent pom version so that tests will run in Java 7. See https://issues.jenkins-ci.org/browse/JENKINS-10818 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-9259) Include promotion status in the JSON/XML for a build
Jesse Glick resolved JENKINS-9259 as Fixed Include promotion status in the JSON/XML for a build Was fixed in 2.12 but I guess the JIRA link daemon was down. Change By: Jesse Glick (25/Aug/14 2:40 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24426) Jenkins version 1.575 killing processes at end of shell script
Reinhard Karbas created JENKINS-24426 Jenkins version 1.575 killing processes at end of shell script Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: core, slave-setup Created: 25/Aug/14 9:50 PM Description: It looks to me like the fix for Killing processes started by builds on Unix was broken as of 1.553. (issue 22641) has broken the way how Jenkins scripts are executed on a Linux host With version 1.575 when the shell script running the commands exits it now sends signal 15 which kills all child processes that have been started rendering our Linux test system unusable as sshd is being killed. This was not the case in 1.574, which I had to revert to to get this working properly again. Environment: Linux Jenkins Server, Linux slave Project: Jenkins Priority: Major Reporter: Reinhard Karbas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22294) Priority is not used in the scheduling
Markus Strand commented on JENKINS-22294 Priority is not used in the scheduling Interesting. the Problem is not with static priorities, but with the priority parameter. I start the builds in "reverse priority order". The build queue in the job page shows them sorted in priority order: pending #27 cancel this build (pending—Waiting for next available executor on foobar) BuildPriority=6 pending #26 cancel this build (pending—Waiting for next available executor on foobar) BuildPriority=4 pending #25 cancel this build (pending—Waiting for next available executor on foobar) BuildPriority=3 pending #24 cancel this build (pending—Waiting for next available executor on foobar) BuildPriority=2 pending #23 cancel this build (pending—Waiting for next available executor on foobar) BuildPriority=1 In progress > Console Output #22 Aug 25, 2014 7:56:28 AM [cancel] The queue is all with the same priority: Aug 25, 2014 7:57:27 AM FINER PrioritySorter.Queue.Sorter Queue: -- Item Id Job Name Priority Weight -- 5921 testPriorityN 5 5.0 5922 testPriorityN 5 5.0 5923 testPriorityN 5 5.0 5924 testPriorityN 5 5.0 -- Aug 25, 2014 7:57:29 AM FINE PrioritySorter.Queue.Sorter Sorted 4 Buildable Items with Min Weight 5 and Max Weight 5 Aug 25, 2014 7:57:29 AM FINER PrioritySorter.Queue.Sorter Queue: -- Item Id Job Name Priority Weight -- 5921 testPriorityN 5 5.0 5922 testPriorityN 5 5.0 5923 testPriorityN 5 5.0 5924 testPriorityN 5 5.0 -- Aug 25, 2014 7:57:29 AM FINE PrioritySorter.Queue.Items Starting: Id: 5921, JobName: testPriorityN, jobGroupId: 0, reason: , priority: 5, weight: 5.0, status: BUILDABLE Aug 25, 2014 7:57:29 AM FINE PrioritySorter.Queue.Sorter Sorted 3 Buildable Items with Min Weight 5 and Max Weight 5 Aug 25, 2014 7:57:29 AM FINER PrioritySorter.Queue.Sorter Queue: -- Item Id Job Name Priority Weight -- 5922 testPriorityN 5 5.0 5923 testPriorityN 5 5.0 5924 testPriorityN 5 5.0 -- Aug 25, 2014 7:57:32 AM FINE PrioritySorter.Queue.Sorter Sorted 3 Buildable Items with Min Weight 5 and Max Weight 5 Aug 25, 2014 7:57:32 AM FINER PrioritySorter.Queue.Sorter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-24122) github service being removed when saving on the "configure jenkins" page
Stuart Whelan commented on JENKINS-24122 github service being removed when saving on the "configure jenkins" page I am getting the same issue with 1.576 running on Windows 2k8r2. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [metadata-plugin] (JENKINS-22532) 404 Error returned by MetadataChecks on configure pages when jenkins not at server root
SCM/JIRA link daemon resolved JENKINS-22532 as Fixed 404 Error returned by MetadataChecks on configure pages when jenkins not at server root Change By: SCM/JIRA link daemon (25/Aug/14 1:38 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] [github] (JENKINS-24421) Github webhook throwing "Form too large"
Matthew Wilson created JENKINS-24421 Github webhook throwing "Form too large" Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: github Created: 25/Aug/14 7:50 PM Description: Aug 25, 2014 7:40:56 PM WARNING org.eclipse.jetty.util.log.JavaUtilLog warn Error while serving https://myjenkinsserver/github-webhook/ 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$2.dispatch(MetaClass.java:164) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) 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.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:135) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) 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) a
[JIRA] [promoted-builds] (JENKINS-11972) Cannot create job with promoted build plugin automatically using jenkins API
Jesse Glick commented on JENKINS-11972 Cannot create job with promoted build plugin automatically using jenkins API @zhh the copy-job command itself does nothing special, but CopyListener in the plugin handles copying of promotions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector] (JENKINS-24243) Add ability to disable using the global configured proxy
Jørgen Jervidalo commented on JENKINS-24243 Add ability to disable using the global configured proxy It seems like Artifact Resolver ignores no proxy host-list in Jenkins config. https://github.com/jenkinsci/repository-connector-plugin/pull/3/files#diff-fc716ec217fac95888eb1b7190b8eb52R104 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21437) Failed to update /computer/xxxxxxxxxxx/builds
Jesse Glick updated JENKINS-21437 Failed to update /computer/xxx/builds Change By: Jesse Glick (25/Aug/14 2:06 PM) Labels: exception lts-candidate regression threads This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24427) P4 Trust error show up when integrate Parameterize Trigger Plugin
dan tran commented on JENKINS-24427 P4 Trust error show up when integrate Parameterize Trigger Plugin This problem is intermittent, I am able to get my build pipeline working occasionally without this error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-24182) Disk Usage plugin throws severe exception in latest release and prevents maven jobs from loading
Peter Kolínek commented on JENKINS-24182 Disk Usage plugin throws severe exception in latest release and prevents maven jobs from loading Same here with disk usage 0.24 on Jenkins LTS 1.554.2. Downgrade to 0.23 works. Only some jobs throw exception and are hidden during start-up. Those hidden are some Maven-type jobs, but not all of them. Each job which had this problem was created as a copy of other job ( if that helps in any way ). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24405) Validation of Subversion URL should ignore @$Var (Ie. variable peg-revision)
Markus Eisenmann created JENKINS-24405 Validation of Subversion URL should ignore @$Var (Ie. variable peg-revision) Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: subversion Created: 25/Aug/14 10:06 AM Description: Hi! It‘s already possible to limit the validation of a subversion URL only up to the first $ sign. But, if I use a variable to specify the peg-revision (may containing a number or “HEAD”) and the @character is used as (prefix) part within the URL, like: https://anyhost/svn/project/trunk/GMC@$Revision The job-configuration does display the error-message: "/trunk/GMC@" doesn't exist in the repository. Maybe you meant "/trunk/GMC"? In my opinion, the limited URL-validation should also recognize this pattern; Ie. Validation should be done up to the first $-sign (as now) or the first @$-pair; if the corresponding configuration (within global settings) is set. Best regards from Salzburg, Markus Project: Jenkins Priority: Minor Reporter: Markus Eisenmann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21437) Failed to update /computer/xxxxxxxxxxx/builds
dogfood commented on JENKINS-21437 Failed to update /computer/xxx/builds Integrated in jenkins_main_trunk #3648 [FIXED JENKINS-21437] Mismatched synchronization monitor. (Revision 03b31a2361b4bc00cac6c1545ee8300fca5bd8a3) Result = SUCCESS Jesse Glick : 03b31a2361b4bc00cac6c1545ee8300fca5bd8a3 Files : changelog.html core/src/main/java/jenkins/widgets/RunListProgressiveRendering.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-24084) Slave file leak build is interrupted during Copy Artifacts build step
mrobinet
updated JENKINS-24084
Slave file leak build is interrupted during Copy Artifacts build step
Change By:
mrobinet
(25/Aug/14 1:19 PM)
Description:
Slave processes are having file locks to files in the workspace hanging around after builds are interrupted during copy artifacts step.I used http://file-leak-detector.kohsuke.org/ to get a stack trace of the lock:
{code:title=File leak detector output}
#12 C:\jenkins\workspace\Browser Tests (QA)\BrowserType\InternetExplorer32\OS\windows\TestCategory\JourneyTest02\Bin\Release\Test\Quartz.pdb by thread:pool-1-thread-1178 for channel on Thu Aug 21 07:28:35 CDT 2014 at java.io.FileOutputStream.(Unknown Source) at java.io.FileOutputStream.(Unknown Source) at hudson.FilePath$32.call(FilePath.java:1715) at hudson.FilePath$32.call(FilePath.java:1710) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source)
{code}
The build log
for the build that corresponds to the file lock timestamp
shows:
{code:title=Build console log output}
ERROR: Failed to copy artifacts from Build Empower with filter: Bin/*/Test/**/*.*,Build/**/*.*,Bin/*.runsettingshudson.util.IOException2: Failed to copy C:\jenkins\jobs\Build Empower\builds\2014-08-20_13-38-06\archive\Bin\Release\Test\Quartz.pdb to C:\jenkins\workspace\Browser Tests (QA)\BrowserType\InternetExplorer32\OS\windows\TestCategory\JourneyTest02\Bin\Release\Test\Quartz.pdb at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyOne(FingerprintingCopyMethod.java:107) at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyAll(FingerprintingCopyMethod.java:68) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:396) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:327) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:535) at hudson.model.Run.execute(Run.java:1732) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234)Caused by: java.io.InterruptedIOException at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.writeBlock(NioChannelHub.java:212) at hudson.remoting.AbstractByteArrayCommandTransport.write(AbstractByteArrayCommandTransport.java:83) at hudson.remoting.Channel.send(Channel.java:545) at hudson.remoting.ProxyOutputStream._write(ProxyOutputStream.java:163) at hudson.remoting.ProxyOutputStream.write(ProxyOutputStream.java:109) at hudson.remoting.RemoteOutputStream.write(RemoteOutputStream.java:110) at java.security.DigestOutputStream.write(Unknown Source) at hudson.remoting.RemoteOutputStream.write(RemoteOutputStream.java:110) at hudson.Util.copyStream(Util.java:461) at hudson.FilePath$37.invoke(FilePath.java:1845) at hudson.FilePath$37.invoke(FilePath.java:1839) at hudson.FilePath.act(FilePath.java:922) at hudson.FilePath.act(FilePath.java:895) at hudson.FilePath.copyTo(FilePath.java:1839) at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyOne(FingerprintingCopyMethod.java:79) ... 12 moreCaused by: java.lang.InterruptedException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:503) at org.jenkinsci.remoting.nio.FifoBuffer.write(FifoBuffer.java:336) at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.writeBlock(NioChannelHub.java:207) ... 26 moreBuild step 'Copy artifacts from another project' marked build as failure
{code}
I'm guessing there was a network hiccup of some sort
that caused the slave to mom
[JIRA] [cluster-stats] (JENKINS-23712) Exceptions in multi-conf jobs and concurrents executions
toomasr edited a comment on JENKINS-23712 Exceptions in multi-conf jobs and concurrents executions I did some changes: Had to bump the dependency version to 1.557 I thought 1.520 is enough but then I stumbled on JENKINS-23712 Also synchronized the file saving that should fix the problem Release 0.4.5 version Let me know if this solves your issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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
Bart M commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials I also seem to have the same problem, but my SVN externals are all on the same SVN server, accessible with the same credentials. It's strange though, when the CI build triggered by the change fails, and you just force it to build again, it works fine. It only seems to happen the first time svn had to update something (in the main checked out repo, not in one of the externals), if nothing changed in the checked out repository, everything continues as expected. If something updated - it fails with the "hudson.util.IOException2: revision check failed on http://svnserver/path/to/external" exception. We also use the '^' everywhere in our externals btw... I'm running Jenkins ver. 1.575 with SVN plugin ver. 2.4.3. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22333) Possibility to transfer promotion config via REST API (promotion config needed in job config.xml)
Jesse Glick resolved JENKINS-22333 as Duplicate Possibility to transfer promotion config via REST API (promotion config needed in job config.xml) Change By: Jesse Glick (25/Aug/14 2:37 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] [p4] (JENKINS-24427) P4 Trust error show up when integrate Parameterize Trigger Plugin
dan tran created JENKINS-24427 P4 Trust error show up when integrate Parameterize Trigger Plugin Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: p4 Created: 25/Aug/14 10:40 PM Description: I have a start job on Maser Linux which dump p4 changelist number into a properties file, and use Parameterize Trigger Plugin to spin other slaves Unix slaves takes turn to pop this error Started by upstream project "authc-java-snapshot" build number 110 originally caused by: Started by user trand8 [EnvInject] - Loading node environment variables. Building on master in workspace /data/trand8/.jenkins/jobs/authc-linux-x64-snapshot/workspace P4: Unable to connect: com.perforce.p4java.exception.ConnectionException: * WARNING PERFORCE SERVER IDENTIFICATION HAS CHANGED! * It is possible that someone is intercepting your connection to the Perforce server 'p4brsb.lss.emc.com:1666' If this is not a scheduled key change, then you should contact your Perforce administrator. The fingerprint for the mismatched key sent to your client is 71:FB:BD:1A:FA2:EF8:A7:12:70:B5:61:01:4F:2F:46:B1:BF:C3 Can't trust mismatched Perforce server key without both 'force' and 'autoAccept' options. P4: Unable to use Workspace: java.lang.NullPointerException P4: Unable to close Perforce connection: java.lang.NullPointerException ERROR: Unable to update workspace: java.lang.NullPointerException Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered Notifying upstream build authc-java-snapshot #110 of job completion Project authc-java-snapshot still waiting for [authc-windows-x64-snapshot, authc-solaris-sparcv9-snapshot] builds to complete Notifying upstream projects of job completion Notifying upstream of completion: authc-java-snapshot #110 Finished: FAILURE Also notice that .p4trust updated for each build. There my be some concurrent write/read issue? I dont see the error on normal post job trigger, and it also does not show up at Perforce Plugin ( the one uses p4 exe) Environment: linux on master, slaves are on linux, windows, solaris. Unix's home directory is from same NFS mount Project: Jenkins Priority: Critical Reporter: dan tran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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] (JENKINS-24409) Docker Plugin issues link using wrong component ID
aaron axisa created JENKINS-24409 Docker Plugin issues link using wrong component ID Issue Type: Bug Assignee: Unassigned Components: docker, jira Created: 25/Aug/14 12:09 PM Description: The page for Docker plugin contains a link for open issues. said link redirects to a query for components called "docker-plugin" whereas the actual name is "docker" resulting in a failed query. https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin Project: Jenkins Priority: Minor Reporter: aaron axisa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24312) NPE if session was left open for a longer time
Björn Pedersen resolved JENKINS-24312 as Fixed NPE if session was left open for a longer time probably a duplicate of 24317 Change By: Björn Pedersen (25/Aug/14 12:45 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] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
Yoann Dubreuil commented on JENKINS-23693 Cannot delete workspace We also hit the issue in version 0.22. I don't have a case to reproduce, but referring to the following stacktrace, I think it's required to check for null before calling get(command) on EnvVars Aug 19, 2014 6:23:15 PM hudson.plugins.ws_cleanup.WsCleanup perform SEVERE: null java.lang.NullPointerException at hudson.util.CaseInsensitiveComparator.compare(CaseInsensitiveComparator.java:40) at hudson.util.CaseInsensitiveComparator.compare(CaseInsensitiveComparator.java:34) at java.util.TreeMap.getEntryUsingComparator(TreeMap.java:369) at java.util.TreeMap.getEntry(TreeMap.java:340) at java.util.TreeMap.get(TreeMap.java:273) at hudson.plugins.ws_cleanup.Cleanup.(Cleanup.java:35) at hudson.plugins.ws_cleanup.WsCleanup.perform(WsCleanup.java:165) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) I will propose a PR with the null check if it works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24352) Unneccessary line breaks in JUnit test results table since 1.576
Lars W commented on JENKINS-24352 Unneccessary line breaks in JUnit test results table since 1.576 Same with the tables in the side panel (build processor, build history, ...) with certain screen resolutions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24420) Add job-dsl-plugin support for delivery-pipeline-plugin
Patrik Boström created JENKINS-24420 Add job-dsl-plugin support for delivery-pipeline-plugin Issue Type: New Feature Assignee: Daniel Spilker Components: job-dsl-plugin Created: 25/Aug/14 5:40 PM Description: Add job-dsl-plugin support for delivery-pipeline-plugin Should support: Creation of Delivery Pipeline View Stage name and Task name for Jobs Support for pipeline version creation Project: Jenkins Priority: Major Reporter: Patrik Boström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21437) Failed to update /computer/xxxxxxxxxxx/builds
SCM/JIRA link daemon commented on JENKINS-21437 Failed to update /computer/xxx/builds Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/jenkins/widgets/RunListProgressiveRendering.java http://jenkins-ci.org/commit/jenkins/03b31a2361b4bc00cac6c1545ee8300fca5bd8a3 Log: [FIXED JENKINS-21437] Mismatched synchronization monitor. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24413) java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction
Riccardo Gorza created JENKINS-24413 java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext, jabber Created: 25/Aug/14 2:06 PM Description: Build-status notifiers fail with the same exception: WARNING: Publisher hudson.plugins.jabber.im.transport.JabberPublisher aborted due to exception java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; at hudson.plugins.im.build_notify.PrintFailingTestsBuildToChatNotifier.getFailedTestsReport(PrintFailingTestsBuildToChatNotifier.java:68) at hudson.plugins.im.build_notify.PrintFailingTestsBuildToChatNotifier.buildCompletionMessage(PrintFailingTestsBuildToChatNotifier.java:37) at hudson.plugins.im.IMPublisher.notifyChatsOnBuildEnd(IMPublisher.java:577) at hudson.plugins.im.IMPublisher.notifyOnBuildEnd(IMPublisher.java:304) at hudson.plugins.im.IMPublisher.perform(IMPublisher.java:291) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1765) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) OR WARNING: Publisher hudson.plugins.emailext.ExtendedEmailPublisher aborted due to exception java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; at hudson.plugins.emailext.plugins.content.FailedTestsContent.evaluate(FailedTestsContent.java:47) at org.jenkinsci.plugins.tokenmacro.DataBoundTokenMacro.evaluate(DataBoundTokenMacro.java:189) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:182) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:233) at hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:71) at hudson.plugins.emailext.ExtendedEmailPublisher.getContent(ExtendedEmailPublisher.java:597) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:476) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:290) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:281) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:233) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1786) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) Environment: Jenkins 1.577, CentOS 6.5, Java 7 Project: Jenkins Priority: Major Reporter: Riccardo Gorza
[JIRA] [docker] (JENKINS-24408) docker plugin throwing NumberFormatException when trying to connect to docker from jenkins
aaron axisa created JENKINS-24408 docker plugin throwing NumberFormatException when trying to connect to docker from jenkins Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: docker Created: 25/Aug/14 12:02 PM Description: I am running docker using the following command: docker -d -H tcp://127.0.0.1:4243 I have tried opening the port just in case using the following commands firewall-cmd --zone=dmz --add-port=4243/tcp --permanent firewall-cmd --reload I have set up the jenkins-1 docker image on the machine according to the wiki page of the plugin under Creating a docker image https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin Under Configure System on Jenkins i added the Cloud for the Docker plugin Name: localDocker DockerURL : http://localhost:4243 Connection Timeout 5 (default) Read Timeout 15 (default) Then I press Test Connection and I get the followign stack trace: javax.servlet.ServletException: java.lang.NumberFormatException: For input string: "1-dev" at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 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.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:615) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportVa
[JIRA] [postbuild-task] (JENKINS-24418) Getting NullPointer exception while executing post build steps (after successful build)
Daniel Beck commented on JENKINS-24418 Getting NullPointer exception while executing post build steps (after successful build) sean head: Make sure you're not running 1.576, it's known to throw NPEs all over. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-8963) Remote API to create/delete/modify promotions
SCM/JIRA link daemon commented on JENKINS-8963 Remote API to create/delete/modify promotions Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/hudson/plugins/promoted_builds/JobPropertyImpl.java src/test/java/hudson/plugins/promoted_builds/RemoteApiTest.java http://jenkins-ci.org/commit/promoted-builds-plugin/ca0b5e516bb37e0b3000422c93d2cde05dc560b8 Log: JENKINS-8963 Make existing REST API for deletion work naturally. Compare: https://github.com/jenkinsci/promoted-builds-plugin/compare/2ceec77c9c12...ca0b5e516bb3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cluster-stats] (JENKINS-23712) Exceptions in multi-conf jobs and concurrents executions
toomasr resolved JENKINS-23712 as Fixed Exceptions in multi-conf jobs and concurrents executions Change By: toomasr (25/Aug/14 8:22 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24417) email-ext Content Token Reference help info: after first list, it repeats each item hundreds of times
m_broida commented on JENKINS-24417 email-ext Content Token Reference help info: after first list, it repeats each item hundreds of times e-mail-ext changelog suggests a similar problem may have been fixed in version 2.28. But this is present in version 2.36, and nothing in changelog since then (or in open issues) seems to match. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24405) Validation of Subversion URL should ignore @$Var (Ie. variable peg-revision)
Markus Eisenmann updated JENKINS-24405 Validation of Subversion URL should ignore @$Var (Ie. variable peg-revision) Change By: Markus Eisenmann (25/Aug/14 10:09 AM) Description: Hi!It‘s already possible to limit the validation of a subversion URL only up to the first $ sign.But, if I use a variable to specify the peg-revision (may containing a number or “HEAD”) and the @- character '@' is used as (prefix-) part within the URL, like:https://anyhost/svn/project/trunk/GMC@$RevisionThe job-configuration does display the error-message:"/trunk/GMC@" doesn't exist in the repository. Maybe you meant "/trunk/GMC"?In my opinion, the limited URL-validation should also recognize this pattern; Ie. Validation should be done up to the first $-sign (as now) or the first @$-pair; if the corresponding configuration (within global settings) is set.Best regards from Salzburg,Markus This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testlink] (JENKINS-24424) TestLink Plugin - Does not show "Execution Status"
Sahaja Koorapati created JENKINS-24424 TestLink Plugin - Does not show "Execution Status" Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: Jenkins_Build_status.jpeg Components: testlink Created: 25/Aug/14 9:09 PM Description: I have used Jenkins Testlink plugin to trigger test cases and it went through fine. But the Testlink execution status always shows "Not Run". It produces a Junit result xml file. Please find the Build status screenshot I have tried "Publish JUnit test reports", just to make sure there is nothing wrong with the result xml. And it is working fine. Please let me know if it is an issue with Test link plugin, or let me know if there is any other way to capture Testlink results. Thank you in advance! Due Date: 27/Aug/14 12:00 AM Project: Jenkins Priority: Major Reporter: Sahaja Koorapati This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-multijob-plugin] (JENKINS-24419) Builds fail/skip randomly without reason given.
Daniel Beck updated JENKINS-24419 Builds fail/skip randomly without reason given. Change By: Daniel Beck (26/Aug/14 2:03 AM) Component/s: jenkins-multijob-plugin Component/s: core Component/s: multi-slave-config This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24402) jsch version
ivanm created JENKINS-24402 jsch version Issue Type: Improvement Assignee: Unassigned Components: ssh Created: 25/Aug/14 9:27 AM Description: Sometimes, SSH plugin return this error: /some/script [SSH] Exception:verify: false com.jcraft.jsch.JSchException: verify: false at com.jcraft.jsch.Session.connect(Session.java:295) at com.jcraft.jsch.Session.connect(Session.java:150) at org.jvnet.hudson.plugins.SSHSite.createSession(SSHSite.java:141) at org.jvnet.hudson.plugins.SSHSite.executeCommand(SSHSite.java:151) at org.jvnet.hudson.plugins.SSHBuilder.perform(SSHBuilder.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:535) at hudson.model.Run.execute(Run.java:1740) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:233) According to this post, this error has been fixed in jsch 0.1.50. Would it be possible to use latest version of this dependency? Project: Jenkins Priority: Major Reporter: ivanm This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [postbuild-task] (JENKINS-24418) Getting NullPointer exception while executing post build steps (after successful build)
Premkumar Dhanarajan created JENKINS-24418 Getting NullPointer exception while executing post build steps (after successful build) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: postbuild-task Created: 25/Aug/14 4:16 PM Description: I have configured a post build action to deploy the bundles in Archiva repository. But I sometimes get the below error intermittently while executing the post build action step. This does not happen always but at sometimes. ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.NullPointerException at hudson.maven.MavenModuleSetBuild$1.isDescendantOf(MavenModuleSetBuild.java:246) at hudson.maven.MavenModuleSetBuild$1.(MavenModuleSetBuild.java:215) at hudson.maven.MavenModuleSetBuild.getChangeSetFor(MavenModuleSetBuild.java:208) at hudson.maven.FilteredChangeLogSet.(FilteredChangeLogSet.java:51) at hudson.maven.MavenBuild.getChangeSet(MavenBuild.java:183) at hudson.tasks.MailSender.appendBuildUrl(MailSender.java:216) at hudson.tasks.MailSender.createBackToNormalMail(MailSender.java:181) at hudson.tasks.MailSender.getMail(MailSender.java:168) at hudson.tasks.MailSender.execute(MailSender.java:100) at hudson.maven.reporters.MavenMailer.end(MavenMailer.java:55) at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:103) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:758) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:593) at hudson.model.Run.execute(Run.java:1567) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) project=hudson.maven.MavenModuleSet@77dbb506[DGW_Release_6_Build] project.getModules()=[hudson.maven.MavenModule@58759e1d[DGW_Release_6_Build/com.centurylink.dgw:dgwmanualrepairschema][DGW_Release_6_Build/com.centurylink.dgw:dgwmanualrepairschema][relativePath:DGWManualRepairSchema], hudson.maven.MavenModule@38e0028d[DGW_Release_6_Build/com.centurylink.dgw:dgwprocessor][DGW_Release_6_Build/com.centurylink.dgw:dgwprocessor][relativePath:DGWProcessor], hudson.maven.MavenModule@7e6a41ea[DGW_Release_6_Build/com.centurylink.dgw:dgwschema][DGW_Release_6_Build/com.centurylink.dgw:dgwschema][relativePath:DGWSchema], hudson.maven.MavenModule@2b029273[DGW_Release_6_Build/com.centurylink.dgw:dgwstatusreporterschema][DGW_Release_6_Build/com.centurylink.dgw:dgwstatusreporterschema][relativePath:DGWStatusReporterSchema], hudson.maven.MavenModule@3c3173ad[DGW_Release_6_Build/com.centurylink.dgw:dgwworkflow][DGW_Release_6_Build/com.centurylink.dgw:dgwworkflow][relativePath:DGWWorkflow]] project.getRootModule()=hudson.maven.MavenModule@3c3173ad[DGW_Release_6_Build/com.centurylink.dgw:dgwworkflow][DGW_Release_6_Build/com.centurylink.dgw:dgwworkflow][relativePath:DGWWorkflow] FATAL: null Environment: I running Jenkins 1.503v on tomcat server. The SCM tool used is dimensions and build is performed using Maven build XML. The resulting bundles are deployed in Archiva Maven repository post successful build completion. Fix Versions: current Project: Jenkins Priority: Critical Reporter: Premkumar Dhanarajan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administra
[JIRA] [build-timeout] (JENKINS-7832) Hudson build time is calculated from the time job enters the queue while it should be when job actually starts to run
Daniel Klingensmith commented on JENKINS-7832 Hudson build time is calculated from the time job enters the queue while it should be when job actually starts to run This is still an issue for me running 1.558. I am seeing this consistently happen across 5 build configurations. Let me know which information is needed to dissect 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] [core] (JENKINS-24407) missing weather icons (randomly?)
K P created JENKINS-24407 missing weather icons (randomly?) Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: broken_weather.png, weather_img_notOK.png, weather_img_OK.png Components: core Created: 25/Aug/14 11:01 AM Description: Since Jenkins 1.576 (running as Windows service), some weather icons are missing. Instead, only the percentage is printed. This happens for some jobs, not for others. (it happen to be Maven jobs, I don't know whether that is relevant). This issue started in 1.576 (where also some plugin icons in the sidebar went missing), but persists in the latest 1.577. Note that the image apparently is loaded correctly, as some other jobs in the same percentage range get their icon printed correctly. When looking at the html sources of the broken icons, the img tag seems to be missing the src attributes with the image filename. Note that the same issue also occurs on the project details page, where the weather icons is normally printed at the top of the recent builds list. Environment: Windows Server, running Jenkins 1.576 or 1.577 as service. Project: Jenkins Priority: Major Reporter: K P This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-24416) Reverse proxy auth is preventing SSH CLI access
Lieuwe Hummel created JENKINS-24416 Reverse proxy auth is preventing SSH CLI access Issue Type: Bug Assignee: Unassigned Components: cli, reverse-proxy-auth Created: 25/Aug/14 3:28 PM Description: When trying to perform a CLI action using SSH, the reverse proxy auth plugin can not find the username. It gives a stack trace and exits. FYI: i filed another issue relating to Reverse Proxy Auth as well. It may or may not be related: JENKINS-24415 Stack trace $ ssh jenkins.company.com help org.acegisecurity.userdetails.UsernameNotFoundException: myUserName at org.jenkinsci.plugins.reverse_proxy_auth.ReverseProxySecurityRealm$3.loadUserByUsername(ReverseProxySecurityRealm.java:108) at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32) at hudson.model.User.impersonate(User.java:282) at org.jenkinsci.main.modules.sshd.AsynchronousCommand$1.run(AsynchronousCommand.java:101) at java.lang.Thread.run(Thread.java:701) Project: Jenkins Labels: plugin authentication cli ssh Priority: Minor Reporter: Lieuwe Hummel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
