[JIRA] [core] (JENKINS-27443) PATH environment variable incorrect on slaves
Cameron Horn created JENKINS-27443 PATH environment variable incorrect on slaves Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Mar/15 3:59 PM Description: Jenkins 1.599: Path E:\BoxTone\Database\BoxToneDB\bin;E:\BoxTone\sql-client;E:\BoxTone\utilities\CSVUpload;E:\BoxTone\dlls;E:\BoxTone\maintenancewindow\bin;E:\BoxTone\rails\ruby\bin;E:\BoxTone\Database\BoxToneDB\OHS\jlibs;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft\Exchange Server\bin;C:\Program Files\Microsoft\Exchange Server\Scripts Jenkins 1.602 Path C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft\Exchange Server\bin;C:\Program Files\Microsoft\Exchange Server\Scripts Project: Jenkins Priority: Minor Reporter: Cameron Horn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-27442) Failed to record SCM polling for hudson.model.FreeStyleProject
Cameron Horn created JENKINS-27442 Failed to record SCM polling for hudson.model.FreeStyleProject Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Mar/15 3:55 PM Description: SCM polling is failing for multiple projects, using multiple SCMs (git and svn). Jenkins 1.599 Log excerpt: Mar 15, 2015 4:36:28 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@5f0bc88b7.5-CORE_rails_ios-enrollment-api java.lang.NullPointerException Mar 15, 2015 4:36:28 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@3ee89b6d7.5_rails_ios-enrollment-api java.lang.NullPointerException Mar 15, 2015 4:36:28 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@271d900d7.5patch216_uss java.lang.NullPointerException Mar 15, 2015 4:36:28 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@347e4f517.5patch358_uss java.lang.NullPointerException Mar 15, 2015 4:36:28 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@55f55e9f8.0_active-directory java.lang.NullPointerException Mar 15, 2015 4:36:28 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@54da11b4heavyseas_active-directory java.lang.NullPointerException Mar 15, 2015 4:36:28 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@6a04009trunk_active-directory java.lang.NullPointerException Mar 15, 2015 4:36:28 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@5c6647cbtrunk_user-device-service java.lang.NullPointerException Project: Jenkins Priority: Major Reporter: Cameron Horn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-27443) PATH environment variable incorrect on slaves
Cameron Horn commented on JENKINS-27443 PATH environment variable incorrect on slaves Env-inject is installed, and was recently updated. It is not enabled on the slave jobs, and the path shows up incorrectly on the node | system information page. Jenkins master path: c:\app\oracle\product\11.2.0\dbhome_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Graphviz 2.28\bin;C:\Program Files\7-Zip;c:\cygwin\bin;C:\Program Files\Microsoft Windows Performance Toolkit\;C:\Program Files\TortoiseSVN\bin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-27443) PATH environment variable incorrect on slaves
Cameron Horn commented on JENKINS-27443 PATH environment variable incorrect on slaves 1.602 specific madness? Will upgrade Jenkins and disable env-inject when I can. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-27443) PATH environment variable incorrect on slaves
Cameron Horn commented on JENKINS-27443 PATH environment variable incorrect on slaves Will upgrade Jenkins and downgrade env-inject, I mean. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-27443) PATH environment variable incorrect on slaves
Cameron Horn commented on JENKINS-27443 PATH environment variable incorrect on slaves To clarify, Jenkins 1.602 and Env-inject 1.91 results in an incorrect slave PATH. Jenkins 1.599 and Env-inject 1.91 is what I'm running right now, and the slave PATH is correct. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26519) Build records not migrated due to “failed to rename
Cameron Horn commented on JENKINS-26519 Build records not migrated due to “failed to rename I am also still experiencing this issue with 1.598. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24380) Use build numbers as IDs
Cameron Horn commented on JENKINS-24380 Use build numbers as IDs Got a ton of messages like this: Jan 20, 2015 1:24:00 PM jenkins.model.RunIdMigrator doMigrate WARNING: failed to rename 2014-12-05_14-18-42 to 1 Ended up with every job timestamp set to 1970. Was able to downgrade. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-16201) Join plugin - join job does not run
Cameron Horn commented on JENKINS-16201 Join plugin - join job does not run Still happening in 1.554. Seems to cluster around jobs that are on tabs that aren't regularly viewed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [all-changes] (JENKINS-22031) all-changes oops
Cameron Horn commented on JENKINS-22031 all-changes oops This appears to happen when git is used as the source control. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [all-changes] (JENKINS-22031) all-changes oops
Cameron Horn created JENKINS-22031 all-changes oops Issue Type: Bug Assignee: wolfs Components: all-changes Created: 04/Mar/14 5:06 PM Description: Stack trace java.lang.RuntimeException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Users/sysbuild/AppData/Local/Temp/jetty-0.0.0.0-80-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.553.jar!/lib/layout/layout.jelly:233:26: d:invokeBody org.apache.commons.jelly.JellyTagException: jar:file:/C:/Users/sysbuild/AppData/Local/Temp/jetty-0.0.0.0-80-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.553.jar!/lib/layout/main-panel.jelly:36:21: d:invokeBody For input string: "1970-01-16T21:50:58-0500 -0500" at org.kohsuke.stapler.jelly.groovy.JellyBuilder.doInvokeMethod(JellyBuilder.java:280) at org.kohsuke.stapler.jelly.groovy.Namespace$ProxyImpl.invoke(Namespace.java:92) at $Proxy65.layout(Unknown Source) at lib.LayoutTagLib$layout.call(Unknown Source) at org.jenkinsci.plugins.all_changes.AllChangesAction.index.run(index.groovy:40) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:69) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:62) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:55) at org.kohsuke.stapler.jelly.groovy.GroovyFacet.handleIndexRequest(GroovyFacet.java:117) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [subversion] (JENKINS-20690) Subversion changes using Assembla
Cameron Horn resolved JENKINS-20690 as Not A Defect Subversion changes using Assembla Change By: Cameron Horn (17/Dec/13 3:26 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-20690) Subversion changes using Assembla
Cameron Horn commented on JENKINS-20690 Subversion changes using Assembla It seems that we did, although I don't know why. Removing that configuration from all projects fixed things. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-20690) Subversion changes using Assembla
Cameron Horn commented on JENKINS-20690 Subversion changes using Assembla The repository browser is set to "(Auto)". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-20690) Subversion changes using Assembla
Cameron Horn created JENKINS-20690 Subversion changes using Assembla Issue Type: Bug Assignee: Unassigned Components: subversion Created: 20/Nov/13 9:46 PM Description: Projects with local Subversion repositories show links to Assembla. Have no Assembla configured, no Assembla plugins installed, and no desire to use it. A typical changelog looks like this: #17 (Nov 20, 2013 4:24:35 PM) simplify patch-auto workflow — Horn, Cameron / Assembla INSTALL_SQL = false for install-all — Horn, Cameron / Assembla #14 (Nov 20, 2013 3:18:03 PM) new "make-patch-auto" target and project — Horn, Cameron / Assembla Updated the calls — Mazumdar, Anupam / Assembla The Assembla links are like this: https://www.assembla.com/code//subversion/changesets/136603/ Environment: Jenkins 1.539 Subversion 1.53 Project: Jenkins Priority: Major Reporter: Cameron Horn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-18220) Unable to find a build for artifact copy
Cameron Horn created JENKINS-18220 Unable to find a build for artifact copy Issue Type: Bug Assignee: Unassigned Components: copyartifact Created: 05/Jun/13 3:17 PM Description: Executing copy artifacts against a specific build number. In this case, the project is trunk_analyzers_merge-modules and the build number is 50. The build fails as follows: Copied 2 artifacts from "trunk_database-clone" build number 48 Unable to find a build for artifact copy from: trunk_analyzers_merge-modules This persists until the trunk_analyzers_merge-modules project page is viewed, at which point the next build will be successful: Copied 2 artifacts from "trunk_database-clone" build number 48 Copied 5 artifacts from "trunk_analyzers_merge-modules" build number 50 The same build will fail again the following day. This is happening with many jobss. No obvious errors in the Jenkins logs. Environment: Windows 2008 R2 Jenkins 1.516 CopyArtifact 1.27 Project: Jenkins Priority: Major Reporter: Cameron Horn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-17600) Unable to find build for artifact copy using specific build number and current slave.jar
Cameron Horn created JENKINS-17600 Unable to find build for artifact copy using specific build number and current slave.jar Issue Type: Bug Assignee: Unassigned Components: copyartifact Created: 12/Apr/13 8:51 PM Description: We are having a build that fails when passed this build selector parameter: SpecificBuildSelector plugin="copyartifact@1.26" buildNumber2/buildNumber/SpecificBuildSelector like so: Unable to find a build for artifact copy from: 7.2patch211_integrated-installer_patch Yet passes with a parameter like this: StatusBuildSelector plugin="copyartifact@1.26"/ like so: Copied 17 artifacts from "7.2patch211_integrated-installer_patch" build number 2 The failures only occur for us on slaves version 2.20. Slaves with version 2.20 have been verified to work, while we have seen version 2.22 and 2.23 fail. Environment: Jenkins 1.510, Windows Project: Jenkins Priority: Major Reporter: Cameron Horn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16201) Join plugin - join job does not run
Cameron Horn commented on JENKINS-16201 Join plugin - join job does not run I'm seeing this as well, suspect it relates to lazy project loading. Here's an example log (7.1patch142_platform_rails): Notifying upstream build 7.1patch142_platform #9 of job completion Project 7.1patch142_platform still waiting for 7.1patch142_platform_DataServices, 7.1patch142_platform_katrina, 7.1patch142_platform_flex-components, 7.1patch142_platform_authentication, 7.1patch142_platform_bAware, 7.1patch142_platform_cicada, 7.1patch142_platform_DPServer, 7.1patch142_platform_elibs, 7.1patch142_platform_ebins, 7.1patch142_platform_sdks, 7.1patch142_platform_HSQLDefrag, 7.1patch142_platform_service-wrapper, 7.1patch142_platform_bSecurity, 7.1patch142_platform_adforest builds to complete Notifying upstream projects of job completion Notifying upstream of completion: 7.1patch142_platform #9 Finished: SUCCESS Note that at the time of this project's completion, all of the jobs listed as being waited for have already completed, and have similar logs. Here's 7.1patch142_platform_elibs from above: Notifying upstream build 7.1patch142_platform #9 of job completion Project 7.1patch142_platform still waiting for 7.1patch142_platform_DataServices, 7.1patch142_platform_rails, 7.1patch142_platform_bAware, 7.1patch142_platform_cicada builds to complete Notifying upstream projects of job completion Notifying upstream of completion: 7.1patch142_platform #9 Finished: SUCCESS Clearly, in between these projects building, 7.1patch142_platform #9 forgot about projects that it already knew had been completed. The time between those projects completing is ~6 hours. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16201) Join plugin - join job does not run
Cameron Horn commented on JENKINS-16201 Join plugin - join job does not run It's just a guess that lazy loading is involved. The issue appeared to have started then, and I've noticed a lot of nonsense with builds disappearing with lazy loading (JENKINS-15156). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Cameron Horn commented on JENKINS-15156 Builds Disappear from Build History after Completion Notice this in particular with newly created jobs, where all build history will vanish after a build or two. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
