[JIRA] [jobconfighistory] (JENKINS-21411) Add option to easily review changes sequentially (Add Next Previous links)
Stefan Brausch stopped work on JENKINS-21411 Add option to easily review changes sequentially (Add Next Previous links) Change By: Stefan Brausch (15/Apr/14 7:30 AM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory] (JENKINS-21411) Add option to easily review changes sequentially (Add Next Previous links)
Stefan Brausch resolved JENKINS-21411 as Fixed Add option to easily review changes sequentially (Add Next Previous links) Feature released in version 2.6 Change By: Stefan Brausch (15/Apr/14 7:31 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-tracker] (JENKINS-22617) Can't delete crash report
R. H. created JENKINS-22617 Cant delete crash report Issue Type: Bug Assignee: Unassigned Attachments: error.png, report.png Components: jenkins-tracker Created: 15/Apr/14 8:07 AM Description: Hello, it's not possible to delete a crash report. Before a few days Jenkins crashed. I go to the Settings section and saw the message: "This Jenkins appears to have crashed. Please check the logs." So when i klick on it i see one crash report. I have checked the report and tried to delete the report. So its not possible to delete the crash report your can see it in the screenshot. I get an 404. More in the Screenshots. Environment: Linux Debian Project: Jenkins Priority: Major Reporter: R. H. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-21003) ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading
Lucie Votypkova commented on JENKINS-21003 ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading It is easiest solution for backward compatibility (it does not need a lot of changes so there is not a big chance for mistake). It is true that your suggestion is faster for loading, I will check the code how complicated it will be. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19246) Configure Project loading overloay not hiding error invalid gitTool selection Default
R. H. closed JENKINS-19246 as Fixed Configure Project loading overloay not hiding error invalid gitTool selection Default The Problem is fixed in the Version 1.559. Change By: R. H. (15/Apr/14 8:08 AM) 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] [git-client] (JENKINS-22119) Fail to update update git repository with stored credential
Michka Popoff commented on JENKINS-22119 Fail to update update git repository with stored credential I just found this bug report as my credentials stopped working with my private bitbucket repo. Removing the @username from the url fixed it. This is quite confusing as this was working before and the behavior of the credentials changed between 1.6.3 and 1.6.4 If the @username can not be stripped, you could perhaps add a hint in the error message telling the user to try without the @username ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-19025) MultiJob marked as aborted when one phase failed
Sampo Niskanen commented on JENKINS-19025 MultiJob marked as aborted when one phase failed Hi, After upgrading Jenkins and MultiJob and adding a few jobs to be MultiJob phase, I'm seeing the same. Additionally it seems that MultiJob aborts some of the child jobs. My speculation on what's going on (at least in my case): MultiJob launches the jobs one of the jobs fails MultiJob (for some reason) aborts one or more of the child jobs since the child job has been aborted, the state of the MultiJob itself is set as aborted This has broken down our entire CI flow, and no results are reliable anymore. Any idea how to fix this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mstestrunner] (JENKINS-22618) NullPointerException at org.jenkinsci.plugins.MsTestBuilder.perform(MsTestBuilder.java:144)
S W created JENKINS-22618 NullPointerException at org.jenkinsci.plugins.MsTestBuilder.perform(MsTestBuilder.java:144) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: mstestrunner Created: 15/Apr/14 10:11 AM Description: I got this error in the console if I try to build a .Net project. The build itself (with msbuild) works Path To MSTest.exe: mstest.exe Result file was not found so no action has been taken. file:/C:/Program%20Files%20(x86)/Jenkins/jobs/UsageStatistic%20Test/workspace/testresult.trx FATAL: null java.lang.NullPointerException at org.jenkinsci.plugins.MsTestBuilder.perform(MsTestBuilder.java:144) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:523) at hudson.model.Run.execute(Run.java:1700) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Environment: Windows Server 2012 Project: Jenkins Labels: exception Priority: Major Reporter: S W This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20769) Failed to execute command Pipe.EOF
Oliver Gondža resolved JENKINS-20769 as Fixed Failed to execute command Pipe.EOF Resolved integrating remoting:2.36 in 75447b57b655e38fdb48f1e854a4b287071342cf. Change By: Oliver Gondža (15/Apr/14 10:22 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit] (JENKINS-22619) JUnit report format from Behat not parsing as valid JUnit XML report
Nick Jones created JENKINS-22619 JUnit report format from Behat not parsing as valid JUnit XML report Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Attachments: example_behat_junit_report.xml Components: xunit Created: 15/Apr/14 10:24 AM Description: When running Behat tests and requesting junit as report output format I am presented with: https://gist.github.com/punkstar/dbdf24408939f560edae. On the surface, this looks like a legitimate junit format and I would expect xUnit to be able to parse it. Is this a bug in the xUnit parsing, or a bug in the Behat generation? If the later, I'll inform the Behat project. Project: Jenkins Priority: Minor Reporter: Nick Jones This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit] (JENKINS-22619) JUnit report format from Behat not parsing as valid JUnit XML report
Nick Jones updated JENKINS-22619 JUnit report format from Behat not parsing as valid JUnit XML report Removed link from issue description, it's already attached. Change By: Nick Jones (15/Apr/14 10:26 AM) Description: Whenrunning[Behat|http://behat.org/]testsandrequestingjunitasreportoutputformatIampresentedwith :https://gist theattached . github.com/punkstar/dbdf24408939f560edae. Onthesurface,thislookslikealegitimatejunitformatandIwouldexpectxUnittobeabletoparseit.IsthisabuginthexUnitparsing,orabugintheBehatgeneration?Ifthelater,IllinformtheBehatproject. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20769) Failed to execute command Pipe.EOF
SCM/JIRA link daemon commented on JENKINS-20769 Failed to execute command Pipe.EOF Code changed in jenkins User: Kohsuke Kawaguchi Path: pom.xml http://jenkins-ci.org/commit/jenkins/a89aa713b2ba5c325cd296d5733a565aa5cc63ec Log: JENKINS-20769 JENKINS-20204 Integrating remoting 2.36 Fixed a bug Jesse found in remoting (cherry picked from commit 75447b57b655e38fdb48f1e854a4b287071342cf) Conflicts: pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20204) Latest release of Java 7 blocks the connection to slaves due to no permissions attribute in the JAR file
SCM/JIRA link daemon commented on JENKINS-20204 Latest release of Java 7 blocks the connection to slaves due to no permissions attribute in the JAR file Code changed in jenkins User: Kohsuke Kawaguchi Path: pom.xml http://jenkins-ci.org/commit/jenkins/a89aa713b2ba5c325cd296d5733a565aa5cc63ec Log: JENKINS-20769 JENKINS-20204 Integrating remoting 2.36 Fixed a bug Jesse found in remoting (cherry picked from commit 75447b57b655e38fdb48f1e854a4b287071342cf) Conflicts: pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22039) Credentialed git init fails with file exists - reuses same tmp dir for all credentials
Marcus Bristol commented on JENKINS-22039 Credentialed git init fails with file exists - reuses same tmp dir for all credentials The "Force polling using workspace" setting seems to have done the trick. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22442) Jetty exploding war to /tmp is a bad idea
SCM/JIRA link daemon commented on JENKINS-22442 Jetty exploding war to /tmp is a bad idea Code changed in jenkins User: Kohsuke Kawaguchi Path: war/pom.xml http://jenkins-ci.org/commit/jenkins/f01a7c2c0ef3cc41ac9513dfbf77c67e65e039be Log: FIXED JENKINS-22442 Avoid extracting war file under /tmp. When jar files and resource files disappear from under us, all sorts of strange errors happen. (cherry picked from commit d927a0c8bea678eb6d179edd786b004bb47a18c5) Conflicts: changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22620) 'Could not checkout null' when trying to checkout sha passed from upstream job
Paulo Matos created JENKINS-22620 Could not checkout null when trying to checkout sha passed from upstream job Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 15/Apr/14 10:47 AM Description: I have been getting the following exception when trying to get an existing sha passed from an upstream job: Started by upstream project "fptools_gcc-25x_test" build number 558 originally caused by: Started by upstream project "fptools_gcc-25x" build number 630 originally caused by: Started by an SCM change EnvInject - Loading node environment variables. Building on master in workspace http://jenkins-cam-04.cam.broadcom.com/job/fptools_gcc-25x_test/archs=fp4014/ws/ Fetching changes from the remote Git repository Fetching upstream changes from dsl-...@eng-cbga-2.cam.broadcom.com:tools/fp_gcc Checking out Revision 79c8eb3d846d09ecedf3b331942d8904cdedf515 (origin/FP_GCC_2_5_X_BRANCH) ERROR: Timeout after 10 minutes FATAL: Could not checkout null with start point 79c8eb3d846d09ecedf3b331942d8904cdedf515 hudson.plugins.git.GitException: Could not checkout null with start point 79c8eb3d846d09ecedf3b331942d8904cdedf515 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:1309) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:888) at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1665) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Caused by: hudson.plugins.git.GitException: Command "git checkout -f 79c8eb3d846d09ecedf3b331942d8904cdedf515" returned status code 143: stdout: stderr: at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1183) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1160) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1156) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:972) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:982) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkout(CliGitAPIImpl.java:1283) at hudson.plugins.git.GitAPI.checkout(GitAPI.java:208) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:1293) ... 9 more Project: Jenkins Priority: Major Reporter: Paulo Matos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [audit-trail] (JENKINS-22602) NullPointerException in AuditTrailFilter.doFilter() when HttpServletRequest.getPathInfo() is null
Cyrille Le Clerc resolved JENKINS-22602 as Fixed NullPointerException in AuditTrailFilter.doFilter() when HttpServletRequest.getPathInfo() is null Fixed in 1.9 Change By: Cyrille Le Clerc (15/Apr/14 11:30 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-22393) Problem deploying EAR to WAS 7
ingmartinlopez commented on JENKINS-22393 Problem deploying EAR to WAS 7 I'm using Standard WebSphere version 7.0.0.13 ... maybe is there a way to skip annotation processing when deploying EARS? Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-22622) Maven incremental build is too eager
Jean Blanchard created JENKINS-22622 Maven incremental build is too eager Issue Type: Bug Affects Versions: current Assignee: Jean Blanchard Components: maven Created: 15/Apr/14 12:50 PM Description: Given a maven multimodule project with multiple levels: top * moduleA * moduleAA * moduleAB * moduleB If a changeset impacts files in moduleAA and moduleB, then moduleA, moduleAA and moduleB are passed to the Maven command, when moduleA should not. This leads to longer build times than necessary I have fixed the issue here, and will have a pull request ready soon. Project: Jenkins Priority: Major Reporter: Jean Blanchard This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22611) Triggered by SCM multiple times
Patrik Boström assigned JENKINS-22611 to Patrik Boström Triggered by SCM multiple times Change By: Patrik Boström (15/Apr/14 12:51 PM) Assignee: PatrikBoströ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] [maven] (JENKINS-22622) Maven incremental build is too eager
Jean Blanchard commented on JENKINS-22622 Maven incremental build is too eager PR: https://github.com/jenkinsci/maven-plugin/pull/21 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-22622) Maven incremental build is too eager
Jean Blanchard started work on JENKINS-22622 Maven incremental build is too eager Change By: Jean Blanchard (15/Apr/14 12:58 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-22623) Jenkins ver. 1.532.3 restart from web problem
Alexandr Y created JENKINS-22623 Jenkins ver. 1.532.3 restart from web problem Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-tracker Created: 15/Apr/14 1:11 PM Description: When i want restart jenkins from web-interface (http://jenkins/restart)i got a mistake A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: hudson.lifecycle.RestartNotSupportedException: Failed to obtain the command line arguments of the process at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) 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:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:85) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) 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:79) 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 winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at
[JIRA] [categorized-view] (JENKINS-22624) Support Jenkins LTS 1.532.1
taksan created JENKINS-22624 Support Jenkins LTS 1.532.1 Issue Type: Bug Assignee: taksan Components: categorized-view Created: 15/Apr/14 1:28 PM Description: The plugin doesn't work on Jenkins 1.532.1 LTS. The problem is described in the following issue: https://github.com/jenkinsci/categorized-view-plugin/issues/2 Project: Jenkins Priority: Major Reporter: taksan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-21579) Very slow resource loading from UberClassLoader
SCM/JIRA link daemon commented on JENKINS-21579 Very slow resource loading from UberClassLoader Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/jenkins/util/AntClassLoader.java http://jenkins-ci.org/commit/jenkins/fd9f273f3645fc670e1283bbed7967f789475c86 Log: FIXED JENKINS-21579 UberClassLoader.findResources() improvements This is just a locally patched version, so not meant to be used outside core. Cherry-picked-from: 9a2882dd704bece9b7ca51a52347dad15d79f843 Compare: https://github.com/jenkinsci/jenkins/compare/f01a7c2c0ef3...fd9f273f3645 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-21579) Very slow resource loading from UberClassLoader
Marco Miller commented on JENKINS-21579 Very slow resource loading from UberClassLoader ed1f1435a016da86ad0321e9acf3389a3c68add3 and 5daaf168a81902d852082f3f03b47e6b78f56981 are the 2 commits by KK fixing this issue. -Which commits I back-ported to 1.554.1 (current 'stable’ branch). I did so after this successful testing of ours: jenkinsci /jenkins unit tests, for regression (passing ones kept passing); jenkinsci /acceptance-test-harness, incl. both parent- and plugin-1st class-loading plugins (failures looked unrelated); Ericsson-internal CLI ‘stress' tests, which used to reproduce JENKINS-22310; incl. parent/plugin-1st plugins, too; brief manual testing through quick clicking-around, exercising some parent+plugin-1st (plugins) class-loading. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-21579) Very slow resource loading from UberClassLoader
SCM/JIRA link daemon commented on JENKINS-21579 Very slow resource loading from UberClassLoader Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/ClassicPluginStrategy.java core/src/main/java/jenkins/util/AntClassLoader.java http://jenkins-ci.org/commit/jenkins/705f5eb8e737d1e0770f509edb5edb3d50f60cdc Log: JENKINS-21579 Copied as-is from Ant 1.8.3 to apply patches (cherry picked from commit 69773dc9f785b12f033ba268fb4e4107fc3e7f46) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22310) CLI slow performance investigation
Marco Miller commented on JENKINS-22310 CLI slow performance investigation ed1f1435a016da86ad0321e9acf3389a3c68add3 and 5daaf168a81902d852082f3f03b47e6b78f56981 are the 2 commits by KK fixing this issue. -Which commits I back-ported to 1.554.1 (current 'stable’ branch). I did so after this successful testing of ours: jenkinsci /jenkins unit tests, for regression (passing ones kept passing); jenkinsci /acceptance-test-harness, incl. both parent- and plugin-1st class-loading plugins (failures looked unrelated); Ericsson-internal CLI ‘stress' tests, which used to reproduce JENKINS-22310; incl. parent/plugin-1st plugins, too; brief manual testing through quick clicking-around, exercising some parent+plugin-1st (plugins) class-loading. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [image-gallery] (JENKINS-22625) Allow customization of gallery title with Build/Project Parameters
Ioannis Moutsatsos created JENKINS-22625 Allow customization of gallery title with Build/Project Parameters Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: image-gallery Created: 15/Apr/14 2:12 PM Description: The image gallery plugin is an indispensable addition to anyone using Jenkins-CI as a tool for scientific data analysis and integration. Used in combination with the R-plugin it provides a robust and powerful platform for analyzing data with R and visualizing the generated output. One of the improvements I can see is a way to customize the Image Gallery title using build parameters. This way we will have a more 'dynamic' title that actually reflects the contents of the specific image gallery For example the title would be defined like '$SAMPLE Comparative Boxplots' where SAMPLE is a build parameter. Project: Jenkins Priority: Minor Reporter: Ioannis Moutsatsos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22310) CLI slow performance investigation
Daniel Beck commented on JENKINS-22310 CLI slow performance investigation Marco Miller: Those commit IDs do not exist in https://github.com/jenkinsci/jenkins, are they correct? Could you provide the URLs? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-flow] (JENKINS-22626) Build triggers - Gitlab Merge Requests Builder
Steven Heirman created JENKINS-22626 Build triggers - Gitlab Merge Requests Builder Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Attachments: jenkins.stack Components: build-flow Created: 15/Apr/14 2:23 PM Description: crontab line H/5 * * * * gives an error WARNING: Error while serving http://'blah'/jenkins/job/Gitlab'blah'/descriptorByName/org.jenkinsci.plugins.gitlab.GitlabBuildTrigger/checkCron java.lang.reflect.InvocationTargetException Worked in version 1.552 Environment: Linux - 3.11.0-19-generic #33~precise1-Ubuntu SMP Wed Mar 12 21:16:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Jenkins 1.559 Project: Jenkins Labels: exception Priority: Major Reporter: Steven Heirman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22310) CLI slow performance investigation
Marco Miller commented on JENKINS-22310 CLI slow performance investigation Corrected now (edited above); thx! = https://github.com/jenkinsci/jenkins/commits/stable https://github.com/jenkinsci/jenkins/commit/fd9f273f3645fc670e1283bbed7967f789475c86 https://github.com/jenkinsci/jenkins/commit/705f5eb8e737d1e0770f509edb5edb3d50f60cdc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-flow] (JENKINS-22627) Dependency graph does not render conditional buildstep nodes
Ioannis Moutsatsos created JENKINS-22627 Dependency graph does not render conditional buildstep nodes Issue Type: Improvement Affects Versions: current Assignee: Nicolas De Loof Components: build-flow Created: 15/Apr/14 2:47 PM Description: The build-graph-flow dependency graph does not traverse through Conditional BuildStep nodes: https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin As a result the dependency graph can not be displayed. Project: Jenkins Priority: Major Reporter: Ioannis Moutsatsos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22310) CLI slow performance investigation
Oleg Nenashev commented on JENKINS-22310 CLI slow performance investigation I also confirm that both commits can be easily backported to 1.509.x and 1.532.x. We use fixes for about 1 week on 1.509.4... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-multijob-plugin] (JENKINS-19025) MultiJob marked as aborted when one phase failed
Sampo Niskanen commented on JENKINS-19025 MultiJob marked as aborted when one phase failed It seems that the problem disappeared when I upgraded from Jenkins 1.532.2 to 1.532.3. Will report if the problem reappears. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-oauth] (JENKINS-22035) Add Repository based authorization
Leandro Lucarella commented on JENKINS-22035 Add Repository based authorization Seems like the PR was merged already, any ETA for a release? 8-) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-22628) Change comments/description to use String.format() instead.
Tristan Amini created JENKINS-22628 Change comments/description to use String.format() instead. Issue Type: Improvement Assignee: Tristan Amini Components: jira Created: 15/Apr/14 3:24 PM Project: Jenkins Priority: Trivial Reporter: Tristan Amini This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-22628) Change comments/description to use String.format() instead.
Tristan Amini started work on JENKINS-22628 Change comments/description to use String.format() instead. Change By: Tristan Amini (15/Apr/14 3:27 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-22628) Change comments/description to use String.format() instead.
Tristan Amini updated JENKINS-22628 Change comments/description to use String.format() instead. Change By: Tristan Amini (15/Apr/14 3:38 PM) Labels: jiraplugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-21026) LR Scenario runs but LR Analysis fails
Nicholas Godfrey commented on JENKINS-21026 LR Scenario runs but LR Analysis fails I had the same issue and found a work around, maybe the solution. In your scenario, under results, results settings, do not set the 'automatically create a results directory for each scenario execution'. Also, I reset the results name to the default 'res', which may or may not be required. This does make some sense as for CI, each run creates it's own workspace results folder anyway. Nick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-11600) Implement Entry.getDate and Entry.getRevision for email-ext support
Nik San commented on JENKINS-11600 Implement Entry.getDate and Entry.getRevision for email-ext support Any ideas on this or what version of Jenkins we should go back to? I'm a newcomer so unable to have ever seen it working (last two weeks) but am also seeing the null for revision. Cheers. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-22628) Change comments/description to use String.format() instead.
SCM/JIRA link daemon commented on JENKINS-22628 Change comments/description to use String.format() instead. Code changed in jenkins User: Tristan Amini Path: src/main/java/hudson/plugins/jira/JiraCreateIssueNotifier.java http://jenkins-ci.org/commit/jira-plugin/83cd21de05ac324ba20cead169b47a89fa1b8475 Log: JENKINS-22628 Switched comment and description strings to use String.format() This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-22628) Change comments/description to use String.format() instead.
SCM/JIRA link daemon commented on JENKINS-22628 Change comments/description to use String.format() instead. Code changed in jenkins User: artkoshelev Path: src/main/java/hudson/plugins/jira/JiraCreateIssueNotifier.java http://jenkins-ci.org/commit/jira-plugin/035a36c28161cb1d6ca10e556f1cb7c710b9e92d Log: Merge pull request #41 from Tamini/develop JENKINS-22628 Switched comment and description strings to use String.f... Compare: https://github.com/jenkinsci/jira-plugin/compare/eaa8760d5600...035a36c28161 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [thinBackup] (JENKINS-22630) Log when backup is finished/complete
Brian Krische created JENKINS-22630 Log when backup is finished/complete Issue Type: Improvement Assignee: Thomas Fürer Components: thinBackup Created: 15/Apr/14 4:24 PM Description: It would be nice if the thinBackup plugin would log a finished/complete message when it has finished running the backup. Project: Jenkins Priority: Minor Reporter: Brian Krische This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22631) OutOfOrderBuildMonitor fails to correct builds with duplicate number
Jesse Glick created JENKINS-22631 OutOfOrderBuildMonitor fails to correct builds with duplicate number Issue Type: Bug Assignee: Jesse Glick Components: core Created: 15/Apr/14 4:33 PM Description: A user reported a case where on occasion two distinct build records for a job shared the same build number. (The symlink pointed to the later one, and Jenkins loaded the later one, but this apparently caused problems for the Copy Artifact plugin.) The OOOBM did run, printing to the system log for example ... jenkins.diagnostics.ooom.Problem$Inspector scan WARNING: Multiple builds have the same number: /.../jobs/.../builds/2014-01-23_09-12-34:#18 vs /.../jobs/.../builds/2014-01-23_15-34-56:#18 yet the older build record (/.../jobs/.../builds/2014-01-23_09-12-34/ in the above example) remained on disk, and no warning was displayed in the OOOBM log. Project: Jenkins Labels: diagnostics Priority: Major Reporter: 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-22631) OutOfOrderBuildMonitor fails to correct builds with duplicate number
Jesse Glick started work on JENKINS-22631 OutOfOrderBuildMonitor fails to correct builds with duplicate number Change By: Jesse Glick (15/Apr/14 4:35 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sloccount] (JENKINS-22597) Error 404 when trying to access language details for C/C++ Header
Michal Turek commented on JENKINS-22597 Error 404 when trying to access language details for C/C++ Header Thanks for the report, I will look at it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sloccount] (JENKINS-22597) Error 404 when trying to access language details for C/C++ Header
Michal Turek started work on JENKINS-22597 Error 404 when trying to access language details for C/C++ Header Change By: Michal Turek (15/Apr/14 4:47 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sloccount] (JENKINS-22597) Error 404 when trying to access language details for C/C++ Header
Michal Turek assigned JENKINS-22597 to Michal Turek Error 404 when trying to access language details for C/C++ Header Change By: Michal Turek (15/Apr/14 4:47 PM) Assignee: npiguet MichalTurek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-12850) Pre-select SVN path matching default value for SVN list tags parameters
John David commented on JENKINS-12850 Pre-select SVN path matching default value for SVN list tags parameters This is exactly what I was looking for. We have a project with multiple svn repos that lets developers submit test builds. It would be really great if they already had a default value so the developer only had to change what was necessary. Much less error prone. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-22628) Change comments/description to use String.format() instead.
Tristan Amini resolved JENKINS-22628 as Fixed Change comments/description to use String.format() instead. Change By: Tristan Amini (15/Apr/14 5:24 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-11600) Implement Entry.getDate and Entry.getRevision for email-ext support
Rob Petti commented on JENKINS-11600 Implement Entry.getDate and Entry.getRevision for email-ext support Email-ext has changed something on their end. It seems they are now using Entry.getTimestamp and Entry.getCommitId instead of getDate and getRevision like they were previously... The perforce plugin will need these two new functions implemented. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-11600) Implement Entry functions for email-ext support
Rob Petti updated JENKINS-11600 Implement Entry functions for email-ext support Updated ticket with details. Change By: Rob Petti (15/Apr/14 5:28 PM) Summary: ImplementEntry .getDateandEntry.getRevision functions foremail-extsupport Description: email-extlooksfor - getDate -getTimestamp and - getRevision -getCommitId methodsusingreflectionwhenretrievingchangeloginformation.Currentlytheperforceplugindoesnotimplementthesemethods,sothedateandchangenumberarenotavailable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21459) Jenkins don't run jobs from queue (there are available executors)
Thomas Fields commented on JENKINS-21459 Jenkins dont run jobs from queue (there are available executors) I'm also getting this on Jenkins 1.539. I removed the builds as suggested by Serj and some jobs built but now they are stuck again. Does anyone have any ideas? Cheers, Tom This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22632) Promote build plugin fails to promote the job when trying to promote with build parameters
Raghav Vaidhyanathan created JENKINS-22632 Promote build plugin fails to promote the job when trying to promote with build parameters Issue Type: Bug Assignee: Unassigned Components: promoted-builds, promoted-builds-simple Created: 15/Apr/14 5:33 PM Description: When trying to configure the promotion process based on a build parameter, the promotion fails as it tries to get the last failed instance for a job that never failed. As a result the promotion also fails with null pointer exception. Caused by: java.lang.NullPointerException at hudson.plugins.promoted_builds.Status.getLastFailed(Status.java:252) 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:297) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:201) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) Project: Jenkins Priority: Minor Reporter: Raghav Vaidhyanathan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22631) OutOfOrderBuildMonitor fails to correct builds with duplicate number
SCM/JIRA link daemon resolved JENKINS-22631 as Fixed OutOfOrderBuildMonitor fails to correct builds with duplicate number Change By: SCM/JIRA link daemon (15/Apr/14 5:36 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-21304) NPE - Reverse Proxy Authentication
Chris Frohoff commented on JENKINS-21304 NPE - Reverse Proxy Authentication This seems to be caused by older, incompatible Reverse Proxy Plugin config.xml data being bound into newer classes. Disabling security (https://wiki.jenkins-ci.org/display/JENKINS/Disable+security) and reconfiguring the Reverse Proxy Plugin Authentication (under Manage Jenkins Configure Global Security) seems to fix the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22631) OutOfOrderBuildMonitor fails to correct builds with duplicate number
dogfood commented on JENKINS-22631 OutOfOrderBuildMonitor fails to correct builds with duplicate number Integrated in jenkins_main_trunk #3312 FIXED JENKINS-22631 Do not just warn about multiple builds with the same number; note this in the official problem list, and offer to fix it. (Revision deb90a493c5341274fec11e653b44d7ad8b33586) Result = UNSTABLE Jesse Glick : deb90a493c5341274fec11e653b44d7ad8b33586 Files : test/src/test/resources/jenkins/diagnostics/ooom/OutOfOrderBuildDetectorTest/buildNumberClash.zip test/src/test/groovy/jenkins/diagnostics/ooom/OutOfOrderBuildDetectorTest.groovy core/src/main/java/jenkins/diagnostics/ooom/Problem.java core/src/main/java/jenkins/diagnostics/ooom/BuildPtr.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22634) Installing gerrit plugin somehow affects ability to display details of git changes
Robert Luberda created JENKINS-22634 Installing gerrit plugin somehow affects ability to display details of git changes Issue Type: Bug Affects Versions: current Assignee: rsandell Components: gerrit-trigger Created: 15/Apr/14 6:47 PM Description: After installing gerrit-trigger plugin, the changes pages (http://SERVERNAME:8080/job/JOBNAME/NUMBER/changes) for existing jobs (that are configured to use git plugin without gerrit) do not show the commit message details of changes any longer. After disabling gerrit-trigger plugin, the details are shown. Environment: Jenkins 1.509.2 Gerrit Trigger plugin 2.11.1 Git plugin 2.2.0 Project: Jenkins Priority: Major Reporter: Robert Luberda This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22635) Committer names not shown in pipeline heading
Pia Fåk Sunnanbo created JENKINS-22635 Committer names not shown in pipeline heading Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: pipeline_without_patch.png, pipeline_with_patch.png Components: delivery-pipeline Created: 15/Apr/14 7:07 PM Description: When using a previous version of the Delivery Pipeline Plugin in our project (unfortunately I don't know which one, but probably a version prior to 0.6.8), a list of committers were included in the headline of each pipeline triggered by an SCM change in Git or Subversion. In later versions (including 0.7.4) only "triggered by SCM change" is shown in the headline, which is much less informative. Please see attached screenshot (pipeline_without_patch.png). I created a quick local quick fix for this problem, which makes the pipeline heading look like the second screenshot (pipeline_with_patch.png). That quick fix has now been submitted as a pull request: https://github.com/Diabol/delivery-pipeline-plugin/pull/62 Project: Jenkins Labels: plugin Priority: Minor Reporter: Pia Fåk Sunnanbo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20707) NullPointerException in MultiClassLoaderSerializer when Warnings plugin processes puppet-lint output
Kohsuke Kawaguchi updated JENKINS-20707 NullPointerException in MultiClassLoaderSerializer when Warnings plugin processes puppet-lint output Moving it to core and reassigning to myself as I work on this issue. Change By: Kohsuke Kawaguchi (15/Apr/14 7:18 PM) Component/s: warnings This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20707) NullPointerException in MultiClassLoaderSerializer when Warnings plugin processes puppet-lint output
Kohsuke Kawaguchi assigned JENKINS-20707 to Kohsuke Kawaguchi NullPointerException in MultiClassLoaderSerializer when Warnings plugin processes puppet-lint output Change By: Kohsuke Kawaguchi (15/Apr/14 7:18 PM) Assignee: UlliHafner KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20707) NullPointerException in MultiClassLoaderSerializer when Warnings plugin processes puppet-lint output
Kohsuke Kawaguchi reopened JENKINS-20707 NullPointerException in MultiClassLoaderSerializer when Warnings plugin processes puppet-lint output Reopening as I work on this issue. Reported independently by one of our customers. Change By: Kohsuke Kawaguchi (15/Apr/14 7:19 PM) Resolution: CannotReproduce Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14993) JDK auto-installer for OSX
Nikita Salnikov-Tarnovski commented on JENKINS-14993 JDK auto-installer for OSX Any feedback or ETA for 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-22636) Build History timeline graph only displays builds of current GMT day
D Soa created JENKINS-22636 Build History timeline graph only displays builds of current GMT day Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core, gui Created: 15/Apr/14 7:31 PM Description: I'm in Central time and all builds before midnight GMT are missing from the graph--only builds from the current "GMT day" are shown. Also, if the current timezone is not in daylight savings time, they are displayed one hour later than they happened. Environment: Jenkins 1.540 Project: Jenkins Labels: jenkins gui Priority: Major Reporter: D Soa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth] (JENKINS-22633) Exclude permissions for Matrix Authorization Strategy plugin
Jesse Glick updated JENKINS-22633 Exclude permissions for Matrix Authorization Strategy plugin I could have sworn this is a duplicate, but cannot now find the original issue. Other authorization strategies do support this. This is a key feature of Role-Based Access Control, a proprietary plugin produced by my employed (CloudBees). Role Strategy might also have a similar feature, I am not sure. Change By: Jesse Glick (15/Apr/14 7:32 PM) Assignee: JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-14993) JDK auto-installer for OSX
Ulli Hafner commented on JENKINS-14993 JDK auto-installer for OSX Feel free to provide a pull request, shouldn't be so hard to implement... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22631) OutOfOrderBuildMonitor fails to correct builds with duplicate number
SCM/JIRA link daemon commented on JENKINS-22631 OutOfOrderBuildMonitor fails to correct builds with duplicate number Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/diagnostics/ooom/Problem.java http://jenkins-ci.org/commit/jenkins/1bf993caf5be57bfe8c1c4a80bfd51c38d683d5b Log: JENKINS-22631 The wrong (newer) build was sometimes being marked for fixing, depending on arbitrary directory listing order. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sloccount] (JENKINS-22597) Error 404 when trying to access language details for C/C++ Header
SCM/JIRA link daemon commented on JENKINS-22597 Error 404 when trying to access language details for C/C++ Header Code changed in jenkins User: Michal Turek Path: src/main/java/hudson/plugins/sloccount/SloccountDiffLanguage.java src/main/java/hudson/plugins/sloccount/SloccountResult.java src/main/java/hudson/plugins/sloccount/model/Folder.java src/main/java/hudson/plugins/sloccount/model/Language.java src/main/java/hudson/plugins/sloccount/model/Module.java src/main/java/hudson/plugins/sloccount/util/HtmlUtil.java src/main/resources/hudson/plugins/sloccount/SloccountBuildAction/summary.jelly src/main/resources/hudson/plugins/sloccount/SloccountResult/languages.jelly src/main/resources/hudson/plugins/sloccount/SloccountResult/modules.jelly http://jenkins-ci.org/commit/sloccount-plugin/f98c8ca5116bc8252dbad571272269de850aae7e Log: Merge pull request #41 from mixalturek/master JENKINS-22597 Error 404 when trying to access language details for "C/... Compare: https://github.com/jenkinsci/sloccount-plugin/compare/a75e1a064e9b...f98c8ca5116b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sloccount] (JENKINS-22597) Error 404 when trying to access language details for C/C++ Header
Michal Turek resolved JENKINS-22597 as Fixed Error 404 when trying to access language details for C/C++ Header Fixed, will be released in version 1.19. Change By: Michal Turek (15/Apr/14 8:11 PM) Status: InProgress Resolved Fix Version/s: current 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] [sloccount] (JENKINS-22597) Error 404 when trying to access language details for C/C++ Header
Michal Turek closed JENKINS-22597 as Fixed Error 404 when trying to access language details for C/C++ Header Change By: Michal Turek (15/Apr/14 8:11 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-20608) Cannot use Env Var in Task Name
Glenn Poston commented on JENKINS-20608 Cannot use Env Var in Task Name I'd also like to see this implemented. Just to be clear I'd like to use a build parameter as the value for the task name. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22395) Run.delete (from LogRotator) failing with ...looks to have already been deleted
Jesse Glick started work on JENKINS-22395 Run.delete (from LogRotator) failing with ...looks to have already been deleted Change By: Jesse Glick (15/Apr/14 8:30 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22395) Run.delete (from LogRotator) failing with ...looks to have already been deleted
Jesse Glick updated JENKINS-22395 Run.delete (from LogRotator) failing with ...looks to have already been deleted Change By: Jesse Glick (15/Apr/14 8:30 PM) Labels: exception lazy-loading log-rotator This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22395) Run.delete (from LogRotator) failing with ...looks to have already been deleted
Jesse Glick commented on JENKINS-22395 Run.delete (from LogRotator) failing with ...looks to have already been deleted Enhanced logging suggests that when MavenModuleSetBuild.delete leads to this error, it is deleting a MavenModuleBuild with the same number (successfully), and then (via getModuleBuilds) one with a later number that had already been deleted during an earlier MavenModuleSetBuild.delete. In other words, AbstractBuild.getNextBuild is returning a build which was already (recently) deleted from its parent! That suggests that dropLinks failed to actually drop the link from the older build—perhaps because the referent of previousBuildR in the newer build was null, perhaps because the older build was collected and then recreated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22334) plugin thinks emulator always crashes using sdk 22.6.1
Sam Xiao commented on JENKINS-22334 plugin thinks emulator always crashes using sdk 22.6.1 This becomes a blocker for us, can someone quickly review this and merge it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [buckminster] (JENKINS-10803) Buckminster Plugin does not use proxy
Matthew Kruer commented on JENKINS-10803 Buckminster Plugin does not use proxy If this bug was fixed (https://issues.jenkins-ci.org/browse/JENKINS-12885) the solution would be simple, Create my own zip that contains /director/configuration/.settings/org.eclipse.core.net.prefs with the proxy viables set or run a shell script without requiring the plugins. FATAL: java.io.FileNotFoundException: No 'plugins' directory has been found in /home/jenkins/tools/hudson.plugins.buckminster.BuckminsterInstallation/Buckminster_4.2_Headless java.lang.RuntimeException: java.io.FileNotFoundException: No 'plugins' directory has been found in /home/jenkins/tools/hudson.plugins.buckminster.BuckminsterInstallation/Buckminster_4.2_Headless at hudson.plugins.buckminster.EclipseBuckminsterBuilder.perform(EclipseBuckminsterBuilder.java:265) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) 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:566) at hudson.model.Run.execute(Run.java:1665) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Caused by: java.io.FileNotFoundException: No 'plugins' directory has been found in /home/jenkins/tools/hudson.plugins.buckminster.BuckminsterInstallation/Buckminster_4.2_Headless at hudson.plugins.buckminster.command.CommandLineBuilder.findEquinoxLauncher(CommandLineBuilder.java:391) at hudson.plugins.buckminster.command.CommandLineBuilder.addStarterParameters(CommandLineBuilder.java:252) at hudson.plugins.buckminster.command.CommandLineBuilder.buildCommands(CommandLineBuilder.java:146) at hudson.plugins.buckminster.EclipseBuckminsterBuilder.perform(EclipseBuckminsterBuilder.java:259) ... 9 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16490) New versions of slave.jar not reliably pushed via JNLP
Jesse Glick commented on JENKINS-16490 New versions of slave.jar not reliably pushed via JNLP There should also be a NodeMonitor for slaves running an old version of slave.jar. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-16490) New versions of slave.jar not reliably pushed via JNLP
Daniel Beck commented on JENKINS-16490 New versions of slave.jar not reliably pushed via JNLP Jesse: It's called VersionColumn Plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22631) OutOfOrderBuildMonitor fails to correct builds with duplicate number
dogfood commented on JENKINS-22631 OutOfOrderBuildMonitor fails to correct builds with duplicate number Integrated in jenkins_main_trunk #3314 JENKINS-22631 The wrong (newer) build was sometimes being marked for fixing, depending on arbitrary directory listing order. (Revision 1bf993caf5be57bfe8c1c4a80bfd51c38d683d5b) Result = SUCCESS Jesse Glick : 1bf993caf5be57bfe8c1c4a80bfd51c38d683d5b Files : core/src/main/java/jenkins/diagnostics/ooom/Problem.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] [delivery-pipeline] (JENKINS-20608) Cannot use Env Var in Task Name
Patrik Boström commented on JENKINS-20608 Cannot use Env Var in Task Name I can look in to it. I have one question: What should be the taskname value be if the build parameter is not set? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22635) Committer names not shown in pipeline heading
Patrik Boström assigned JENKINS-22635 to Patrik Boström Committer names not shown in pipeline heading Change By: Patrik Boström (15/Apr/14 9:20 PM) Assignee: PatrikBoströ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] [compress-artifacts] (JENKINS-22637) Cannot use Copy Artifacts Plugin in conjuction with the Compress Artifacts Plugin, archive not found.
Dominic St-Jacques created JENKINS-22637 Cannot use Copy Artifacts Plugin in conjuction with the Compress Artifacts Plugin, archive not found. Issue Type: Bug Affects Versions: current Assignee: Jesse Glick Components: compress-artifacts, copyartifact Created: 15/Apr/14 9:22 PM Description: When using the Compress Artifacts Plugin, the Copy Artifact Plugin cannot find the zip archive created and fails when trying to copy the previous job's artifacts. The error is: Unable to access upstream artifacts area C:\JenkinsData\job_name\builds\2014-04-15_17-02-29\archive. Does source project archive artifacts? The archive file is (no archive folder): C:\JenkinsData\job_name\builds\2014-04-15_17-02-29\archive.zip Environment: Windows 2012 Project: Jenkins Labels: plugin Priority: Minor Reporter: Dominic St-Jacques This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22635) Committer names not shown in pipeline heading
Patrik Boström commented on JENKINS-22635 Committer names not shown in pipeline heading Pull request is merged into master. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-22495) When rundeck job option values have hyphens in them, they don't get correctly parsed in RDECK_EXEC_ARG_
Greg Schueler commented on JENKINS-22495 When rundeck job option values have hyphens in them, they dont get correctly parsed in RDECK_EXEC_ARG_ released version 3.3 of the plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-22629) Prevent autofill of password entry fields
Daniel Beck commented on JENKINS-22629 Prevent autofill of password entry fields Please explain how this can be reproduced. In "Inject passwords to the build as environment variables", specifying a password foobar and saving, accessing the page afterwards results in 4l1OLblQ8negGA2Ldqe6HCiHhu+VGHtVSEQdPSSDna8= being entered in the password field (it's obviously much longer, and inspect element shows the value). Even when enabling password storage in my browser after saving the config page the first time (Firefox 28). Jenkins 1.532.2, env-inject 1.89. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22638) Rebuild plugin shows parameter descriptions as unsanitized HTML
Daniel Beck
created JENKINS-22638
Rebuild plugin shows parameter descriptions as unsanitized HTML
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
build.png, rebuild.png
Components:
plugin
Created:
15/Apr/14 10:29 PM
Description:
Use as description e.g. scriptalert('I 0wn j00');/script.
Gets sanitized by default (read: hidden) using 1.532.x default formatter, but on the rebuild page, it runs.
Using different markup formatters (e.g. Wikitext Security) makes no difference, it's always used verbatim.
Environment:
Rebuilder plugin 1.21
Project:
Jenkins
Priority:
Major
Reporter:
Daniel Beck
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-20707) NullPointerException in MultiClassLoaderSerializer when Warnings plugin processes puppet-lint output
Kohsuke Kawaguchi commented on JENKINS-20707 NullPointerException in MultiClassLoaderSerializer when Warnings plugin processes puppet-lint output The error indicates that the master is deserializing a response from a slave, and encountered an instance of a class that is originally defined from the master. The remoting library tried to find the classloader that defines this class, by looking up its own export table, but it didn't find it, because apparently it was already unexported. As can be seen by the stack trace, the deserialization of the response happens in the thread that made the request, and not in the channel reader thread. Thus it seems technically possible that the said classloader was unexported after the response (UserResponse) was received but before it was deserialized by the caller. This is my current hypothesis. But that implies ClassLoaders getting exported and unexported frequently, and I find that surprising. I'm going to see how classloaders get unexported to see if this hypothesis is likely. A relevant issue that Jesse points out here is that he observes a number of open tickets in JIRA where Channel.getExportedObject(int) returns null, and that we should be doing better error diagnostics. I need to find where those tickets are. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22395) Run.delete (from LogRotator) failing with ...looks to have already been deleted
Jesse Glick updated JENKINS-22395 Run.delete (from LogRotator) failing with ...looks to have already been deleted Change By: Jesse Glick (15/Apr/14 10:33 PM) URL: https://github.com/jenkinsci/jenkins/pull/1190 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20707) NullPointerException in MultiClassLoaderSerializer when Warnings plugin processes puppet-lint output
Kohsuke Kawaguchi commented on JENKINS-20707 NullPointerException in MultiClassLoaderSerializer when Warnings plugin processes puppet-lint output ClassLoader is always exported with autoUnexport=false (MultiClassLoaderSerializer.Output.annotateClass), so its unexporting is subject to the garbage collection on the other side. When RemoteClassLoader gets GC-ed, its proxy is RemoteIClassLoader and that in turn points to a generated proxy that wraps RemoteInvocationHandler. The finalizer of this object sends an unexport command back to the other side. Therefore indeed classloaders are getting exported and unexported pretty rapidly, which seems rather wasteful. It forces all the class loading to be redone, for one thing. There's a method to prevent exported objects from getting unexported (Channel.pin and Channel.pinClassLoader), but this is only used once in the Jenkins core to pin down the Jenkins core classloader (SlaveComputer.setChannel) and not plugins. Given that Jenkins doesn't unload plugins, I think we should just pin down all the plugin classloaders as well. So far, I think my hypothesis that I mentioned in the previous comment is indeed possible. I'm going to write a test case to reproduce this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20707) NullPointerException in MultiClassLoaderSerializer when Warnings plugin processes puppet-lint output
SCM/JIRA link daemon commented on JENKINS-20707 NullPointerException in MultiClassLoaderSerializer when Warnings plugin processes puppet-lint output Code changed in jenkins User: Kohsuke Kawaguchi Path: src/test/java/hudson/remoting/Bug20707Test.java src/test/java/hudson/remoting/ClassRemotingTest.java src/test/java/hudson/remoting/DummyClassLoader.java src/test/java/hudson/remoting/DummyClassLoaderTest.java src/test/java/hudson/remoting/TestEcho.java src/test/java/hudson/remoting/util/OneShotEvent.java http://jenkins-ci.org/commit/remoting/bd8e65cd874b863fc7d45e601da9a9267478d192 Log: JENKINS-20707 I tried to write a test case to verify the hypothesis along the line of https://issues.jenkins-ci.org/browse/JENKINS-20707?focusedCommentId=198755page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-198755, but ultimately it was a dead-end. The reason I was wrong is because ImportedClassLoaderTable maintain strong references to all the imported classloaders, and it prevents them from getting garbage collected. Probably for the reasons I was mentioning in JENKINS-20707, RemoteClassLoaders never get garbage collected, so they should never get unexported. I've spent much time trying to make the test case work, so I'm going to commit it on the side just in case someone finds useful in the future. Compare: https://github.com/jenkinsci/remoting/compare/663dae9c83be^...bd8e65cd874b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory] (JENKINS-22639) Configuration for CloudSlaves Ephemeral Nodes is persisted
recampbell created JENKINS-22639 Configuration for CloudSlaves Ephemeral Nodes is persisted Issue Type: Bug Assignee: Mirko Friedenhagen Components: jobconfighistory Created: 15/Apr/14 10:51 PM Description: The jobConfigHistory plugin tracks changes to AbstractCloudSlaves and EphemeralNodes. This can cause high load and high memory usage. These slaves should simply not be tracked. Project: Jenkins Priority: Major Reporter: recampbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22637) Cannot use Copy Artifacts Plugin in conjuction with the Compress Artifacts Plugin, archive not found.
Jesse Glick updated JENKINS-22637 Cannot use Copy Artifacts Plugin in conjuction with the Compress Artifacts Plugin, archive not found. Not a problem with Compress Artifacts per se. Rather, hudson.plugins.copyartifact.BuildSelector would need to be modified to work with ArtifactManager, present in Jenkins 1.532 and later, rather than calling Run.getArtifactsDir (which is now deprecated). In turn, the BuildSelector and Copier APIs would need to change to work with VirtualFile. Change By: Jesse Glick (15/Apr/14 10:53 PM) Issue Type: Bug NewFeature Assignee: JesseGlick Component/s: compress-artifacts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory] (JENKINS-22639) Configuration for CloudSlaves Ephemeral Nodes is persisted
recampbell updated JENKINS-22639 Configuration for CloudSlaves Ephemeral Nodes is persisted Change By: recampbell (15/Apr/14 11:02 PM) Labels: performance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory] (JENKINS-22639) Configuration for CloudSlaves Ephemeral Nodes is persisted
SCM/JIRA link daemon commented on JENKINS-22639 Configuration for CloudSlaves Ephemeral Nodes is persisted Code changed in jenkins User: Ryan Campbell Path: src/main/java/hudson/plugins/jobConfigHistory/ComputerHistoryListener.java http://jenkins-ci.org/commit/jobConfigHistory-plugin/e4103327c5143bbe3c0955cf29bcffd342b6251e Log: JENKINS-22639 Don't record changes to AbstractCloudSlaves or EphemeralNodes This can result in high load when there are nodes coming online and offline quickly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20662) When triggering a new build from current build page, 'Next Build' isn't shown after reloading page
Jesse Glick commented on JENKINS-20662 When triggering a new build from current build page, Next Build isnt shown after reloading page Not related to JENKINS-22052 since you see this with a freestyle project. Probably also not related to JENKINS-22395 since that involves build deletion. I think the bug is that when the new build is created, if you are not displaying it right away (which would be the case if you merely scheduled it), getPreviousBuild is not getting called on the new build, and thus nextBuildR is not getting updated on the first build. If true (and that would be pretty easy to test), the fix would simply be to call getPreviousBuild as soon as possible, such as from LazyBuildMixIn.newBuild. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22640) Notify commit can't find job by URI
Dmitry Moskowski created JENKINS-22640 Notify commit cant find job by URI Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 15/Apr/14 11:05 PM Description: I'm trying to trigger builds remotely on Jenkins v1.557, but ##JENKINS_HOST/git/notifyCommit?url="" always returns ## No git consumers for URI git+ssh://g...@git.host.ru/user/project.git ## Looks like something wrong in Jenkins internals Project: Jenkins Priority: Major Reporter: Dmitry Moskowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-16490) New versions of slave.jar not reliably pushed via JNLP
Jesse Glick commented on JENKINS-16490 New versions of slave.jar not reliably pushed via JNLP Ah, how about that! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22640) Notify commit can't find job by URI
Dmitry Moskowski updated JENKINS-22640 Notify commit cant find job by URI Change By: Dmitry Moskowski (15/Apr/14 11:09 PM) Description: ImtryingtotriggerbuildsremotelyonJenkinsv1.557,but ## bq. JENKINS_HOST/git/notifyCommit?url=""> ## alwaysreturns ## bq. NogitconsumersforURIgit+ssh://g...@git.host.ru/user/project.git ## LookslikesomethingwronginJenkinsinternals This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-21914) Intermittent Git(hub) polling errors on Windows
Mark Waite commented on JENKINS-21914 Intermittent Git(hub) polling errors on Windows It certainly seems possible that it might avoid the problem. Have you checked to see if that change avoids 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.
