[JIRA] (JENKINS-50051) Vault Plugin - Unable to retrieve secret get 404 error
Title: Message Title Stuart Whelan assigned an issue to Unassigned Jenkins / JENKINS-50051 Vault Plugin - Unable to retrieve secret get 404 error Change By: Stuart Whelan Assignee: Stuart Whelan Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36938) Please support 'Discard old builds' for published docker images
Title: Message Title Stuart Whelan created an issue Jenkins / JENKINS-36938 Please support 'Discard old builds' for published docker images Issue Type: Improvement Assignee: Unassigned Components: docker-build-publish-plugin Created: 2016/Jul/26 3:38 AM Labels: discard docker Priority: Minor Reporter: Stuart Whelan We build and publish each build as part of a CI process, I would like this plugin to detect and remove builds as per the Discard Old Builds setting. Add Comment
[JIRA] [vault-scm-plugin] (JENKINS-17143) Plugin not saving vault executable path between server restarts
Title: Message Title Stuart Whelan assigned an issue to Unassigned Jenkins / JENKINS-17143 Plugin not saving vault executable path between server restarts Change By: Stuart Whelan Assignee: Stuart Whelan Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vault-scm-plugin] (JENKINS-17143) Plugin not saving vault executable path between server restarts
Title: Message Title Stuart Whelan resolved as Fixed Jenkins / JENKINS-17143 Plugin not saving vault executable path between server restarts Change By: Stuart Whelan Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vault-scm-plugin] (JENKINS-17143) Plugin not saving vault executable path between server restarts
Title: Message Title Stuart Whelan closed an issue as Fixed Jenkins / JENKINS-17143 Plugin not saving vault executable path between server restarts Change By: Stuart Whelan Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vault-scm-plugin] (JENKINS-22953) Show paths/files in Changes reports
Title: Message Title Stuart Whelan assigned an issue to Unassigned Jenkins / JENKINS-22953 Show paths/files in Changes reports Change By: Stuart Whelan Assignee: Stuart Whelan Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vault-scm-plugin] (JENKINS-19784) Setting of Use Non Working Folder does not work
Title: Message Title Stuart Whelan assigned an issue to Unassigned Jenkins / JENKINS-19784 Setting of Use Non Working Folder does not work Change By: Stuart Whelan Assignee: Stuart Whelan Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vault-scm-plugin] (JENKINS-19783) Allow setting of working folder
Title: Message Title Stuart Whelan assigned an issue to Unassigned Jenkins / JENKINS-19783 Allow setting of working folder Change By: Stuart Whelan Assignee: Stuart Whelan Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vault-scm-plugin] (JENKINS-17143) Plugin not saving vault executable path between server restarts
Title: Message Title Stuart Whelan stopped work on JENKINS-17143 Change By: Stuart Whelan Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vault-scm-plugin] (JENKINS-22955) Make Version number shown in Changes reports a Link to that Versions info in Vault
Title: Message Title Stuart Whelan assigned an issue to Unassigned Jenkins / JENKINS-22955 Make Version number shown in Changes reports a Link to that Versions info in Vault Change By: Stuart Whelan Assignee: Stuart Whelan Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vault-scm-plugin] (JENKINS-26487) NPE during SCM polling
Title: Message Title Stuart Whelan assigned an issue to Unassigned Jenkins / JENKINS-26487 NPE during SCM polling Change By: Stuart Whelan Assignee: Stuart Whelan Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [powershell-plugin] (JENKINS-34581) Please add support for Pipelines to the Powershell plugin
Title: Message Title Stuart Whelan created an issue Jenkins / JENKINS-34581 Please add support for Pipelines to the Powershell plugin Issue Type: Improvement Assignee: Unassigned Components: powershell-plugin Created: 2016/May/03 10:04 PM Labels: pipeline powershell windows microsoft Priority: Major Reporter: Stuart Whelan I would like to use the powershell plugin from within pipelines, please add support for the pipelines to the powershell plugin. This is especially important as we approach Jenkins 2.0 and its move towards pipelines. Add Comment
[JIRA] [promoted-builds-plugin] (JENKINS-24970) Blank page when reapproving
Stuart Whelan commented on JENKINS-24970 Blank page when reapproving We are getting this exact problem, a blank html page when trying to re-promote. On 1.580 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25913) Please modify clean after checkout behaviour to optionally clean ignored, un-ignored and tracked files
Stuart Whelan commented on JENKINS-25913 Please modify clean after checkout behaviour to optionally clean ignored, un-ignored and tracked files Also the ability to do a git clean -dff, and clean away sub-repos. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-24421) Github webhook throwing "Form too large"
Stuart Whelan commented on JENKINS-24421 Github webhook throwing "Form too large" I worked around this by adding -Dorg.eclipse.jetty.server.Request.maxFormContentSize=500 to my jenkins arguments, just before the -jar parameter. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-24122) github service being removed when saving on the "configure jenkins" page
Stuart Whelan commented on JENKINS-24122 github service being removed when saving on the "configure jenkins" page I am getting the same issue with 1.576 running on Windows 2k8r2. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder] (JENKINS-23525) Crash when using Folders plugin: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.Job
Stuart Whelan created JENKINS-23525 Crash when using Folders plugin: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.Job Issue Type: Bug Assignee: Jesse Glick Components: cloudbees-folder, xfpanel Created: 21/Jun/14 5:48 AM Description: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/plugins/xfpanel/WEB-INF/lib/classes.jar!/maps/hudson/plugin/xfpanel/XFPanelView/configure-entries.jelly:43:73: method getPrioritySortedJobs threw exception: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.Job at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(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.CharacterEn
[JIRA] [parameters] (JENKINS-20760) On the job config screen, allow the the parameters section to be collapsed
Stuart Whelan updated JENKINS-20760 On the job config screen, allow the the parameters section to be collapsed Change By: Stuart Whelan (25/Nov/13 11:23 PM) Summary: On the job config scree screen , allow the the parameters section to be collapsed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [parameters] (JENKINS-20760) On the job config scree, allow the the parameters section to be collapsed
Stuart Whelan created JENKINS-20760 On the job config scree, allow the the parameters section to be collapsed Issue Type: Improvement Assignee: Unassigned Components: parameters Created: 25/Nov/13 9:59 PM Description: Our projects have 30ish parameters defined, it can be frustrating scroll down past them all. Please allow the Parameters section to be collapsed. Project: Jenkins Labels: parameter collapsing-section Priority: Minor Reporter: Stuart Whelan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [maven] (JENKINS-18922) Upgrading to 1.524 ("Upgrade Automatically") breaks jenkins
Stuart Whelan
commented on JENKINS-18922
Upgrading to 1.524 ("Upgrade Automatically") breaks jenkins
I had to also remove javadoc.jpi.disabled
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-15902) Add support for custom xcodebuild arguments
Stuart Whelan resolved JENKINS-15902 as Fixed Add support for custom xcodebuild arguments Checked in change to implement this. Change By: Stuart Whelan (11/Mar/13 8:02 PM) Status: In Progress Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15902) Add support for custom xcodebuild arguments
Stuart Whelan assigned JENKINS-15902 to Stuart Whelan Add support for custom xcodebuild arguments Change By: Stuart Whelan (10/Mar/13 9:28 PM) Assignee: Josh Kennedy Stuart Whelan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-15902) Add support for custom xcodebuild arguments
Stuart Whelan started work on JENKINS-15902 Add support for custom xcodebuild arguments Change By: Stuart Whelan (10/Mar/13 9:28 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17143) Plugin not saving vault executable path between server restarts
Stuart Whelan started work on JENKINS-17143 Plugin not saving vault executable path between server restarts Change By: Stuart Whelan (10/Mar/13 7:56 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17143) Plugin not saving vault executable path between server restarts
Stuart Whelan created JENKINS-17143 Plugin not saving vault executable path between server restarts Issue Type: Bug Affects Versions: current Assignee: Stuart Whelan Components: vault-scm Created: 10/Mar/13 7:29 PM Description: Reported Issue: Jenkins server(v1.504) is installed on a 32-bit Windows 8 machine using the Vault plugin (v1.1.1). In the global configuration settings I have configured a vault installation which points to my vault client executable at “C:\Program Files\SourceGear\Vault Client\vault.exe”. Everything works great, until I restart the Jenkins server. On restart the “Path to Vault executable” is reset to “C:\Program Files (x86)\SourceGear\Vault Client\vault.exe”. It appears that the setting is not being saved. I peeked into the org.jvnet.hudson.plugins.VaultSCM.xml file and I see an element for the setting but its empty. Looking into the code I’m assuming the problem is with line 54 of VaultSCMInstallation.java where the vaultLocation variable is declared transient, which is going to make it so it doesn’t get serialized. I’m not a regular Java programmer, so that assumption may be wrong. Environment: Windows 8 32Bit, Jenkins 1.504 Project: Jenkins Labels: vault-scm Priority: Minor Reporter: Stuart Whelan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17059) Subversion fails when checking out from repository
Stuart Whelan resolved JENKINS-17059 as Fixed Subversion fails when checking out from repository Problem was with an old svnkit-1.3.6.1-jenkins-2.jar in C:\Program Files (x86)\Jenkins\plugins\subversion\WEB-INF\lib Many thanks to kutzi for the help! Change By: Stuart Whelan (05/Mar/13 12:04 AM) Status: Open Resolved Assignee: Stuart Whelan 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] (JENKINS-17059) Subversion fails when checking out from repository
Stuart Whelan commented on JENKINS-17059 Subversion fails when checking out from repository Found svnkit-1.7.6-jenkins-1.jar and svnkit-1.3.6.1-jenkins-2.jar in C:\Program Files (x86)\Jenkins\plugins\subversion\WEB-INF\lib This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17059) Subversion fails when checking out from repository
Stuart Whelan commented on JENKINS-17059 Subversion fails when checking out from repository I have 1.45 of subversion-plugin installed (also tried with 1.44) I cant see any svnkit in the plugins folder, have I missed a dependency? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
Stuart Whelan updated JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves Change By: Stuart Whelan (04/Mar/13 10:04 PM) Labels: timestamp timestamper Component/s: timestamper This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
Stuart Whelan commented on JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves We also have not seen the problem since disabling the Timestamper 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] (JENKINS-17059) Subversion fails when checking out from repository
Stuart Whelan created JENKINS-17059 Subversion fails when checking out from repository Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: consoleText.txt Components: subversion Created: 04/Mar/13 9:46 PM Description: When a slave attempts to check out or update from the repository we get the error below. Have tried with OSX Slave and Ubuntu Slave, with basic HTTP authentication and on a completely different server over svn:// and no authentication. A manual checkout via the command-line works okay. Slave is running the same user as the manual checkout was run as. I have tired all the different versions of SVN in the configuration dropdown box. The repository url validates okay, and displays an error as expected if I get it wrong. Jenkins will report a problem if I put the wrong credentials when validating the URL, and accept them okay when I get them correct. The stacktrace in the console log is: Started by user Stuart Whelan Building remotely on Ubuntu in workspace /home/swhelan/jenkins/workspace/foo hudson.util.IOException2: remote file operation failed: /home/swhelan/jenkins/workspace/foo at hudson.remoting.Channel@211f1041:Ubuntu at hudson.FilePath.act(FilePath.java:861) at hudson.FilePath.act(FilePath.java:838) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781) at hudson.model.AbstractProject.checkout(AbstractProject.java:1342) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: java.io.IOException: Remote call on Ubuntu failed at hudson.remoting.Channel.call(Channel.java:681) at hudson.FilePath.act(FilePath.java:854) ... 11 more Caused by: java.lang.NoSuchMethodError: org.tmatesoft.svn.core.wc.SVNBasicClient.getOperationsFactory()Lorg/tmatesoft/svn/core/wc2/SvnOperationFactory; at hudson.scm.SvnClientManager.wrapUp(SvnClientManager.java:46) at hudson.scm.SvnClientManager.getWCClient(SvnClientManager.java:38) at hudson.scm.subversion.UpdateUpdater$TaskImpl.parseSvnInfo(UpdateUpdater.java:114) at hudson.scm.subversion.UpdateUpdater$TaskImpl.isUpdatable(UpdateUpdater.java:87) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:120) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Finished: FAILURE Environment: Jenkins master 1.504 running on Windows Server 2008 64Bit. Was also a problem with 1.50[1,2,3] Project: Jenkins Labels:
[JIRA] (JENKINS-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
Stuart Whelan commented on JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves Thanks for the tip of the path Geoff, found my logs there also. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
Stuart Whelan updated JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves Change By: Stuart Whelan (20/Feb/13 4:51 PM) Attachment: hs_err_pid4676.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] (JENKINS-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
Stuart Whelan updated JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves Change By: Stuart Whelan (29/Jan/13 9:36 PM) Environment: Windows 2008 RC2 64Bit for Master and Slaves.Java 64bit 7.0 .9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
Stuart Whelan
updated JENKINS-16528
Jenkins master node crashes often when viewing console logs of builds on slaves
Change By:
Stuart Whelan
(29/Jan/13 9:21 PM)
Description:
Crashes often when viewing the build console log. Nothing in the error log. The jenkins.out.log contains:
#
{quote}{noformat}
# A fatal error has been detected by the Java Runtime Environment:## EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x01bd80e3, pid=2888, tid=2196## JRE version: 6.0_26-b03# Java VM: Java HotSpot(TM) Client VM (20.1-b02 mixed mode windows-x86 )# Problematic frame:# J org.kohsuke.stapler.jelly.groovy.GroovyFacet$1.dispatch(Lorg/kohsuke/stapler/RequestImpl;Lorg/kohsuke/stapler/ResponseImpl;Ljava/lang/Object;)Z## An error report file with more information is saved as:# C:\Windows\system32\hs_err_pid2888.log## If you would like to submit a bug report, please visit:# http://java.sun.com/webapps/bugreport/crash.jsp#
{noformat}{quote}
The hs_err_pid2888.log file does not exist.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
Stuart Whelan created JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 29/Jan/13 9:19 PM Description: Crashes often when viewing the build console log. Nothing in the error log. The jenkins.out.log contains: # A fatal error has been detected by the Java Runtime Environment: # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x01bd80e3, pid=2888, tid=2196 # JRE version: 6.0_26-b03 Java VM: Java HotSpot(TM) Client VM (20.1-b02 mixed mode windows-x86 ) Problematic frame: J org.kohsuke.stapler.jelly.groovy.GroovyFacet$1.dispatch(Lorg/kohsuke/stapler/RequestImpl;Lorg/kohsuke/stapler/ResponseImpl;Ljava/lang/Object;)Z # An error report file with more information is saved as: C:\Windows\system32\hs_err_pid2888.log # If you would like to submit a bug report, please visit: http://java.sun.com/webapps/bugreport/crash.jsp # The hs_err_pid2888.log file does not exist. Environment: Windows 2008 RC2 64Bit for Master and Slaves. Java 64bit 7.0 Project: Jenkins Priority: Critical Reporter: Stuart Whelan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
