[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Benjamin Urban commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 +1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sloccount] (JENKINS-13382) Support multimodule sloccount report
Robert Paasche commented on JENKINS-13382 Support multimodule sloccount report That would be create, the table wouldn't grow so fast on large projects. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
Vincent Massol commented on JENKINS-20769 Failed to execute command Pipe.EOF I'm also seeing this in 1.549: Feb 4, 2014 9:10:08 AM com.cloudbees.jenkins.GitHubPushTrigger$1 run INFO: SCM changes detected in xwiki-platform. Triggering #4954 Feb 4, 2014 9:10:28 AM hudson.remoting.Channel$2 handle SEVERE: Failed to execute command Pipe.EOF(9) (channel agent-2-2) java.lang.NullPointerException at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)Feb 4, 2014 9:10:28 AM hudson.remoting.Channel$2 handle SEVERE: This command is created here Command Pipe.EOF(9) created atat hudson.remoting.Command.init(Command.java:67) at hudson.remoting.Command.init(Command.java:50) at hudson.remoting.ProxyWriter$EOF.init(ProxyWriter.java:169)at hudson.remoting.ProxyWriter.close(ProxyWriter.java:124) at hudson.remoting.ProxyWriter.finalize(ProxyWriter.java:132) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83) at java.lang.ref.Finalizer.access$100(Finalizer.java:14)at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:172) Feb 4, 2014 9:10:31 AM hudson.remoting.Channel$2 handle SEVERE: Failed to execute command Pipe.EOF(9) (channel agent-2-3) java.lang.NullPointerException at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Feb 4, 2014 9:10:31 AM hudson.remoting.Channel$2 handle SEVERE: This command is created here Command Pipe.EOF(9) created at at hudson.remoting.Command.init(Command.java:67) at hudson.remoting.Command.init(Command.java:50) at hudson.remoting.ProxyWriter$EOF.init(ProxyWriter.java:169) at hudson.remoting.ProxyWriter.close(ProxyWriter.java:124) at hudson.remoting.ProxyWriter.finalize(ProxyWriter.java:132) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83) at java.lang.ref.Finalizer.access$100(Finalizer.java:14) ... Is it a problem? What can I do? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [git] (JENKINS-20585) Git plugin 2.0 prevents project deletion on Windows, changelog.xml is busy
SCM/JIRA link daemon resolved JENKINS-20585 as Fixed Git plugin 2.0 prevents project deletion on Windows, changelog.xml is busy Change By: SCM/JIRA link daemon (04/Feb/14 8:45 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/groups/opt_out.
[JIRA] [git] (JENKINS-20585) Git plugin 2.0 prevents project deletion on Windows, changelog.xml is busy
SCM/JIRA link daemon commented on JENKINS-20585 Git plugin 2.0 prevents project deletion on Windows, changelog.xml is busy Code changed in jenkins User: Wannes Sels Path: src/main/java/hudson/plugins/git/GitChangeLogParser.java http://jenkins-ci.org/commit/git-plugin/fb611749d41272d672f3347421b3a354206dcfe7 Log: close changelog.xml after reading FIXED JENKINS-20585 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [disk-usage] (JENKINS-21259) Can't save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number.
Lucie Votypkova commented on JENKINS-21259 Cant save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number. Hi I checked it and I reproduce this behaviour only if I left the box "Warn if all jobs exceed some size" checked and I do not set any value for size. I do not think that it is bad behaviour - you should not have checked it without value. Please can you confirm if you have checked "Warn if all jobs exceed some size" without setting any size? 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/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-21637) Use credentials from SSH Credentials Plugin for connection to Gerrit
Tobias Oberlies created JENKINS-21637 Use credentials from SSH Credentials Plugin for connection to Gerrit Issue Type: New Feature Assignee: rsandell Components: gerrit-trigger Created: 04/Feb/14 9:11 AM Description: The SSH Credentials Plugin provides a convenient interface to manage SSH credentials. For example, it allows to enter the SSH private key directly on the configuration page. The Gerrit Trigger plugin should support re-using the SSH configuration from the SSH Credentials Plugin for the configuration of its connection to the Gerrit server. Project: Jenkins Priority: Major Reporter: Tobias Oberlies This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [configurationslicing] (JENKINS-16869) exception when trying to open Configuration Slicing Timestamper Slicer
ntmba lobo commented on JENKINS-16869 exception when trying to open Configuration Slicing Timestamper Slicer I have the same issue with the following configuration Jenkins ver. 1.546 onfigurationslicing 1.37 timestamper 1.5.8 java.runtime.version 1.7.0_25-b15 os.name Linux (Debian) Could you please try to reproduce, I would really like to have this working. I have 80+ jenkins to configure Thanks in advance Here is my stack trace when I click on the link http://JENKINS_URL/slicing/timestamper Stack trace javax.servlet.ServletException: java.lang.NoClassDefFoundError: hudson/plugins/timestamper/TimestamperBuildWrapper at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java: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:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at
[JIRA] [configurationslicing] (JENKINS-16869) exception when trying to open Configuration Slicing Timestamper Slicer
ntmba lobo reopened JENKINS-16869 exception when trying to open Configuration Slicing Timestamper Slicer I have another configuration mentionned in my comment where the problem occurs. Could you please try to reproduce it ? Change By: ntmba lobo (04/Feb/14 9:16 AM) Resolution: CannotReproduce Status: Closed 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/groups/opt_out.
[JIRA] [clearcase] (JENKINS-21626) Permanent build due to the use of an environment variable in config spec
SCM/JIRA link daemon commented on JENKINS-21626 Permanent build due to the use of an environment variable in config spec Code changed in jenkins User: Vincent Latombe Path: src/main/java/hudson/plugins/clearcase/ClearCaseSCM.java src/test/java/hudson/plugins/clearcase/ClearCaseSCMTest.java http://jenkins-ci.org/commit/clearcase-plugin/036f9a41ce7dfd9c377fba3ca0d27fe77dbb4627 Log: JENKINS-21626 Resolve parameters in config spec when checking if config spec has changed. Compare: https://github.com/jenkinsci/clearcase-plugin/compare/297b7096c430^...036f9a41ce7d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [clearcase] (JENKINS-21626) Permanent build due to the use of an environment variable in config spec
SCM/JIRA link daemon commented on JENKINS-21626 Permanent build due to the use of an environment variable in config spec Code changed in jenkins User: Vincent Latombe Path: src/main/java/hudson/plugins/clearcase/ClearCaseSCM.java src/test/java/hudson/plugins/clearcase/ClearCaseSCMTest.java http://jenkins-ci.org/commit/clearcase-plugin/c0a21e0b62746b907bdb17b8300978f8624c9f6c Log: JENKINS-21626 Resolve parameters in config spec when checking if config spec has changed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [integrity-plugin] (JENKINS-21638) PTC integrity plugin: version 1.22, download from MKS only folder without any file
Pawel Laprus created JENKINS-21638 PTC integrity plugin: version 1.22, download from MKS only folder without any file Issue Type: Bug Assignee: Cletus DSouza Attachments: jenkins.err.log Components: integrity-plugin Created: 04/Feb/14 9:43 AM Description: Hi I have problem about PTC Integrity Plugin, it created in workspace only directories (make it clear: directory structure is correct) without any files. When I make some changes in source and start build it's look like something was updated: "Successfully updated workspace with 12 updates and cleaned up 0 files!" but there is still no any file in workspace and it's size in bytes "0". In jenkins.err.log I see only: lut 04, 2014 8:53:17 AM org.apache.commons.httpclient.HttpMethodBase readResponseBody INFO: Response content is not chunk-encoded lut 04, 2014 8:53:17 AM org.apache.commons.httpclient.HttpMethodBase readResponseBody WARNING: Unsupported transfer encoding: Do You have any idea why it's not working? BR/Pawel Project: Jenkins Priority: Major Reporter: Pawel Laprus This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [core] (JENKINS-16018) Not all builds show in the build history dashboard on job
adoudev viaccess-orca commented on JENKINS-16018 Not all builds show in the build history dashboard on job This is not related... We still have 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/groups/opt_out.
[JIRA] [core] (JENKINS-10442) RestartNotSupportedException when trying to do safeRestart
dvaske commented on JENKINS-10442 RestartNotSupportedException when trying to do safeRestart I had this problem on Ubuntu 13.10, Jenkins ver. 1.537 and OpenJDK. Upgrading to oracle Java solved the issue as far as I can tell. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-multijob-plugin] (JENKINS-21615) MultiJob 1.11 phases broken when upgraded from 1.9
Nicolas Morey commented on JENKINS-21615 MultiJob 1.11 phases broken when upgraded from 1.9 I updated from 1.4 to 1.11 and had the same kind of issue. The job in the phase are matrix build. I tried a small test case and I get this backtrace: java.lang.ClassCastException: hudson.matrix.MatrixBuild cannot be cast to hudson.model.Build at com.tikal.jenkins.plugins.multijob.MultiJobBuilder$SubJobWorker.run(MultiJobBuilder.java:199) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [conditional-buildstep] (JENKINS-21491) Time restriction does not work if earliest = latest
Andy Bigos commented on JENKINS-21491 Time restriction does not work if earliest = latest Just hit the same issue. Would be great if the period could span midnight. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [clearcase] (JENKINS-21626) Permanent build due to the use of an environment variable in config spec
SCM/JIRA link daemon commented on JENKINS-21626 Permanent build due to the use of an environment variable in config spec Code changed in jenkins User: Vincent Latombe Path: src/main/java/hudson/plugins/clearcase/ClearCaseSCM.java src/test/java/hudson/plugins/clearcase/ClearCaseSCMTest.java http://jenkins-ci.org/commit/clearcase-plugin/6314cabe75411ebf0887a93341cae063ffb6a308 Log: JENKINS-21626 Resolve parameters in config spec when checking if config spec has changed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [rtc] (JENKINS-21477) Enable multiple Jazz servers per project
x29a commented on JENKINS-21477 Enable multiple Jazz servers per project Maybe one could try to solve this with something like https://wiki.jenkins-ci.org/display/JENKINS/Multiple+SCMs+Plugin - although i think an "onboard" solution from within the RTC plugin would be the cleanest This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [clearcase] (JENKINS-21626) Permanent build due to the use of an environment variable in config spec
Vincent Latombe commented on JENKINS-21626 Permanent build due to the use of an environment variable in config spec Hi, could you check with the following build ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xunit] (JENKINS-15908) Do not fail build when no test reports are found
x29a commented on JENKINS-15908 Do not fail build when no test reports are found I think this is covered with SkipNoTestFiles flag (e.g. here: https://issues.jenkins-ci.org/browse/JENKINS-18443) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [git-client] (JENKINS-20387) Timeout (10min) on git clone command
Mark Waite resolved JENKINS-20387 as Fixed Timeout (10min) on git clone command Pull request has been accepted. This fix should be available in the next release of the git-client-plugin after 1.6.1 Change By: Mark Waite (04/Feb/14 12:04 PM) 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/groups/opt_out.
[JIRA] [git] (JENKINS-20445) Git plugin timeout is too small
Mark Waite resolved JENKINS-20445 as Fixed Git plugin timeout is too small Pull request has been accepted. This fix should be available in the next release of the git-client-plugin after 1.6.1 Change By: Mark Waite (04/Feb/14 12:03 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20750) Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error
Mark Waite resolved JENKINS-20750 as Fixed Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error Pull request has been accepted. This fix should be available in the next release of the git-client-plugin after 1.6.1 Change By: Mark Waite (04/Feb/14 12:04 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20750) Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error
Mark Waite commented on JENKINS-20750 Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error Could you check the value of your HOMEDRIVE and HOMEPATH environment variables? I believe the original report (C/Documents and Settings/Tester/.ssh might indicate that HOMEDRIVE is set as "C" when it needs to be "C:". You might also check the value of your (optional) HOME environment variable, in case it is affecting things. If the HOME environment variable had been set for the Git plugin, it might have needed to be /C/Documents and Settings/Tester. Maybe you're missing the leading slash on the value in the HOME environment variable? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [disk-usage] (JENKINS-21259) Can't save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number.
Jesper Jensen commented on JENKINS-21259 Cant save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number. Problem is partly solved by disabling the plugin and then enabling it again. Then I added the values for all the warning and save that. When I go back in again the values are gone! I restarted Jenkins and the check marks are there but the values are gone. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [swarm] (JENKINS-20138) swarm 1.9 can't connect to current LTS as slave.jar too old
Mark Waite closed JENKINS-20138 as Fixed swarm 1.9 cant connect to current LTS as slave.jar too old I confirmed that swarm client 1.11 connects to LTS 1.532.1 and am closing this issue. Change By: Mark Waite (04/Feb/14 12:24 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/groups/opt_out.
[JIRA] [core] (JENKINS-20418) java.lang.VerifyError: Bad type on operand stack in Base64OutputStream when gitclient is being invoked
Mark Waite closed JENKINS-20418 as Fixed java.lang.VerifyError: Bad type on operand stack in Base64OutputStream when gitclient is being invoked Fix has been available as a released plugin for a few weeks. Change By: Mark Waite (04/Feb/14 12:25 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/groups/opt_out.
[JIRA] [accurev] (JENKINS-21496) Version .6.22 removes advanced options for AccuRev Servers in Global configuration
Anton Feoktistov commented on JENKINS-21496 Version .6.22 removes advanced options for AccuRev Servers in Global configuration I cannot find "Use workspace" and "Use update" functions. For my team it is critical, because stream size is big, but internet connection is too slow. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [core] (JENKINS-21639) Jobs named . can be created, but not built, configured, accessed, ...
Daniel Beck created JENKINS-21639 Jobs named . can be created, but not built, configured, accessed, ... Issue Type: Bug Assignee: Unassigned Components: core Created: 04/Feb/14 12:41 PM Description: Should probably qualify as a forbidden name, like '..' does. 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/groups/opt_out.
[JIRA] [campfire] (JENKINS-19590) Campfire Plugin failing SSL check after upgrading Jenkins to latest 1.530
Kevin van Zonneveld commented on JENKINS-19590 Campfire Plugin failing SSL check after upgrading Jenkins to latest 1.530 On Ubuntu, we installed a newer JRE: sudo aptitude install openjdk-7-jre sudo update-alternatives --set java /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java sudo service jenkins stop sudo service jenkins start Now the error is gone, but so far I still haven't seen campfire notifications This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [disk-usage] (JENKINS-21259) Can't save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number.
Lucie Votypkova commented on JENKINS-21259 Cant save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number. I checked the last version and snapshot. You are right this issue is in the last version of plugin. It is bug in UI (values is not displayed in configuration page). I have already fixed it in snapshot, but I added a few functions in the snapshot which I did not tested. I hope I will test it soon and new version will be at the end of this week. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-21259) Can't save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number.
Jesper Jensen commented on JENKINS-21259 Cant save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number. Thank you very much for the update, I'll wait for the next release for this fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [deploy] (JENKINS-18991) Unable to access debian package 1.525 using apt-get or browse http://pkg.jenkins-ci.org/debian fails
Mark Waite closed JENKINS-18991 as Fixed Unable to access debian package 1.525 using apt-get or browse http://pkg.jenkins-ci.org/debian fails Change By: Mark Waite (04/Feb/14 1:02 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/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-14879) Sun proprietary API and may be removed in a future release
Mark Waite closed JENKINS-14879 as Fixed Sun proprietary API and may be removed in a future release Change By: Mark Waite (04/Feb/14 1:02 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/groups/opt_out.
[JIRA] [core] (JENKINS-9679) NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option
Mark Waite closed JENKINS-9679 as Fixed NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option Change By: Mark Waite (04/Feb/14 1:07 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/groups/opt_out.
[JIRA] [core] (JENKINS-9521) sun.misc.BASE64Encoder is Sun proprietary API and may be removed in a future release
Mark Waite closed JENKINS-9521 as Fixed sun.misc.BASE64Encoder is Sun proprietary API and may be removed in a future release Change By: Mark Waite (04/Feb/14 1:06 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-21617) List Subversion Tags job parameter wants svn credentials but there is no way to fill it
Alexander Krysko commented on JENKINS-21617 List Subversion Tags job parameter wants svn credentials but there is no way to fill it I have noticed the same behavior This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin 2.0
Laurent TOURREAU created JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin 2.0 Issue Type: Bug Affects Versions: current Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 04/Feb/14 1:28 PM Description: We have upgrade to Subversion Plugin 2.0. Since this upgrade, the plugin doesn't work anymore. We get such message in the log: Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:47 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:52 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Environment: Jenkins 1.546 Project: Jenkins Priority: Blocker Reporter: Laurent TOURREAU This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [subversion] (JENKINS-21617) List Subversion Tags job parameter wants svn credentials but there is no way to fill it
Wilm Schomburg commented on JENKINS-21617 List Subversion Tags job parameter wants svn credentials but there is no way to fill it Same to me This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [websphere-deployer] (JENKINS-21641) unable to connect to remote host using websphere deployer plugin
Vamsi Hari created JENKINS-21641 unable to connect to remote host using websphere deployer plugin Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Error_log.txt Components: websphere-deployer Created: 04/Feb/14 1:30 PM Description: We are trying to deploy a java j2ee EAR to WebSphere application server(v8.0.0) hosted on a remote host -We had copied the required jars(com.ibm.ws.admin.client_8.0.0.jar, com.ibm.ws.orb_8.0.0.jar) from that remote host to our Build server where jenkins is hosted. -We had copied the DummyClientKeyFile.jks, DummyClientTrustFile.jks to Build server and given their path in the Job config. -When tried to Test Connection, we are getting the following error, Connection failed: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host 10.25.4.189 at port 8879. at com.ibm.websphere.management.AdminClientFactory.createAdminClientPrivileged(AdminClientFactory.java:634) at com.ibm.websphere.management.AdminClientFactory.access$000(AdminClientFactory.java:126) See the attachment for full error Due Date: 07/Feb/14 12:00 AM Environment: SUSE Linux Enterprise Server 11 (x86_64) Project: Jenkins Labels: jenkins websphere websphere-deployer-plugin SOAP Priority: Blocker Reporter: Vamsi Hari This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin 2.0
Frédéric Camblor commented on JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin 2.0 Arg ... as if it weren't already complicated enough Seems like maintaining compatibility will be a pain. Note that I linked this issue with JENKINS-18124 about scm modularization. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [core] (JENKINS-21567) After Upgrade to 1547 OutOfMemoryError
Kathlen Kuehmel commented on JENKINS-21567 After Upgrade to 1547 OutOfMemoryError We did more investigation. We used to start Jenkins with Tanuki Wrapper. To make sure, it's not a problem of the wrapper, today we startet jenkins direct: java -jar jenkins.war. With the options: -Xmx512m -Xms512m But starting some Jobs and clicking at the jenkins-sites in the browser caused again an outOfMemoryException. HeapDump was writen. It has 76 MB. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [websphere-deployer] (JENKINS-21641) The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin
Vamsi Hari
updated JENKINS-21641
The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin
Change By:
Vamsi Hari
(04/Feb/14 2:28 PM)
Description:
{color:green}*Wearetryingtodeployajavaj2eeEARtoWebSphereapplicationserver(v8.0.0)hostedonaremotehost*{color}*-Wehadcopiedtherequiredjars(com.ibm.ws.admin.client_8.0.0.jar,com.ibm.ws.orb_8.0.0.jar)fromthatremotehosttoourBuildserverwherejenkinsishosted.**-WehadcopiedtheDummyClientKeyFile.jks,DummyClientTrustFile.jkstoBuildserverandgiventheirpathintheJobconfig.*-WhentriedtoTestConnection,wearegettingthefollowingerror,Connectionfailed:com.ibm.websphere.management.exception.ConnectorException:ADMC0016E:ThesystemcannotcreateaSOAPconnectortoconnecttohost
10.25.4.189
remotehostIP
atport8879.atcom.ibm.websphere.management.AdminClientFactory.createAdminClientPrivileged(AdminClientFactory.java:634)atcom.ibm.websphere.management.AdminClientFactory.access$000(AdminClientFactory.java:126){color:red}Seetheattachmentforfullerror{color}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [websphere-deployer] (JENKINS-21641) The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin
Vamsi Hari updated JENKINS-21641 The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin Change By: Vamsi Hari (04/Feb/14 2:27 PM) Summary: unable ThesystemcannotcreateaSOAPconnector toconnecttoremotehostusingwebspheredeployerplugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobconfighistory] (JENKINS-21600) Enable paging to improve performance
SCM/JIRA link daemon commented on JENKINS-21600 Enable paging to improve performance Code changed in jenkins User: Stefan Brausch Path: src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistory.java src/main/resources/hudson/plugins/jobConfigHistory/JobConfigHistory/config.jelly src/main/webapp/help/help-maxEntriesPerSite.html src/test/java/hudson/plugins/jobConfigHistory/JobConfigHistoryTest.java http://jenkins-ci.org/commit/jobConfigHistory-plugin/d3625312101d5b17dccc04550dcb27cd8b709696 Log: JENKINS-21600: Config entry for max history entries per site Compare: https://github.com/jenkinsci/jobConfigHistory-plugin/compare/7826f7abbafb...d3625312101d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [core] (JENKINS-21642) JNLP slaves should refresh old slave.jar when possible
Jesse Glick created JENKINS-21642 JNLP slaves should refresh old slave.jar when possible Issue Type: New Feature Assignee: Unassigned Components: core Created: 04/Feb/14 2:28 PM Description: For an installation with hundreds of JNLP slaves it becomes difficult to ensure that the slave.jar agents get upgraded when there is a significant change to the remoting layer. It would be nice if slave.jar detected when it was out of date relative to the current version available on the master, and tried to swap in a new version. On Unix slaves (uncommon for JNLP) this could be done just be replacing the file; on Windows slaves it would be hard since the file cannot be rewritten in place. Either some JNA code like in WindowsServiceLifecycle could call MoveFileExA(..., ..., MOVEFILE_DELAY_UNTIL_REBOOT | MOVEFILE_REPLACE_EXISTING), or the service wrapper could be instructed to look for a JAR update. Failing this, there ought to at least be an administrative warning if one or more slaves are running an outdated agent. Project: Jenkins Labels: jnlp slave 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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-15977) java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild
SCM/JIRA link daemon commented on JENKINS-15977 java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/copyartifact/CopyArtifact.java http://jenkins-ci.org/commit/copyartifact-plugin/6cd2d83c58527c87cfbcc174fdbf6f5767c8dcbd Log: FIXED JENKINS-15977 ClassNotFound is maven plugin not installed Check for the maven plugin being installed before trying to see if the project src is a maven project. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
k rehman created JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) Issue Type: Bug Affects Versions: current Assignee: Greg Peters Components: websphere-deployer Created: 04/Feb/14 2:40 PM Description: Hi there Most helpful if anyone can help on this. The plugin SSL connection and location of deployment WAR works but it fails to deploy to a remote WAS instance. There is no entry in the log files on the server or any evidence of installables that have been copied over to the remote server. The only msg is a plugin error error message: Connecting to IBM WebSphere Application Server... The following artifacts will be deployed in this order... --- XJourney.war --- Generating EAR For New Artifact: XJourney Deploying New 'XJourney' to IBM WebSphere Application Server Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: Failed to install artifact: Failure uploading archive to server at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.installArtifact(WebSphereDeploymentService.java:167) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.deployArtifact(WebSphereDeployerPlugin.java:193) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.perform(WebSphereDeployerPlugin.java:171) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1007) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1628) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:506) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) Build step 'Deploy To IBM WebSphere Application Server' changed build result to FAILURE Finished: FAILURE Environment: client - Jenkins on Tomcat v7.0.0 with latest plugin remote server Windows 7 Websphere ND V7.0.0.21 Project: Jenkins Priority: Major Reporter: k rehman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-15977) java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild
SCM/JIRA link daemon commented on JENKINS-15977 java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/CopyArtifact.java http://jenkins-ci.org/commit/copyartifact-plugin/d00c85521648361512e84ea0439ca6b1a95b9a4c Log: Merge pull request #14 from cjo9900/JENKINS-15977 FIXED JENKINS-15977 ClassNotFound is maven plugin not installed Compare: https://github.com/jenkinsci/copyartifact-plugin/compare/7df40f147030...d00c85521648 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-15977) java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild
SCM/JIRA link daemon resolved JENKINS-15977 as Fixed java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild Change By: SCM/JIRA link daemon (04/Feb/14 2:38 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-21274) CopyArtifact plugin version 1.28 does not work if Maven plugin is disabled
ikedam updated JENKINS-21274 CopyArtifact plugin version 1.28 does not work if Maven plugin is disabled I found this has nothing to do with JENKINS-15977. Even after fixed JENKINS-15977, I reproduce this. It seems depend on the version of Java compiler used in packaging. Packaged with JDK 1.7, it is not reproduced. Packaged with JDK 1.6, it is reproduced. I attach the stacktrace when reproduced. I tested with Jenkins 1.549. Change By: ikedam (04/Feb/14 2:54 PM) Attachment: stacktrace.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21023) WorkspaceCleanupThread does not handle folders
Jesse Glick assigned JENKINS-21023 to Jesse Glick WorkspaceCleanupThread does not handle folders Change By: Jesse Glick (04/Feb/14 3:05 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/groups/opt_out.
[JIRA] [core] (JENKINS-21023) WorkspaceCleanupThread does not handle folders
Jesse Glick started work on JENKINS-21023 WorkspaceCleanupThread does not handle folders Change By: Jesse Glick (04/Feb/14 3:05 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-21617) List Subversion Tags job parameter wants svn credentials but there is no way to fill it
Alexander Fischer commented on JENKINS-21617 List Subversion Tags job parameter wants svn credentials but there is no way to fill it Since version 2.0 I have the same 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/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
Greg Peters commented on JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) Reference: http://www-01.ibm.com/support/docview.wss?uid=swg21450962 Let me know if this works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21641) The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin
Greg Peters assigned JENKINS-21641 to Greg Peters The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin Change By: Greg Peters (04/Feb/14 3:02 PM) Assignee: GregPeters This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [websphere-deployer] (JENKINS-21641) The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin
Greg Peters resolved JENKINS-21641 as Not A Defect The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin PKIX path building failed: means you haven't imported your SSL cert from the administration console to your local jenkins server. See instructions for details. Change By: Greg Peters (04/Feb/14 3:09 PM) Status: Open Resolved Fix Version/s: current 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] [parameterized-trigger] (JENKINS-21586) Triggered project is not built with the same svn revision as the project which triggered it
ikedam commented on JENKINS-21586 Triggered project is not built with the same svn revision as the project which triggered it How about check out /trunk/product/release by calling svn command from shell script builder? The revision to check out can be determined from /trunk/product checked out by subversion 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/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-21598) Paging for jobconfighistory entries
Stefan Brausch resolved JENKINS-21598 as Duplicate Paging for jobconfighistory entries Duplicated by JENKINS-21600 Change By: Stefan Brausch (04/Feb/14 3:48 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [robot-plugin] (JENKINS-21644) Aggregated results in a multimodule maven project displays only values of the last submodule
Benjamin Zaiser
created JENKINS-21644
Aggregated results in a multimodule maven project displays only values of the last submodule
Issue Type:
Bug
Affects Versions:
current
Assignee:
jpiironen
Components:
robot-plugin
Created:
04/Feb/14 3:59 PM
Description:
Given is a multimodule maven project, with the following parent pom.xml:
project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"
modelVersion4.0.0/modelVersion
groupIdtest/groupId
artifactIdparent/artifactId
version1.0-SNAPSHOT/version
packagingpom/packaging
nameParent/name
modules
modulesubmodule1/module
modulesubmodule2/module
/modules
build
pluginManagement
plugins
plugin
groupIdorg.robotframework/groupId
artifactIdrobotframework-maven-plugin/artifactId
version${default.robotframework-maven-plugin.version}/version
executions
execution
goals
goalrun/goal
/goals
/execution
/executions
configuration
variables
variableLANG:EN/variable
/variables
logLevelDEBUG/logLevel
/configuration
/plugin
/plugins
/pluginManagement
/build
And the pom of a submodule:
project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"
modelVersion4.0.0/modelVersion
parent
groupIdtest/groupId
artifactIdparent/artifactId
version1.0-SNAPSHOT/version
relativePath../pom.xml/relativePath
/parent
name${project.artifactId}/name
artifactIdsubmodule1/artifactId
properties
main.basedir${project.parent.basedir}/main.basedir
appVersion${project.version}/appVersion
/properties
build
plugins
plugin
groupIdorg.robotframework/groupId
artifactIdrobotframework-maven-plugin/artifactId
configuration
testCasesDirectorysrc/test/robotframework/Suites/testCasesDirectory
/configuration
/plugin
/plugins
/build
Given is a Jenkins Job which calls mvn install
The job has the "Robotframework Jenkins Plugin" as Post-Build-Step with the following configuration:
Directory of Robot output
Output xml name
**/output.xml
Report html name
**/report.html
Log html name
**/log.html
Other files to copy
*/selenium-screenshot-.png
Thresholds for build result
yellow: 0.0, blue 0.0
Bug:
Actual
after the job has finished execution, the latest robot results displays only the results of the last module
Expected
after the job has finished execution, the latest robot results displays all testsuites / testcases of all modules
Suggested bugfix:
https://github.com/jenkinsci/robot-plugin/blob/master/src/main/java/hudson/plugins/robot/RobotParser.java line 89:
result = parseResult(reader, baseDirectory);
should be replaced by:
for (RobotSuiteResult suite : parseResult(reader, baseDirectory))
{
result.addSuite(suite);
}
Thanks
Ben
Environment:
Jenkins ver. 1.529
robot-plugin ver. 1.4.0
Project:
Jenkins
Priority:
Major
Reporter:
Benjamin Zaiser
[JIRA] [dashboard-view] (JENKINS-21581) NPE from sidepanel.jelly on changing to a different display page after upgrade to 1.549
jerome prudent commented on JENKINS-21581 NPE from sidepanel.jelly on changing to a different display page after upgrade to 1.549 Same issue here This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [dashboard-view] (JENKINS-21581) NPE from sidepanel.jelly on changing to a different display page after upgrade to 1.549
jerome prudent edited a comment on JENKINS-21581 NPE from sidepanel.jelly on changing to a different display page after upgrade to 1.549 Same issue here. We've got a dozen of view. Only one has this symptom. This view can't be removed nor edited. It's only showing the "evil burning jenkins" with the stacktrace above. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [git] (JENKINS-21401) NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013
Fredrik Hultin
commented on JENKINS-21401
NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013
The problem is that the Team Foundation server uses Microsoft's NTLM authentication rather than Basic HTTP Authentication or digest. The UsernamePasswordCredentials object that the git-client plugin produces for the HTTP request is incompatible with NTLM, which is why an exception is thrown.
To fix this issue an NTCredentials object should be generated instead.
I've hacked together a quick fix that temporarily solves the problem, at least for me. It basically checks if the URI path starts with "/tfs". If it does, it replaces the defaultcreds variable with the corresponding NTCredentials object.
A proper fix would obviously rather query the HTTP server and ask what type of authentication it uses, and use that information to generate the proper credentials object.
In the meantime, this fix might help some people so I'm including it.
DISCLAIMER: I've only tested this with .netrc credentials, in Linux, against a Team Foundation Server 2013. For me, it worked even though I left the domain blank, but perhaps it's needed in other cases. (It's the last parameter for the NTCredentials constructor if someone needs to add it).
a/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
+++ b/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
@@ -29,6 +29,7 @@ import org.apache.commons.httpclient.UsernamePasswordCredentials;
import org.apache.commons.httpclient.auth.AuthScope;
import org.apache.commons.httpclient.contrib.ssl.EasySSLProtocolSocketFactory;
import org.apache.commons.httpclient.methods.GetMethod;
+import org.apache.commons.httpclient.NTCredentials;
import org.apache.commons.httpclient.protocol.Protocol;
import org.apache.commons.io.FileUtils;
import org.apache.commons.lang.StringUtils;
@@ -1576,6 +1577,15 @@ public class CliGitAPIImpl extends LegacyCompatibleGitAPIImpl {
defaultcreds = Netrc.getInstance().getCredentials(u.getHost());
}
if (defaultcreds != null) {
+// Use NT credentials with team foundation addresses
+if(u.getPath().startsWith("/tfs")) {
+listener.getLogger().println("using NT credentials with repository: " + url);
+
+org.apache.commons.httpclient.UsernamePasswordCredentials up =
+(org.apache.commons.httpclient.UsernamePasswordCredentials) defaultcreds;
+
+defaultcreds = new NTCredentials(up.getUserName(), up.getPassword(), u.getHost(), "");
+}
client.getParams().setAuthenticationPreemptive(true);
client.getState().setCredentials(AuthScope.ANY, defaultcreds);
}
The actual source code being patched is from the master branch of the git-client-plugin:
https://github.com/jenkinsci/git-client-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/groups/opt_out.
[JIRA] [clearcase] (JENKINS-21626) Permanent build due to the use of an environment variable in config spec
Vincent Nouguier
commented on JENKINS-21626
Permanent build due to the use of an environment variable in config spec
Hi,
Its works fine using "Config spec " text area ...
But it fails using "Get config spec from a file"
Polling Log
View as plain text
This page captures the polling log that triggered this build.
Started on Feb 4, 2014 4:38:33 PM
Polling SCM changes on master
Checking if build is running
Checking if a build has already happened
Checking if revision state is known
Checking if we have a build with a valid workspace
get view CSPEC ***
workspace $ /usr/atria/bin/cleartool catcs -tag catalogservices_deploy-xsat-packages-and-models_jenkins
element /vobng/catalog_services/ /main/LATEST
element /vobng/catalog_services/xsat/... /main/LATEST
element /vobng/catalog_services/xsatunits/.../main/LATEST
element /vobng/smstk/main/LATEST -nocheckout
element /vobng/smstk/maven/... XSAT_V04_14 -nocheckout
**
INFO CSPEC changed = true
CATCS CSPEC ***
element /vobng/catalog_services/ /main/LATEST
element /vobng/catalog_services/xsat/... /main/LATEST
element /vobng/catalog_services/xsatunits/.../main/LATEST
element /vobng/smstk/main/LATEST -nocheckout
element /vobng/smstk/maven/... XSAT_V04_14 -nocheckout
**
FILE CSPEC ***
element /vobng/catalog_services/ /main/LATEST
element /vobng/catalog_services/xsat/... /main/LATEST
element /vobng/catalog_services/xsatunits/.../main/LATEST
element /vobng/smstk/main/LATEST -nocheckout
element /vobng/smstk/maven/... ${latestXsatLabel} -nocheckout
**
REASON: New config spec detected.
Done. Took 58 ms
Changes found
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [core] (JENKINS-21639) Jobs named . can be created, but not built, configured, accessed, ...
Daniel Beck updated JENKINS-21639 Jobs named . can be created, but not built, configured, accessed, ... Change By: Daniel Beck (04/Feb/14 5:00 PM) Labels: lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [support-core] (JENKINS-21029) Flush logs to disk only periodically
Jesse Glick assigned JENKINS-21029 to Jesse Glick Flush logs to disk only periodically Change By: Jesse Glick (04/Feb/14 5:25 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/groups/opt_out.
[JIRA] [support-core] (JENKINS-21029) Flush logs to disk only periodically
Jesse Glick started work on JENKINS-21029 Flush logs to disk only periodically Change By: Jesse Glick (04/Feb/14 5:25 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/groups/opt_out.
[JIRA] [core] (JENKINS-21023) WorkspaceCleanupThread does not handle folders
SCM/JIRA link daemon resolved JENKINS-21023 as Fixed WorkspaceCleanupThread does not handle folders Change By: SCM/JIRA link daemon (04/Feb/14 5:40 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/groups/opt_out.
[JIRA] [core] (JENKINS-21023) WorkspaceCleanupThread does not handle folders
SCM/JIRA link daemon commented on JENKINS-21023 WorkspaceCleanupThread does not handle folders Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/WorkspaceCleanupThread.java test/src/test/java/hudson/model/WorkspaceCleanupThreadTest.java http://jenkins-ci.org/commit/jenkins/cd526e99e63ae362f2d1ce1a04c3c68a38032a5c Log: FIXED JENKINS-21023 Rewrote WorkspaceCleanupThread to determine where workspaces for known items should be, rather than looking for directories that look like they might be workspaces. One key advantage is that this correctly handles the new default workspace location on the master. Another is that this allows folders to be correctly skipped, and jobs in folders to be correctly deleted. A subtler advantage would be handling of configured nondefault workspace locations, and compatibility with WorkspaceLocator. (Orphaned workspaces from deleted jobs are not removed, but these were not removed before either.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
kal commented on JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) Tried this but doesn't seem to work. I can see the new hostname in the WAS Admin console and I can ping it from the machine that's running Jenkins. Also the "Test Connection" button works fine from the plugin but actual run of the Jenkins job leads to same error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20804) showDependencies for ${CHANGES} doesn't seem to work
Dirk Hain
commented on JENKINS-20804
showDependencies for ${CHANGES} doesnt seem to work
I am running into a similar issue with
Jenkins: 1.548
email-ext: 2.37.2
However, for me the email-ext plugin will return changes with dependencies IF the build ends with a FAILURE. If the build is unstable the changes will not be populated. Here are the settings I am using:
${CHANGES, showDependencies=true, format="[%a] %d, %r: %m\\n %p\\n"}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-multijob-plugin] (JENKINS-21646) ClassCastException with Maven Project
Dominik Bartholdi created JENKINS-21646 ClassCastException with Maven Project Issue Type: Bug Assignee: hagzag Components: jenkins-multijob-plugin Created: 04/Feb/14 5:59 PM Description: If a phase contains a maven project job, the multijob plugin fails with a CalssCastException. java.lang.ClassCastException: hudson.maven.MavenModuleSetBuild cannot be cast to hudson.model.Build at com.tikal.jenkins.plugins.multijob.MultiJobBuilder$SubJobWorker.run(MultiJobBuilder.java:199) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Feb 04, 2014 6:26:59 PM hudson.model.Run execute Project: Jenkins Priority: Blocker Reporter: Dominik Bartholdi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-multijob-plugin] (JENKINS-21646) ClassCastException with Maven Project
Dominik Bartholdi commented on JENKINS-21646 ClassCastException with Maven Project PullRequest placed: https://github.com/jenkinsci/tikal-multijob-plugin/pull/43 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [email-ext] (JENKINS-20804) showDependencies for ${CHANGES} doesn't seem to work
Alex Earl
commented on JENKINS-20804
showDependencies for ${CHANGES} doesnt seem to work
showDependencies uses the following code:
for (EntryAbstractProject, DependencyChange e : build.getDependencyChanges(previousBuild).entrySet()) {
buf.append("\n===\n");
buf.append("\nChanges in ").append(e.getKey().getName()).append(":\n");
for (AbstractBuild?, ? b : e.getValue().getBuilds()) {
for (ChangeLogSet.Entry entry : b.getChangeSet()) {
Util.printf(buf, format, new ChangesSincePrintfSpec(entry, pathFormat, dateFormatter));
}
}
}
AbstractBuild.getDependencyChanges returns an EMPTY Map if there is no Fingerprinter.FingerprintAction for the project. The showDependencies is all based on core Jenkins classes, so you'd need to determine if your projects are meeting the requirements for the dependency graph being populated.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [clearcase] (JENKINS-21626) Permanent build due to the use of an environment variable in config spec
Vincent Latombe commented on JENKINS-21626 Permanent build due to the use of an environment variable in config spec fine, I'll fix that as well tomorrow. Thanks for your feedback! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [core] (JENKINS-20730) Wrong log message for out-of-order build record repair
SCM/JIRA link daemon resolved JENKINS-20730 as Fixed Wrong log message for out-of-order build record repair Change By: SCM/JIRA link daemon (04/Feb/14 6:22 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20730) Wrong log message for out-of-order build record repair
SCM/JIRA link daemon commented on JENKINS-20730 Wrong log message for out-of-order build record repair Code changed in jenkins User: Daniel Beck Path: core/src/main/java/jenkins/diagnostics/ooom/BuildPtr.java http://jenkins-ci.org/commit/jenkins/5ba9bf4417a9de253d8af5471adfcc9baa4d1d3d Log: FIXED JENKINS-20730 Use correct folder in log message This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18935) Make Subversion plugin support Subversion 1.8
Peter Thorson commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 There is a merge request now 2 months old to upgrade org.jenkins-ci.svnkit to 1.8.0: https://github.com/jenkinsci/svnkit/pull/2. But given the Hudson upgrade to 1.8.x just required a change to their pom, I'm hoping we won't need a Jenkins specific SVNKit anymore. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [core] (JENKINS-20730) Wrong log message for out-of-order build record repair
SCM/JIRA link daemon commented on JENKINS-20730 Wrong log message for out-of-order build record repair Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/jenkins/diagnostics/ooom/BuildPtr.java http://jenkins-ci.org/commit/jenkins/4effdb0da5e89f96b791a66b68685658ea5d805a Log: Merge pull request #1118 from daniel-beck/fix-ooom-message FIXED JENKINS-20730 Use correct folder in log message Compare: https://github.com/jenkinsci/jenkins/compare/ef63ccac0a76...4effdb0da5e8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [www] (JENKINS-20911) Jenkins is getting killed every few time
Ryan Smith commented on JENKINS-20911 Jenkins is getting killed every few time I was seeing the same thing run on Ubuntu in Vagrant. I start it with: java -Xmx512m -jar jenkins.war I have given my Vagrant VM more memory and this seems to have fixed 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/groups/opt_out.
[JIRA] [support-core] (JENKINS-21029) Flush logs to disk only periodically
SCM/JIRA link daemon resolved JENKINS-21029 as Fixed Flush logs to disk only periodically Change By: SCM/JIRA link daemon (04/Feb/14 6:45 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/groups/opt_out.
[JIRA] [support-core] (JENKINS-21029) Flush logs to disk only periodically
SCM/JIRA link daemon commented on JENKINS-21029 Flush logs to disk only periodically Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/jenkins/support/impl/JenkinsLogs.java http://jenkins-ci.org/commit/support-core-plugin/a17c789af91718a3a47ca6c7713d06d80e12042a Log: FIXED JENKINS-21029 Periodic flushing of logs to disk. Compare: https://github.com/jenkinsci/support-core-plugin/compare/8046de222f87...a17c789af917 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [core] (JENKINS-15226) Log recorders do not work reliably
SCM/JIRA link daemon commented on JENKINS-15226 Log recorders do not work reliably Code changed in jenkins User: Jesse Glick Path: pom.xml http://jenkins-ci.org/commit/support-core-plugin/e7ab14b15fc7165fb84130ed8d67b0780328bc42 Log: Require 1.480.3 as a baseline so we pick up the JENKINS-15226 fix during testing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [support-core] (JENKINS-20863) Integer overflow in SupportLogHandler
Jesse Glick started work on JENKINS-20863 Integer overflow in SupportLogHandler Change By: Jesse Glick (04/Feb/14 6: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/groups/opt_out.
[JIRA] [support-core] (JENKINS-20863) Integer overflow in SupportLogHandler
Jesse Glick assigned JENKINS-20863 to Jesse Glick Integer overflow in SupportLogHandler Change By: Jesse Glick (04/Feb/14 6:47 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/groups/opt_out.
[JIRA] [support-core] (JENKINS-20863) Integer overflow in SupportLogHandler
SCM/JIRA link daemon resolved JENKINS-20863 as Fixed Integer overflow in SupportLogHandler Change By: SCM/JIRA link daemon (04/Feb/14 6:51 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/groups/opt_out.
[JIRA] [support-core] (JENKINS-20863) Integer overflow in SupportLogHandler
SCM/JIRA link daemon commented on JENKINS-20863 Integer overflow in SupportLogHandler Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/jenkins/support/SupportLogHandler.java http://jenkins-ci.org/commit/support-core-plugin/2648a3bbe9e45c2b71714c58086cbb20ddb9 Log: FIXED JENKINS-20863 Integer overflow. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [scp] (JENKINS-21138) scp plugin throws exception while uploading console log
SCM/JIRA link daemon commented on JENKINS-21138 scp plugin throws exception while uploading console log Code changed in jenkins User: Khai Do Path: pom.xml src/main/java/be/certipost/hudson/plugin/SCPRepositoryPublisher.java http://jenkins-ci.org/commit/scp-plugin/49399091a5aa7fdf5d3937cfa90ced22c1118a4e Log: fix uploading of build console logs to remote server Fixes issue JENKINS-21138 An exception occurs during console log upload causing only partial logs to be copied to the remote server. The problem is that the session object is not thread safe. To fix this problem we need to move the session object into the ConsoleRunnable thread. Now the console upload always runs in a completely detached thread. Notes: 1. Needed to update jenkins version to 1.430 because 1.403 would not build anymore. I think 1.430 should be conservative enought to be compatible with most of the existing jenkins installs. 2. Updated com.jcraft.jsch depenency to version 1.50 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [vsphere-cloud] (JENKINS-21647) In Vsphere Cloud I can not create a machine from a template
Trent Cameron created JENKINS-21647 In Vsphere Cloud I can not create a machine from a template Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: vsphere-cloud Created: 04/Feb/14 7:00 PM Description: When I go to create a machine from a template everything looks good I include the information and test the connection and save the job no errors. When I run the job I receive the following error Started by user anonymous Building in workspace /var/lib/jenkins/jobs/test2/workspace vSphere vSphere Performing vSphere build step: "Deploy VM from template" vSphere Attempting to use server configuration: "XXX.XXX.XX.XX" vSphere Cloning VM. Please wait ... vSphere java.lang.NullPointerException Build step 'vSphere Build Step' marked build as failure Finished: FAILURE I know that the credentials are right because I can start a machine on that cluster. It is possible that I am entering incorrect values for Cluster and Resource Pool. Do I need to have Resource Pools defined to use this feature? I have tried everything I can think of. Thanks Environment: CentOS 6.4 Plugin version 1.1.4 Jenkins ver. 1.549 VMware VCenter Server Version 5.1.0 Project: Jenkins Priority: Major Reporter: Trent Cameron This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [core] (JENKINS-21639) Jobs named . can be created, but not built, configured, accessed, ...
SCM/JIRA link daemon resolved JENKINS-21639 as Fixed Jobs named . can be created, but not built, configured, accessed, ... Change By: SCM/JIRA link daemon (04/Feb/14 7:28 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21639) Jobs named . can be created, but not built, configured, accessed, ...
SCM/JIRA link daemon commented on JENKINS-21639 Jobs named . can be created, but not built, configured, accessed, ... Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/931d2960e9eb6765c0b0c2db7b64c042339b1eb9 Log: JENKINS-21639 Noting merge of #1117. Compare: https://github.com/jenkinsci/jenkins/compare/8660255c4266...931d2960e9eb This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [core] (JENKINS-21639) Jobs named . can be created, but not built, configured, accessed, ...
SCM/JIRA link daemon commented on JENKINS-21639 Jobs named . can be created, but not built, configured, accessed, ... Code changed in jenkins User: Daniel Beck Path: core/src/main/java/jenkins/model/Jenkins.java http://jenkins-ci.org/commit/jenkins/780b38bc755028f4c4d72378896407a182bd5b30 Log: FIXED JENKINS-21639 Prevent creation of job named '.'. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [core] (JENKINS-21163) Git Plugin causes Jenkins to stop working
Mark Waite edited a comment on JENKINS-21163 Git Plugin causes Jenkins to stop working I've now seen the same problem. Some weeks ago, I installed the git-userContent plugin and had encountered some problem from the git-server plugin on which the git-userContent plugin depends. I removed the git-server plugin, restarted my Jenkins server, and the server returned to normal. Could you remove git-server and git-server.*pi from the Jenkins plugins directory to see if you yours is the same problem as mine? If it is, then there is probably some incompatibility between recent versions of the git-client-plugin and the git-server plugin. You don't need the git-server plugin to use Git as an SCM tool in Jenkins, so it is safe to remove it. You do need the git-server plugin if you're allowing users to submit changes to your Jenkins userContent directory through git. If removing git-server as a plugin resolves the issue, then we'll need to investigate the incompatibility between them and fix one or both of the plugins to resolve the incompatibility. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [core] (JENKINS-21163) Git Plugin causes Jenkins to stop working
Mark Waite commented on JENKINS-21163 Git Plugin causes Jenkins to stop working I've now seen the same problem. Some weeks ago, I installed the git-userContent plugin and had encountered some problem from the git-server plugin on which the git-userContent plugin depends. I removed the git-server plugin, restarted my Jenkins server, and the server returned to normal. Could you remove git-server and git-server.*pi from the Jenkins plugins directory to see if you yours is the same problem as mine? If it is, then there is probably some incompatibility between recent versions of the git-client-plugin and the git-server plugin. You don't need the git-server plugin to use Git as an SCM tool in Jenkins, so it is safe to remove it. You do need the git-server plugin if you're allowing users to submit changes to your Jenkins userContent directory through git. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21648) subversion no longer working on OSX build slave after update from 1.54 to 2.0
Timothee Besset created JENKINS-21648 subversion no longer working on OSX build slave after update from 1.54 to 2.0 Issue Type: Bug Assignee: Unassigned Components: subversion Created: 04/Feb/14 7:42 PM Description: The update from 1.54 to 2.0 completely broke subversion support on my OSX build slave. The windows builder is still working correctly. org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.svn.sasl.SVNSaslAuthenticator.createSaslClient(SVNSaslAuthenticator.java:306) at org.tmatesoft.svn.core.internal.io.svn.sasl.SVNSaslAuthenticator.authenticate(SVNSaslAuthenticator.java:92) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.authenticate(SVNConnection.java:194) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.authenticate(SVNRepositoryImpl.java:1275) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1253) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:168) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:706) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:14) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:9) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:777) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:99) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:161) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:169) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:133) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:161) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:1024) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1005) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:981) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2461) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:695) Project: Jenkins Priority: Blocker
[JIRA] [jobconfighistory] (JENKINS-18900) [JobConfigurationHistory] Wrong history being displayed
Stefan Brausch commented on JENKINS-18900 [JobConfigurationHistory] Wrong history being displayed Thanks Kathi, yes I know him This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21648) subversion no longer working on OSX build slave after update from 1.54 to 2.0
Timothee Besset commented on JENKINS-21648 subversion no longer working on OSX build slave after update from 1.54 to 2.0 Reverting to 1.54 doesn't fix the problem either. So the problem may be broader than just that plugin. Any suggestion on what to try? This setup worked fine for a month or two before 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21647) In Vsphere Cloud I can not create a machine from a template
Trent Cameron commented on JENKINS-21647 In Vsphere Cloud I can not create a machine from a template Fixed the problem by creating a pool. The issue is it will not work without a pool. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-multijob-plugin] (JENKINS-21649) High CPU Usage on master while slaves working (multijob)
greg smolyn created JENKINS-21649 High CPU Usage on master while slaves working (multijob) Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: jenkins.war-2014-02-04-2.snapshot, ProfilerStackTrace.jpg Components: jenkins-multijob-plugin Created: 04/Feb/14 8:25 PM Description: When a slave is running a build in a multijob plugin, the monitoring thread on the master eats up 100% of a CPU core. This scales linearly-- so when I have 4 parallel jobs running, jenkins master is using 400% cpu. Attaching screen cap of profiler output, as well as YourKit profiler snapshot. Environment: Ubuntu 12.04, Oracle Java 7 java version 1.7.0_51 Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode) Project: Jenkins Priority: Major Reporter: greg smolyn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobconfighistory] (JENKINS-21600) Enable paging to improve performance
SCM/JIRA link daemon commented on JENKINS-21600 Enable paging to improve performance Code changed in jenkins User: Mirko Friedenhagen Path: src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryProjectAction.java src/test/java/hudson/plugins/jobConfigHistory/JobConfigHistoryProjectActionTest.java http://jenkins-ci.org/commit/jobConfigHistory-plugin/106610c52925c07ccc4297e4f314e63acf233eea Log: JENKINS-21600: Restrict number of returned values to maxEntriesPerPage This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
