[JIRA] [core] (JENKINS-25169) Winstone potentially vulnerable to POODLE (CVE-2014-3566)
Leo Leung edited a comment on JENKINS-25169 Winstone potentially vulnerable to POODLE (CVE-2014-3566) Since Jenkins ver. 1.586, the method to trigger builds remotely using TOKEN authentication URLs with wget described in https://wiki.jenkins-ci.org/display/JENKINS/Authenticating+scripted+clients no longer work due to SSLv1 and SSLv2 is now disabled because of the POODLE vulnerability fix. The following error will appear: Resolving jenkins... 10.0.0.1 Connecting to jenkins|10.0.0.1|:443... connected. Unable to establish SSL connection. The command for wget 1.11.x needs to include the --secure-protocol=TLSv1 option. wget --auth-no-challenge --http-user=user --http-password=apiToken --secure-protocol=TLSv1 http://jenkins.yourcompany.com/job/your_job/build?token=TOKEN This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25169) Winstone potentially vulnerable to POODLE (CVE-2014-3566)
Leo Leung commented on JENKINS-25169 Winstone potentially vulnerable to POODLE (CVE-2014-3566) The method to trigger builds remotely using TOKEN authentication URLs with wget described in https://wiki.jenkins-ci.org/display/JENKINS/Authenticating+scripted+clients no longer work due to SSLv1 and SSLv2 is now disabled because of the POODLE vulnerability fix. The command for wget 1.11.x needs to include the --secure-protocol=TLSv1 parameter. wget --auth-no-challenge --http-user=user --http-password=apiToken --secure-protocol=TLSv1 http://jenkins.yourcompany.com/job/your_job/build?token=TOKEN This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25358) Issues when trying to Install Windows Server
Craig Rodrigues commented on JENKINS-25358 Issues when trying to Install Windows Server Ranganathan, Your bug report is not informative. Just attaching a screenshot is not enough to allow Jenkins developers to help you. Please provide: (1) all the steps which you did to install Jenkins (2) the version of Windows you are using. See this page: http://windows.microsoft.com/en-us/windows/which-operating-system (3) Provide the output of http://yourjenkinshost.com/systemInfo , but substitute "yourjenkinshost.com" with the address and port number of your Jenkins server This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25358) Issues when trying to Install Windows Server
Ranganathan Mohanraj commented on JENKINS-25358 Issues when trying to Install Windows Server Hi Dogfood, I dont see the file path called "core/src/main/java/hudson/util/jna/SHELLEXECUTEINFO.java" in jenkin files. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25358) Issues when trying to Install Windows Server
Ranganathan Mohanraj commented on JENKINS-25358 Issues when trying to Install Windows Server Hi Daniel, Yes, I am new to this software. I taught of copying, anyway given below is the issue. Stack trace javax.servlet.ServletException: java.lang.Error: Structure.getFieldOrder() on class hudson.util.jna.SHELLEXECUTEINFO does not provide enough names ([SEE_MASK_NOCLOSEPROCESS, SW_HIDE, SW_SHOW, cbSize, dwHotKey, fMask, hIcon, hInstApp, hProcess, hkeyClass, hwnd, lpClass, lpDirectory, lpFile, lpIDList, lpParameters, lpVerb, nShow]) to match declared fields ([cbSize, dwHotKey, fMask, hIcon, hInstApp, hProcess, hkeyClass, hwnd, lpClass, lpDirectory, lpFile, lpIDList, lpParameters, lpVerb, nShow]) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) 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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231
[JIRA] [core] (JENKINS-25358) Issues when trying to Install Windows Server
dogfood commented on JENKINS-25358 Issues when trying to Install Windows Server Integrated in jenkins_main_trunk #3788 [FIXED JENKINS-25358] Remove extra fields from getFieldOrder() (Revision f3e9d5d6819b0a96c41f4570487ff42b966d8bb2) JENKINS-25358 Noting merge of #1445. (Revision 8a68ed0e713294747c660abffb6a2f6a668d4e86) Result = SUCCESS rodrigc : f3e9d5d6819b0a96c41f4570487ff42b966d8bb2 Files : core/src/main/java/hudson/util/jna/SHELLEXECUTEINFO.java jesse glick : 8a68ed0e713294747c660abffb6a2f6a668d4e86 Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16454) extension point to browse workspace when build node is offline
Jesse Glick resolved JENKINS-16454 as Fixed extension point to browse workspace when build node is offline This was implemented long ago, as WorkspaceBrowser. Change By: Jesse Glick (30/Oct/14 3:24 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openid-plugin] (JENKINS-23431) Google is phasing out OpenID endpoint. Need to move on to G+ sign-in
kylecordes commented on JENKINS-23431 Google is phasing out OpenID endpoint. Need to move on to G+ sign-in I saw that, and also this variation that works with BitBucket: https://wiki.jenkins-ci.org/display/JENKINS/Bitbucket+OAuth+Plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25353) Git returned status code 128
Mark Waite edited a comment on JENKINS-25353 Git returned status code 128 Reliably removing the lock file and not harming some other use model seems complicated and risky. If a custom workspace is involved, there may be multiple git processes operating in the directory. If a typical workspace is involved, there may be build steps running which start a git process and expect the build step to complete before the git process has completed. What if we removed lock files as part of the optional "clean" step? Would that have resolved the case you detected? Would you have been willing to clean the workspace to remove the lock file? Wiping the workspace should be one way to work around this problem, since wiping the workspace will reconstruct the git repository from a freshly cloned copy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-25353) Git returned status code 128
Mark Waite commented on JENKINS-25353 Git returned status code 128 Reliably removing the lock file and not harming some other use model seems complicated and risky. If a custom workspace is involved, there may be multiple git processes operating in the directory. If a typical workspace is involved, there may be build steps running which start a git process and expect the build step to complete before the git process has completed. What if we removed lock files as part of the optional "clean" step? Would that have resolved the case you detected? Would you have been willing to clean the workspace to remove the lock file? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [openid-plugin] (JENKINS-23431) Google is phasing out OpenID endpoint. Need to move on to G+ sign-in
Kevin Benton commented on JENKINS-23431 Google is phasing out OpenID endpoint. Need to move on to G+ sign-in For those looking for something while waiting for this fix, the github oauth plugin has worked well for us.[1] You can restrict all access to a specific github organization using matrix-based security for a similar effect to using a google apps domain. https://wiki.jenkins-ci.org/display/JENKINS/Github+OAuth+Plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
dogfood commented on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments Integrated in jenkins_main_trunk #3787 [FIXED JENKINS-18366] Winstone is now powered by Jetty (Revision 2394c0cd0e233449c85da3bc75628420a2b07a05) Result = SUCCESS jesse glick : 2394c0cd0e233449c85da3bc75628420a2b07a05 Files : war/pom.xml pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-status-plugin] (JENKINS-25329) java.lang.NoClassDefFoundError: hudson/slaves/SlaveComputer
Xiao Jin Zhao commented on JENKINS-25329 java.lang.NoClassDefFoundError: hudson/slaves/SlaveComputer The issue not reproduced after disconnect/connect the node This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25169) Winstone potentially vulnerable to POODLE (CVE-2014-3566)
dogfood commented on JENKINS-25169 Winstone potentially vulnerable to POODLE (CVE-2014-3566) Integrated in jenkins_main_trunk #3787 JENKINS-25169 integrated the fix for POODLE (Revision 94590fdd69debdfe8469a074b3358f08f6ff0779) Result = SUCCESS jesse glick : 94590fdd69debdfe8469a074b3358f08f6ff0779 Files : war/pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24046) Updating a WAR should unpin a plugin which is now older than the bundled plugin
dogfood commented on JENKINS-24046 Updating a WAR should unpin a plugin which is now older than the bundled plugin Integrated in jenkins_main_trunk #3787 [FIXED JENKINS-24046] (Revision 19f9b63d74693d4de6f6906e9896399d18b4107f) Result = SUCCESS kohsuke : 19f9b63d74693d4de6f6906e9896399d18b4107f Files : core/src/main/java/hudson/ClassicPluginStrategy.java core/src/main/resources/jenkins/diagnostics/PinningIsBlockingBundledPluginMonitor/message.properties core/src/main/java/hudson/PluginWrapper.java core/src/main/java/jenkins/diagnostics/PinningIsBlockingBundledPluginMonitor.java core/src/main/java/hudson/PluginManager.java core/src/main/resources/jenkins/diagnostics/PinningIsBlockingBundledPluginMonitor/message.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-status-plugin] (JENKINS-25329) java.lang.NoClassDefFoundError: hudson/slaves/SlaveComputer
Xiao Jin Zhao updated JENKINS-25329 java.lang.NoClassDefFoundError: hudson/slaves/SlaveComputer Change By: Xiao Jin Zhao (30/Oct/14 2:48 AM) Attachment: logs.zip Attachment: systeminfo.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25358) Issues when trying to Install Windows Server
SCM/JIRA link daemon commented on JENKINS-25358 Issues when trying to Install Windows Server Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/8a68ed0e713294747c660abffb6a2f6a668d4e86 Log: JENKINS-25358 Noting merge of #1445. Compare: https://github.com/jenkinsci/jenkins/compare/47b8d961ae64...8a68ed0e7132 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25358) Issues when trying to Install Windows Server
SCM/JIRA link daemon commented on JENKINS-25358 Issues when trying to Install Windows Server Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/util/jna/SHELLEXECUTEINFO.java http://jenkins-ci.org/commit/jenkins/e22cb19feb73922bae6839afab8f0c75a45976b8 Log: Merge branch 'JENKINS-25358' of github.com:rodrigc/jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25358) Issues when trying to Install Windows Server
SCM/JIRA link daemon resolved JENKINS-25358 as Fixed Issues when trying to Install Windows Server Change By: SCM/JIRA link daemon (30/Oct/14 2:37 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25358) Issues when trying to Install Windows Server
SCM/JIRA link daemon commented on JENKINS-25358 Issues when trying to Install Windows Server Code changed in jenkins User: Craig Rodrigues Path: core/src/main/java/hudson/util/jna/SHELLEXECUTEINFO.java http://jenkins-ci.org/commit/jenkins/f3e9d5d6819b0a96c41f4570487ff42b966d8bb2 Log: [FIXED JENKINS-25358] Remove extra fields from getFieldOrder() Remove fields which are not part of struct _SHELLEXECUTEINFO. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22648) SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput
R. Tyler Croy
commented on JENKINS-22648
SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput
Daniel Beck agreed that these look like different issues, but what's interesting to me is that they're both coming out of the Jelly tag. I'm not familiar enough with Jelly to know whether this means that there might be something busted in core, or something busted in a plugin, or just a general resource constraint being hit here that's causing a weird exception to be thrown ("deflate" lolwut?)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [google-oauth-plugin] (JENKINS-24160) Can this plugin support Google OAuth 2.0?
kylecordes commented on JENKINS-24160 Can this plugin support Google OAuth 2.0? Daniel - would it be suitable to rephrase this item as an issue/feature request, something like "Add support for OpenID Connect or Google+ Sign-in"? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [openid-plugin] (JENKINS-24974) OpenId with Google Apps stopped working in jenkins 1.565.3
kylecordes commented on JENKINS-24974 OpenId with Google Apps stopped working in jenkins 1.565.3 I first thought I might be experiencing a new OpenId problem with Jenkins, but it turns out to be Google phasing our OpenId/OAuth support in favor of their proprietary solution. More info: https://issues.jenkins-ci.org/browse/JENKINS-23431 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23543) Launchctl does not load Jenkins on OS X 10.10 Yosemite
Mark Callow commented on JENKINS-23543 Launchctl does not load Jenkins on OS X 10.10 Yosemite I can confirm that the change I suggested yesterday (I wish this system numbered the comments) works. The new log file created during file rotation is owned by jenkins and the jenkins server therefore continues to run. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [openid-plugin] (JENKINS-23431) Google is phasing out OpenID endpoint. Need to move on to G+ sign-in
kylecordes commented on JENKINS-23431 Google is phasing out OpenID endpoint. Need to move on to G+ sign-in Like others here (and probably many others who haven't found this and commented) I just learned that a newly added Jenkins instance with OpenID plugin won't work with Google, as they are no longer allowing new endpoints. It appears that OpenID Connect would get through until April 2015, then it's all out in favor of their new G+-centric thing. This is clearly a Google-led problem, but certainly and workarounds or other ways to achieve smooth Google auth integration from the Jenkins end would be much appreciated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25370) H in schedule does not work properly for minutes
Ivan Kurnosov commented on JENKINS-25370 H in schedule does not work properly for minutes Okay, further investigations revealed that if there is an active job running at the moment when another SCM Poll is scheduled - then it just does not run This is the access log to the repository server - - [30/Oct/2014:14:03:00 +1300] — - - [30/Oct/2014:14:05:00 +1300] — - - [30/Oct/2014:14:07:00 +1300] — - - [30/Oct/2014:14:11:00 +1300] — - - [30/Oct/2014:14:13:00 +1300] — And at 14:09 some other JOB was running, so the SCM was not polled This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25370) H in schedule does not work properly for minutes
Ivan Kurnosov edited a comment on JENKINS-25370 H in schedule does not work properly for minutes Okay, further investigations revealed that if there is an active job running at the moment when another SCM Poll is scheduled - then it just does not run This is the access log to the repository server - - [30/Oct/2014:14:03:00 +1300] — - - [30/Oct/2014:14:05:00 +1300] — - - [30/Oct/2014:14:07:00 +1300] — - - [30/Oct/2014:14:11:00 +1300] — - - [30/Oct/2014:14:13:00 +1300] — And at 14:09 some other JOB was running, so the SCM was not polled PS: for testing purposes I switched it to `H/2 * * * *` This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-25356) hudson.tasks.junit.AbortException while using maven.test.skip
Nicholas Wertzberger edited a comment on JENKINS-25356 hudson.tasks.junit.AbortException while using maven.test.skip Also having this issue. Running Java 8 + Jenkins 1.586 on RHEL 6 [JENKINS] Recording test results hudson.AbortException: Test reports were found but none of them are new. Did tests run? For example, /home/djbs002/.jenkins/jobs/SGI Web Console/workspace/target/jasmine/TEST-jasmine.xml is 44 yr old at hudson.tasks.junit.TestResult.parse(TestResult.java:213) at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:148) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:634) at hudson.maven.Maven3Builder$MavenExecutionListener.forkSucceeded(Maven3Builder.java:700) at hudson.maven.Maven3Builder$JenkinsEventSpy.onEvent(Maven3Builder.java:31) This is even happening when i do run Jasmine tests, as can be seen below, these tests did not run 44 yr ago: total 165 -rw-r--r-- 1 djbs002 jbsgrp 79943 Oct 29 20:06 FIREFOX_3-ManualSpecRunner.html -rw-r--r-- 1 djbs002 jbsgrp 80171 Oct 29 20:06 FIREFOX_3-SpecRunner.html drwxr-xr-x 8 djbs002 jbsgrp 1024 Jul 30 10:39 js drwxr-xr-x 6 djbs002 jbsgrp 1024 Jul 30 10:39 spec -rw-r--r-- 1 djbs002 jbsgrp 5069 Oct 29 20:06 TEST-jasmine.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-25356) hudson.tasks.junit.AbortException while using maven.test.skip
Nicholas Wertzberger commented on JENKINS-25356 hudson.tasks.junit.AbortException while using maven.test.skip Also having this issue. Running Java 8 + Jenkins 1.586 on RHEL 6 [JENKINS] Recording test results hudson.AbortException: Test reports were found but none of them are new. Did tests run? For example, /home/djbs002/.jenkins/jobs/SGI Web Console/workspace/target/jasmine/TEST-jasmine.xml is 44 yr old at hudson.tasks.junit.TestResult.parse(TestResult.java:213) at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:148) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:634) at hudson.maven.Maven3Builder$MavenExecutionListener.forkSucceeded(Maven3Builder.java:700) at hudson.maven.Maven3Builder$JenkinsEventSpy.onEvent(Maven3Builder.java:31) This is even happening when i do run Jasmine tests: total 165 rw-rr- 1 djbs002 jbsgrp 79943 Oct 29 20:06 FIREFOX_3-ManualSpecRunner.html rw-rr- 1 djbs002 jbsgrp 80171 Oct 29 20:06 FIREFOX_3-SpecRunner.html drwxr-xr-x 8 djbs002 jbsgrp 1024 Jul 30 10:39 js drwxr-xr-x 6 djbs002 jbsgrp 1024 Jul 30 10:39 spec rw-rr- 1 djbs002 jbsgrp 5069 Oct 29 20:06 TEST-jasmine.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25370) H in schedule does not work properly for minutes
Ivan Kurnosov edited a comment on JENKINS-25370 H in schedule does not work properly for minutes @Daniel Beck, "scm polling log" page shows the last time the scheduler triggered (and it's always < 30 in every hour). The point is not that the build is not running, but that SCM is not polled. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25370) H in schedule does not work properly for minutes
Ivan Kurnosov commented on JENKINS-25370 H in schedule does not work properly for minutes @Daniel Beck, on scm polling log shows the last time the scheduler triggered. The point is not that the build is not triggered, but that SCM is not polled. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25370) H in schedule does not work properly for minutes
Ivan Kurnosov edited a comment on JENKINS-25370 H in schedule does not work properly for minutes @Daniel Beck, on scm polling log shows the last time the scheduler triggered (and it's always < 30 in every hour). The point is not that the build is not triggered, but that SCM is not polled. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25370) H in schedule does not work properly for minutes
Daniel Beck commented on JENKINS-25370 H in schedule does not work properly for minutes Poll SCM only triggers builds if it detected changes. Open SCM polling log (in the sidepanel of the job) to see how that went. If all of these are 'Poll SCM' rather than timer trigger, this may well behave as intended. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25144) Basic Authentication in combination with Session is broken
Daniel Beck commented on JENKINS-25144 Basic Authentication in combination with Session is broken No single sign-on though. Everything needs to authenticate. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25370) H in schedule does not work properly for minutes
Ivan Kurnosov updated JENKINS-25370 H in schedule does not work properly for minutes Change By: Ivan Kurnosov (30/Oct/14 12:52 AM) Description: I have several jobs configured with the same schedule interval:H/12 8-18 * * 1-5Which basically should mean: run every 12 minutes in business hours in work days.But the issue is that every of those jobs runs only 3 times. Like at 01, 13, 25 minutes. And none of them run in the second half of the hour.Jenkins Version: LTS 1.565.3 *UPDATE*: even if I specify `* * * * *` - then `SCM Poll` scheduler does not run in the second half of every hour. In 40 minutes I will add what minute is the last run at. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25370) H in schedule does not work properly for minutes
Ivan Kurnosov edited a comment on JENKINS-25370 H in schedule does not work properly for minutes @Daniel Beck, with `H/12 * * * * ` it does not run in the second half of an hour either. With `*/12 * * * * ` it presumably will work but then all the jobs will run simultaneously, so I wanted to avoid it using `H` PS: for these jobs it's "Poll SCM", not "Build Periodically" UPD: ghm, it does not even run it in the second half with `* * * * *` o_O This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25370) H in schedule does not work properly for minutes
Ivan Kurnosov edited a comment on JENKINS-25370 H in schedule does not work properly for minutes @Daniel Beck, with `H/12 * * * * ` it does not run in the second half of an hour either. With `*/12 * * * * ` it presumably will work but then all the jobs will run simultaneously, so I wanted to avoid it using `H` PS: for these jobs it's "Poll SCM", not "Build Periodically" *UPD: ghm, it does not even run it in the second half with ` * * * *` o_O This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25370) H in schedule does not work properly for minutes
Ivan Kurnosov commented on JENKINS-25370 H in schedule does not work properly for minutes @Daniel Beck, with `H/12 * * * * ` it does not run in the second half of an hour either. With `*/12 * * * * ` it presumably will work but then all the jobs will run simultaneously, so I wanted to avoid it using `H` This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [files-found-trigger-plugin] (JENKINS-25354) Directory not found
afra wh updated JENKINS-25354 Directory not found Change By: afra wh (30/Oct/14 12:41 AM) Priority: Critical Major Assignee: stevengbrown This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [files-found-trigger-plugin] (JENKINS-25354) Directory not found
afra wh reopened JENKINS-25354 Directory not found Change By: afra wh (30/Oct/14 12:42 AM) Resolution: Not A Defect Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25144) Basic Authentication in combination with Session is broken
uncletall commented on JENKINS-25144 Basic Authentication in combination with Session is broken There were 89K+ downloads for the LDAP plugin in Sep-2014. I guess indeed that this should be quite common. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
SCM/JIRA link daemon commented on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments Code changed in jenkins User: Kohsuke Kawaguchi Path: pom.xml war/pom.xml http://jenkins-ci.org/commit/jenkins/2394c0cd0e233449c85da3bc75628420a2b07a05 Log: [FIXED JENKINS-18366] Winstone is now powered by Jetty (cherry picked from commit b19f4650d7cc146e28398a33ad0625d46991e27f) Conflicts: changelog.html war/pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25169) Winstone potentially vulnerable to POODLE (CVE-2014-3566)
SCM/JIRA link daemon commented on JENKINS-25169 Winstone potentially vulnerable to POODLE (CVE-2014-3566) Code changed in jenkins User: Kohsuke Kawaguchi Path: war/pom.xml http://jenkins-ci.org/commit/jenkins/94590fdd69debdfe8469a074b3358f08f6ff0779 Log: JENKINS-25169 integrated the fix for POODLE (cherry picked from commit 1351b18e42b1677ee9bb14255583f5b3624d530a) Conflicts: war/pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24046) Updating a WAR should unpin a plugin which is now older than the bundled plugin
SCM/JIRA link daemon resolved JENKINS-24046 as Fixed Updating a WAR should unpin a plugin which is now older than the bundled plugin Change By: SCM/JIRA link daemon (30/Oct/14 12:37 AM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24046) Updating a WAR should unpin a plugin which is now older than the bundled plugin
SCM/JIRA link daemon commented on JENKINS-24046 Updating a WAR should unpin a plugin which is now older than the bundled plugin Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/ClassicPluginStrategy.java core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/PluginWrapper.java core/src/main/java/jenkins/diagnostics/PinningIsBlockingBundledPluginMonitor.java core/src/main/resources/jenkins/diagnostics/PinningIsBlockingBundledPluginMonitor/message.jelly core/src/main/resources/jenkins/diagnostics/PinningIsBlockingBundledPluginMonitor/message.properties http://jenkins-ci.org/commit/jenkins/19f9b63d74693d4de6f6906e9896399d18b4107f Log: [FIXED JENKINS-24046] Warn users if the pinning is preventing Jenkins from overwriting older versions with bundled versions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25370) H in schedule does not work properly for minutes
Daniel Beck commented on JENKINS-25370 H in schedule does not work properly for minutes Does the same issue occur for other (but similar) schedules, e.g. H/12 * * * * ? How about */12 * * * * ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25369) DNS multicast error messages
Daniel Beck commented on JENKINS-25369 DNS multicast error messages Since they're in a third party component, I don't think effort/gain works out in favor of reducing log level. Workaround: java -Dhudson.DNSMultiCast.disabled=true This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25370) H in schedule does not work properly for minutes
Ivan Kurnosov created JENKINS-25370 H in schedule does not work properly for minutes Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Oct/14 12:00 AM Description: I have several jobs configured with the same schedule interval: H/12 8-18 * * 1-5 Which basically should mean: run every 12 minutes in business hours in work days. But the issue is that every of those jobs runs only 3 times. Like at 01, 13, 25 minutes. And none of them run in the second half of the hour. Jenkins Version: LTS 1.565.3 Project: Jenkins Priority: Minor Reporter: Ivan Kurnosov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25369) DNS multicast error messages
Kohsuke Kawaguchi updated JENKINS-25369 DNS multicast error messages Change By: Kohsuke Kawaguchi (29/Oct/14 11:26 PM) Summary: Recurring DNS multicast error messages on a plain vanilla jenkins (no jobs configured) Description: I've seen [these error messages|https://gist.github.com/uaarkoti/75fc1292ed921238770e] in my console output, which comes from jmdns.The level of the logging messages should be toned down significantly given that these are from a relatively minor feature in Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25369) Recurring error messages on a plain vanilla jenkins (no jobs configured)
Udaypal Aarkoti updated JENKINS-25369 Recurring error messages on a plain vanilla jenkins (no jobs configured) Change By: Udaypal Aarkoti (29/Oct/14 11:23 PM) Description: Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming readAnswerWARNING: There was an OPT answer. Not currently handled. Option code: 0 data:Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming readAnswerWARNING: There was an OPT answer. Not currently handled. Option code: 40960 data:Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming readAnswerWARNING: There was an OPT answer. Not currently handled. Option code: 0 data:Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming readAnswerWARNING: There was an OPT answer. Not currently handled. Option code: 59904 data:Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming readAnswerWARNING: There was an OPT answer. Not currently handled. Option code: 65486 data:Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming readAnswerWARNING: There was a problem reading the OPT record. Ignoring.Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming$MessageInputStream readNameSEVERE: Extended label are not currently supported.Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming$MessageInputStream readNameSEVERE: bad domain name: possible circular name detected. Bad offset: 0x at 0x249Oct 29, 2014 4:04:50 PM javax.jmdns.impl.constants.DNSRecordType typeForIndexSEVERE: Could not find record type for index: -1Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming readAnswerSEVERE: Could not find record type. domain:dns[query,192.168.253.42:5353, length=587, id=0x0, questions=7, authorities=9questions: [AllRecords@1075896505 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: zero._ssh._tcp.local.] [AllRecords@1126595816 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: zero.local.] [AllRecords@1227188214 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: zero._sftp-ssh._tcp.local.] [AllRecords@1475477511 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: 42.253.168.192.in-addr.arpa.] [AllRecords@269490024 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: zero._device-info._tcp.local.] [AllRecords@1612835006 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: 52821._keepalive._dns-sd._udp.local.] [AllRecords@47790491 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: 2.6.b.4.d.0.e.f.f.f.0.5.6.e.2.8.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa.]authorities: [Service@1164768255 type: TYPE_SRV index 33, class: CLASS_IN index 1, name: zero._ssh._tcp.local. ttl: '4499/4500' server: 'zero.local.:22'] [Text@1431766893 type: TYPE_TXT index 16, class: CLASS_IN index 1, name: zero._ssh._tcp.local. ttl: '4499/4500' text: ''] [IPv6Address@987521377 type: TYPE_ index 28, class: CLASS_IN index 1, name: zero.local. ttl: '119/120' address: 'fe80:0:0:0:82e6:50ff:fe0d:4b62'] [IPv4Address@1895993920 type: TYPE_A index 1, class: CLASS_IN index 1, name: zero.local. ttl: '119/120' address: '192.168.253.42'] [Service@1406366868 type: TYPE_SRV index 33, class: CLASS_IN index 1, name: zero._sftp-ssh._tcp.local. ttl: '4499/4500' server: 'zero.local.:22'] [Text@1053978092 type: TYPE_TXT index 16, class: CLASS_IN index 1, name: zero._sftp-ssh._tcp.local. ttl: '4499/4500' text: ''] [Pointer@1742521406 type: TYPE_PTR index 12, class: CLASS_IN index 1, name: 42.253.168.192.in-addr.arpa. ttl: '119/120' alias: 'zero.local.'] [Text@44681751 type: TYPE_TXT index 16, class: CLASS_IN index 1, name: zero._device-info._tcp.local. ttl: '4499/4500' text: 'model=MacBookPro...'] [Pointer@1251375362 type: TYPE_PTR index 12, class: CLASS_IN index 1, name: 2.6.b.4.d.0.e.f.f.f.0.5.6.e.2.8.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ttl: '119/120' alias: 'zero.local.']] question: [AllRecords@1075896505 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: zero._ssh._tcp.local.] question: [AllRecords@1126595816 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: zero.local.] question: [AllRecords@1227188214 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: zero._sftp-ssh._tcp.local.] question: [AllRecords@1475477511 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: 42.253.168.192.in-addr.arpa.] question: [AllRecords@269490024 type: TYP
[JIRA] [core] (JENKINS-25369) Recurring error messages on a plain vanilla jenkins (no jobs configured)
Udaypal Aarkoti created JENKINS-25369 Recurring error messages on a plain vanilla jenkins (no jobs configured) Issue Type: Bug Assignee: Unassigned Components: core Created: 29/Oct/14 11:19 PM Description: Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming readAnswer WARNING: There was an OPT answer. Not currently handled. Option code: 0 data: Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming readAnswer WARNING: There was an OPT answer. Not currently handled. Option code: 40960 data: Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming readAnswer WARNING: There was an OPT answer. Not currently handled. Option code: 0 data: Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming readAnswer WARNING: There was an OPT answer. Not currently handled. Option code: 59904 data: Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming readAnswer WARNING: There was an OPT answer. Not currently handled. Option code: 65486 data: Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming readAnswer WARNING: There was a problem reading the OPT record. Ignoring. Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming$MessageInputStream readName SEVERE: Extended label are not currently supported. Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming$MessageInputStream readName SEVERE: bad domain name: possible circular name detected. Bad offset: 0x at 0x249 Oct 29, 2014 4:04:50 PM javax.jmdns.impl.constants.DNSRecordType typeForIndex SEVERE: Could not find record type for index: -1 Oct 29, 2014 4:04:50 PM javax.jmdns.impl.DNSIncoming readAnswer SEVERE: Could not find record type. domain: dns[query,192.168.253.42:5353, length=587, id=0x0, questions=7, authorities=9 questions: [AllRecords@1075896505 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: zero._ssh._tcp.local.] [AllRecords@1126595816 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: zero.local.] [AllRecords@1227188214 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: zero._sftp-ssh._tcp.local.] [AllRecords@1475477511 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: 42.253.168.192.in-addr.arpa.] [AllRecords@269490024 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: zero._device-info._tcp.local.] [AllRecords@1612835006 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: 52821._keepalive._dns-sd._udp.local.] [AllRecords@47790491 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: 2.6.b.4.d.0.e.f.f.f.0.5.6.e.2.8.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa.] authorities: [Service@1164768255 type: TYPE_SRV index 33, class: CLASS_IN index 1, name: zero._ssh._tcp.local. ttl: '4499/4500' server: 'zero.local.:22'] [Text@1431766893 type: TYPE_TXT index 16, class: CLASS_IN index 1, name: zero._ssh._tcp.local. ttl: '4499/4500' text: ''] [IPv6Address@987521377 type: TYPE_ index 28, class: CLASS_IN index 1, name: zero.local. ttl: '119/120' address: 'fe80:0:0:0:82e6:50ff:fe0d:4b62'] [IPv4Address@1895993920 type: TYPE_A index 1, class: CLASS_IN index 1, name: zero.local. ttl: '119/120' address: '192.168.253.42'] [Service@1406366868 type: TYPE_SRV index 33, class: CLASS_IN index 1, name: zero._sftp-ssh._tcp.local. ttl: '4499/4500' server: 'zero.local.:22'] [Text@1053978092 type: TYPE_TXT index 16, class: CLASS_IN index 1, name: zero._sftp-ssh._tcp.local. ttl: '4499/4500' text: ''] [Pointer@1742521406 type: TYPE_PTR index 12, class: CLASS_IN index 1, name: 42.253.168.192.in-addr.arpa. ttl: '119/120' alias: 'zero.local.'] [Text@44681751 type: TYPE_TXT index 16, class: CLASS_IN index 1, name: zero._device-info._tcp.local. ttl: '4499/4500' text: 'model=MacBookPro...'] [Pointer@1251375362 type: TYPE_PTR index 12, class: CLASS_IN index 1, name: 2.6.b.4.d.0.e.f.f.f.0.5.6.e.2.8.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ttl: '119/120' alias: 'zero.local.']] question: [AllRecords@1075896505 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: zero._ssh._tcp.local.] question: [AllRecords@1126595816 type: TYPE_ANY index 255, class: CLASS_IN index 1, name: zero.local.] question: [AllRecords@1227188214 type: TYPE_ANY index 255, class: CLASS_IN index 1
[JIRA] [core] (JENKINS-22648) SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput
Daniel Beck commented on JENKINS-22648 SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput That looks like a completely different issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-2487) "Please wait, getting ready to work" takes very long
Daniel Beck commented on JENKINS-2487 "Please wait, getting ready to work" takes very long Relevant information for filing performance-related issues can be found here: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25221) Content of "Custom Workspace" changes in v1.585
dogfood commented on JENKINS-25221 Content of "Custom Workspace" changes in v1.585 Integrated in jenkins_main_trunk #3785 [FIXED JENKINS-25221] Noting merge of #1446. (Revision 3880e00190a7432ad6aa53186fdb62154d3218a0) Result = SUCCESS jesse glick : 3880e00190a7432ad6aa53186fdb62154d3218a0 Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-15065) Gerrit server suddenly shutdown and as a consequence the Jenkins Gerrit-Trigger fails to restart.
Joshua Kugler commented on JENKINS-15065 Gerrit server suddenly shutdown and as a consequence the Jenkins Gerrit-Trigger fails to restart. Just experienced this on Jenkins 1.583, Gerrit Trigger 2.3.1 (yes, old version, but from above comments, seems to exist in recent versions as well). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [other] (JENKINS-2487) "Please wait, getting ready to work" takes very long
Jesse Glick resolved JENKINS-2487 as Incomplete "Please wait, getting ready to work" takes very long This issue is too vague and general to be worth keeping open. If there are specific startup performance problems reproducible in current versions of Jenkins they should be filed with details. Change By: Jesse Glick (29/Oct/14 10:32 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs] (JENKINS-25368) Add an option to hide the long list of files checked out by TFS
Brent Olson created JENKINS-25368 Add an option to hide the long list of files checked out by TFS Issue Type: Improvement Assignee: redsolo Components: tfs Created: 29/Oct/14 10:12 PM Description: We have a long list of files that we're checking out, and the file list crowds the console log. This improvement suggests that we offer some hack that will still display the workspace information, but will suppress the text of the the "tf get" command. "tf get" doesn't have the equivalent of a /quiet option, so we can't simply invoke that. Obviously, if there are errors associated with the get, you would still want to see that. Perhaps the option could pipe the stdout to /dev/nul (null on win)? Environment: currently using tfs plugin 3.1.1 Project: Jenkins Priority: Minor Reporter: Brent Olson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25221) Content of "Custom Workspace" changes in v1.585
SCM/JIRA link daemon commented on JENKINS-25221 Content of "Custom Workspace" changes in v1.585 Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/3880e00190a7432ad6aa53186fdb62154d3218a0 Log: [FIXED JENKINS-25221] Noting merge of #1446. Compare: https://github.com/jenkinsci/jenkins/compare/86ea65ab6fe7...3880e00190a7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25221) Content of "Custom Workspace" changes in v1.585
SCM/JIRA link daemon resolved JENKINS-25221 as Fixed Content of "Custom Workspace" changes in v1.585 Change By: SCM/JIRA link daemon (29/Oct/14 10:11 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/d/optout.
[JIRA] [core] (JENKINS-25221) Content of "Custom Workspace" changes in v1.585
Jesse Glick updated JENKINS-25221 Content of "Custom Workspace" changes in v1.585 Change By: Jesse Glick (29/Oct/14 10:05 PM) Labels: core form-data regression stapler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22648) SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput
Sam Xiao
updated JENKINS-22648
SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput
Change By:
Sam Xiao
(29/Oct/14 10:04 PM)
Description:
After upgraded to 1.532.2 LTS, start seeing this error{noformat}Apr 16, 2014 2:54:40 PM winstone.Logger logInternalSEVERE: Error in the error servletjavax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.532.3.jar!/lib/layout/layout.jelly:143:68: Could not write to XMLOutput 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$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.include(RequestDispatcher.java:199) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:251) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) 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:744)Caused by: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.532.3.jar!/lib/layout/layout.jelly:143:68: Could not write to XMLOutput at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:72) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.kohsuke.stapler.jelly.CompressTag.doTag(CompressTag.java:44) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:95) ... 22 moreCaused by: org.xml.sax.SAXException: Failed to write to clientwinstone.ClientSocketException: Failed to write to client at org.dom4j.io.XMLWriter.handleException(XMLWriter.java:1888)
[JIRA] [core] (JENKINS-22648) SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput
Sam Xiao edited a comment on JENKINS-22648 SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput still reproducible on 1.565.3 Oct 29, 2014 2:54:45 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.565.3.jar!/lib/layout/layout.jelly:75:72: failed to deflate: error=-2 avail_out=512 at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:636) at hudson.init.impl.InstallUncaughtExceptionHandler$1.reportException(InstallUncaughtExceptionHandler.java:27) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:63) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.565.3.jar!/lib/layout/layout.jelly:75:72: failed to deflate: error=-2 avail_out=512 at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.ja
[JIRA] [core] (JENKINS-22648) SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput
Sam Xiao commented on JENKINS-22648 SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput still reproducible Oct 29, 2014 2:54:45 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.565.3.jar!/lib/layout/layout.jelly:75:72: failed to deflate: error=-2 avail_out=512 at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:636) at hudson.init.impl.InstallUncaughtExceptionHandler$1.reportException(InstallUncaughtExceptionHandler.java:27) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:63) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.565.3.jar!/lib/layout/layout.jelly:75:72: failed to deflate: error=-2 avail_out=512 at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) a
[JIRA] [core] (JENKINS-22648) SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput
Sam Xiao commented on JENKINS-22648 SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput Change priority to "critical" as this is blocking the UI response and making the web UI unresponsive, which renders the jenkins master instance in hanging state. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-23152) builds getting lost due to GerritTrigger
SCM/JIRA link daemon commented on JENKINS-23152 builds getting lost due to GerritTrigger Code changed in jenkins User: Robert Sandell Path: pom.xml src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/model/BuildMemory.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerTimerTask.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/spec/SpecGerritTriggerHudsonTest.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/24c7b25dbf75925379480f0cbfda8903c0d336db Log: Merge branch 'reload-JENKINS-23152' of github.com:jglick/gerrit-trigger-plugin into JENKINS-23152 Conflicts: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/spec/SpecGerritTriggerHudsonTest.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scp] (JENKINS-25367) Unable to SCP a jar file to a remote server
joom ster commented on JENKINS-25367 Unable to SCP a jar file to a remote server my jar is built on jenkins server at /xyz/target/*.jar and destination is my server x...@xxx.com:/home/user/jars This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [scp] (JENKINS-25367) Unable to SCP a jar file to a remote server
joom ster created JENKINS-25367 Unable to SCP a jar file to a remote server Issue Type: Bug Assignee: ramazanyich2 Components: scp Created: 29/Oct/14 9:29 PM Description: I am unable to scp a jar file to my remote server as a post build step, I keep getting the following exception [SCP] Connecting to "Server" ERROR: Failed to upload files 4: at com.jcraft.jsch.ChannelSftp.stat(ChannelSftp.java:1720) at be.certipost.hudson.plugin.SCPSite.upload(SCPSite.java:188) at be.certipost.hudson.plugin.SCPRepositoryPublisher.perform(SCPRepositoryPublisher.java:211) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: 0 at java.lang.String.charAt(String.java:658) at com.jcraft.jsch.ChannelSftp.remoteAbsolutePath(ChannelSftp.java:2359) at com.jcraft.jsch.ChannelSftp.stat(ChannelSftp.java:1711) ... 11 more Build step 'Publish artifacts to SCP Repository' changed build result to UNSTABLE Finished: UNSTABLE Can Someone please help? Project: Jenkins Priority: Blocker Reporter: joom ster This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [naginator] (JENKINS-22459) NullPointerException in NaginatorActionFactory caused by empty "Managed windows batch" build step
jminne commented on JENKINS-22459 NullPointerException in NaginatorActionFactory caused by empty "Managed windows batch" build step I also ran into this stacktrace again and the cause this time was invalid credentials being used by the Remote Trigger plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-22456) github plugin too many open files unclosed github-polling.log filehandles causes all builds to fail
Jesse Glick commented on JENKINS-22456 github plugin too many open files unclosed github-polling.log filehandles causes all builds to fail I installed the File Leak Detector plugin and activated it, but could not reproduce. Various accesses to github-polling.log all reliably close the file. However I also did not manage to get a hook added, despite using a valid API token to connect to my own repo: java.io.FileNotFoundException: https://api.github.com/repos/jglick/simple-maven-project-with-tests/hooks at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1624) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) at org.kohsuke.github.Requester.parse(Requester.java:383) at org.kohsuke.github.Requester._to(Requester.java:185) at org.kohsuke.github.Requester.to(Requester.java:160) at org.kohsuke.github.GHRepository.createHook(GHRepository.java:754) at com.cloudbees.jenkins.GitHubPushTrigger.createJenkinsHook(GitHubPushTrigger.java:161) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20531) Retry count not working in Git plugin 2.0
Mark Waite commented on JENKINS-20531 Retry count not working in Git plugin 2.0 Would this pull request improve the code (better to do it before I release 2.2.8, rather than after)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [remoting] (JENKINS-25272) remoting-2.46.jar breaks Maven 5 builds
Jesse Glick commented on JENKINS-25272 remoting-2.46.jar breaks Maven 5 builds it is not easy to know the correct JAVA_HOME I think you can just use something like $JDK_5_HOME from the Maven goals field after defining such a variable using the Tool Env plugin. But yes it would be good to get the automatic switch working again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25144) Basic Authentication in combination with Session is broken
andreasmandel commented on JENKINS-25144 Basic Authentication in combination with Session is broken Is there an alternative way? I need a 2nd component to perform authentication (against an LDAP server) and single sign on for other tools accessible on this server. All is nicely done by using a Apache with mod proxy and mod_authnz_ldap. I guess this is quite common, at least for larger setups? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22456) github plugin too many open files unclosed github-polling.log filehandles causes all builds to fail
Jesse Glick updated JENKINS-22456 github plugin too many open files unclosed github-polling.log filehandles causes all builds to fail Change By: Jesse Glick (29/Oct/14 8:20 PM) Labels: leak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20531) Retry count not working in Git plugin 2.0
Jesse Glick commented on JENKINS-20531 Retry count not working in Git plugin 2.0 It would not be source-compatible. Whether this is a problem or not is a matter of judgement; arguably a caller of Git commands ought to be aware of the possibility that a command could fail and have thought about how that should be handled. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
Jesse Glick commented on JENKINS-25340 lost trend history after skipping build If you delete the aborted builds then definitely the graph will stop there; that is the limitation of the current algorithm. But builds which are displayed in Build History, including aborted ones, ought not be a barrier, because displaying the history widget should be forcing them to be in memory. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25226) Perforce Plugin Substitutes default Parameter Value instead of actual Parameter Value for client name
stuart rowe commented on JENKINS-25226 Perforce Plugin Substitutes default Parameter Value instead of actual Parameter Value for client name Thanks, I never got around to looking into it This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-25366) Load parameters from file jobs will fail to remote trigger if nothing is entered in the textbox
Thanh Ha created JENKINS-25366 Load parameters from file jobs will fail to remote trigger if nothing is entered in the textbox Issue Type: Bug Assignee: Maurice W. Components: parameterized-remote-trigger Created: 29/Oct/14 7:35 PM Description: When creating a remote trigger using this plugin. If you check the "Load parameters from file" and pass it a file while leaving the Parameter text box just above it empty. The job will fail to trigger the remote job. Workaround is to put anything in the text box such as a comment "# Comment". Project: Jenkins Priority: Major Reporter: Thanh Ha This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [svn-tag] (JENKINS-25359) old svn tags get deleted / please give option to prevent deletion of old svn tags
k2nakamura assigned JENKINS-25359 to Renjith V old svn tags get deleted / please give option to prevent deletion of old svn tags Change By: k2nakamura (29/Oct/14 7:31 PM) Assignee: k2nakamura Renjith V This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
Kanstantsin Shautsou commented on JENKINS-25340 lost trend history after skipping build FreeStyle. When new success/unstable jobs appeared - only new jobs appeared in Trend. Then i deleted skipped builds and graph is still without not full. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
Kanstantsin Shautsou edited a comment on JENKINS-25340 lost trend history after skipping build FreeStyle. When new success/unstable jobs appeared - only new jobs appeared in Trend. Then i deleted skipped builds and graph is still not full. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25226) Perforce Plugin Substitutes default Parameter Value instead of actual Parameter Value for client name
Oleg Nenashev commented on JENKINS-25226 Perforce Plugin Substitutes default Parameter Value instead of actual Parameter Value for client name This issue has been caused by a new variables substitution mechanism. https://github.com/jenkinsci/perforce-plugin/pull/54 I'll handle it This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-19579) Add support of workspace variables during the workspace cleanup
Oleg Nenashev resolved JENKINS-19579 as Duplicate Add support of workspace variables during the workspace cleanup Change By: Oleg Nenashev (29/Oct/14 7:20 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-23467) Streamline the variables handling
Oleg Nenashev commented on JENKINS-23467 Streamline the variables handling https://github.com/jenkinsci/perforce-plugin/pull/54 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-23467) Streamline the variables handling
Oleg Nenashev started work on JENKINS-23467 Streamline the variables handling Change By: Oleg Nenashev (29/Oct/14 7:19 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25226) Perforce Plugin Substitutes default Parameter Value instead of actual Parameter Value for client name
Oleg Nenashev started work on JENKINS-25226 Perforce Plugin Substitutes default Parameter Value instead of actual Parameter Value for client name Change By: Oleg Nenashev (29/Oct/14 7:17 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25365) [VariablesSubstitutionHelper] - Multi-line strings with variables are not being substituted
Oleg Nenashev started work on JENKINS-25365 [VariablesSubstitutionHelper] - Multi-line strings with variables are not being substituted Change By: Oleg Nenashev (29/Oct/14 7:17 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25365) [VariablesSubstitutionHelper] - Multi-line strings with variables are not being substituted
Oleg Nenashev assigned JENKINS-25365 to Oleg Nenashev [VariablesSubstitutionHelper] - Multi-line strings with variables are not being substituted Change By: Oleg Nenashev (29/Oct/14 7:16 PM) Assignee: Rob Petti Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25365) [VariablesSubstitutionHelper] - Multi-line strings with variables are not being substituted
Oleg Nenashev
created JENKINS-25365
[VariablesSubstitutionHelper] - Multi-line strings with variables are not being substituted
Issue Type:
Bug
Assignee:
Rob Petti
Components:
perforce-plugin
Created:
29/Oct/14 7:16 PM
Description:
Example (view spec):
$Unknown macro: {param1} ... //p/param1/...
$Unknown macro: {param2} ... //p/param2/...
Output:
Warning: Client Spec line invalid, ignoring. (${param1}... //p/param1/...)
Warning: Client Spec line invalid, ignoring. (${param2}... //p/param2/...)
Project:
Jenkins
Priority:
Critical
Reporter:
Oleg Nenashev
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25226) Perforce Plugin Substitutes default Parameter Value instead of actual Parameter Value for client name
Oleg Nenashev assigned JENKINS-25226 to Oleg Nenashev Perforce Plugin Substitutes default Parameter Value instead of actual Parameter Value for client name Change By: Oleg Nenashev (29/Oct/14 7:09 PM) Assignee: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-25263) Multi Config Project broken "Custom Workspace"
Dana Goyette
commented on JENKINS-25263
Multi Config Project broken "Custom Workspace"
After setting custom workspace to "/parent/here" and child workspace to "/child/here", a few cycles of reloading the page and then hitting Apply (with no other changes) results in the following value for "Directory" and "Directory for sub-builds", respectively:
{"directory":["{\"directory\":[\"{\\\"directory\\\":[\\\"/parent/here\\\",\\\"/child/here\\\"]}\",\"/child/here\"]}","/child/here"]}
/child/here
I've had a job become completely un-editable due to this bug.
Attempting to save the job gave "Form Too Large", and clicking "Advanced" did not expose the text box.
The job only became editable after deleting the workspace definition in the job's config.xml, and restarting the server.
In my broken case, the field had turned into 28 kilobytes of the following:
{"directory":["{\"directory\":[\"{\\\"directory\\\":[\\\"{\\\"directory\\\":[\\\"{\\\"directory\\\":[\\\"{\\\"directory\\\": ...
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
Jesse Glick commented on JENKINS-25340 lost trend history after skipping build By the way I just tried to reproduce this bug with a freestyle project and could not. The aborted builds are still shown in Build History, and are simply skipped over in Test Result Trend (like any other build which exists on disk but has no test result action). Are you using another job type? Or is LogRotator configured to delete these aborted builds? AbstractTestResultAction.getPreviousResult is going to need a test using RunLoadCounter to avoid accidental regressions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25026) Console output stops populating after several seconds
Christoph Vogtländer commented on JENKINS-25026 Console output stops populating after several seconds I have the same problem but it does not seem to be server related... in IE update is working as expected but not in FF. So it seems to be an issue on the client side. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
Jesse Glick commented on JENKINS-25340 lost trend history after skipping build As an aside, as to why JENKINS-23945 took so long to be reported: in part because there were other even more serious lazy-loading bugs masking it for a while (such as JENKINS-18065). After that, just because you were suffering from that bug does not mean you knew that a particular graph in the corner of the job index page was thrashing the system. You may just have concluded that Jenkins did not scale well to large systems and thrown more hardware at it, or put up with five-minute page loads. That is the problem with performance/scalability bugs: people cannot clamor for fixes of problems they cannot even identify without training and tools. JENKINS-25078 is another example: once the administrator was told what the source of the problem was, and how to opt out of what was for that installation an unnecessary feature, massive performance problems suddenly vanished. So we need to strike a balance of unconditionally showing useful data only when it is cheap to compute, and somehow allowing the admin (or a browsing user) to opt in to potentially more expensive but thorough reports in a way that makes the tradeoff clear. (And of course in the longer term we need to find a way of storing build records that makes display of routine metadata actually be cheap.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [analysis-core] (JENKINS-24940) New Warnings link in Static Analysis results shows all warnings
Daniel Beck commented on JENKINS-24940 New Warnings link in Static Analysis results shows all warnings Maybe also consider what the desired behavior should be when a build is deleted between two other builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core] (JENKINS-24940) New Warnings link in Static Analysis results shows all warnings
Ulli Hafner commented on JENKINS-24940 New Warnings link in Static Analysis results shows all warnings I see. That makes sense: the number of new warnings is computed and persisted for each build (i.e. constant for lifetime). On the other hand, the actual new warnings are computed dynamically by reading the current and previous warnings. If the previous warnings are deleted (because the build got discarded), then all warnings of the oldest build are new. In order to fix that I would need to introduce an additional field for each warning that denotes if the warning is new or not. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [analysis-core] (JENKINS-24940) New Warnings link in Static Analysis results shows all warnings
Ulli Hafner updated JENKINS-24940 New Warnings link in Static Analysis results shows all warnings Change By: Ulli Hafner (29/Oct/14 6:18 PM) Priority: Major Minor Component/s: analysis-collector This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20531) Retry count not working in Git plugin 2.0
Mark Waite commented on JENKINS-20531 Retry count not working in Git plugin 2.0 It is only marked as open because I haven't been through the fixes prepared for the git plugin 2.2.8 release to assure they are all marked as resolved before it is released. I am hesitant to change the inheritance of GitException lest that break compatibility for unknown consumers. Is that a compatibility safe change? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-23660) Attached log in Jenkins email incomplete
Alex Earl assigned JENKINS-23660 to Alex Earl Attached log in Jenkins email incomplete Change By: Alex Earl (29/Oct/14 5:51 PM) Assignee: Alex Earl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20531) Retry count not working in Git plugin 2.0
Jesse Glick commented on JENKINS-20531 Retry count not working in Git plugin 2.0 Is there a reason this issue is still marked Open? The fix seems a bit off. Either defaultCheckout should catch general Exception, and/or GitException should be made to extend IOException rather than RuntimeException. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth] (JENKINS-17539) Swarm clients fail to connect if GitHub for authentication
Atish Narlawar commented on JENKINS-17539 Swarm clients fail to connect if GitHub for authentication I think this issue is resolved with v20. I ask @Sam to have a look again before mark it resolve This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
