[JIRA] [active-directory-plugin] (JENKINS-13940) I'm trying to authenticate the Jenkins command line (CLI) and the system returns an error message (user authentication with AD), but the GUI works.
Dmitrijs Sahlovs commented on JENKINS-13940 Im trying to authenticate the Jenkins command line (CLI) and the system returns an error message (user authentication with AD), but the GUI works. Could you please be more specific? Should I use something like java -jar jenkins-cli.jar -s http://example.net:port/jenkins/ login --username USERNAME --password APITOKEN? If yes, than I receive following exception: org.acegisecurity.BadCredentialsException: Either no such user 'usern...@example.net' or incorrect password; nested exception is javax.naming.AuthenticationException: LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903AA, comment:AcceptSecurityContext error, data 52e, v1772 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gradle-jpi-plugin] (JENKINS-25401) Libraries not included in JPI file
Daniel Spilker closed JENKINS-25401 as Fixed Libraries not included in JPI file Change By: Daniel Spilker (04/Nov/14 8:17 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-25401) Libraries not included in JPI file
Daniel Spilker resolved JENKINS-25401 as Fixed Libraries not included in JPI file fixed in version 0.7.1 Change By: Daniel Spilker (04/Nov/14 8:16 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] [maven-plugin] (JENKINS-25416) text parameter with newlines causing the default goal run
Daniel Beck commented on JENKINS-25416 text parameter with newlines causing the default goal run Possibly. Could you try with ant 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] [core] (JENKINS-25422) OS X installer creates local jenkins user even when network jenkins user exists
Mark Callow created JENKINS-25422 OS X installer creates local jenkins user even when network jenkins user exists Issue Type: Bug Assignee: Unassigned Components: core Created: 04/Nov/14 8:19 AM Description: We have an Active Directory network user "jenkins" intended to be the jenkins user for all masters and slaves on our network. Even though I was logged in as that user when I ran the OS X installer, it created a local "jenkins" user which it made the owner of the jenkins installation and the user under which launchd runs jenkins. It completely failed to notice that the current user was "jenkins" or that there was a "jenkins" network user. After this I removed the jenkins installation and local jenkins user and tried again, paying more attention to the installer options. The installer provides no way to pick a different existing user. It really should. It just blindly creates the local "jenkins". It is possible that the user and group ids are hardcoded as 240 as well. That is the ID that was used both times I ran the installer. I do not want to manually fix up the installation because I expect the next time I install an update the installer will create local "jenkins" again. Environment: OS X 10.9; Jenkins 1.585 Project: Jenkins Priority: Major Reporter: Mark Callow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [active-directory-plugin] (JENKINS-13940) I'm trying to authenticate the Jenkins command line (CLI) and the system returns an error message (user authentication with AD), but the GUI works.
Daniel Beck commented on JENKINS-13940 Im trying to authenticate the Jenkins command line (CLI) and the system returns an error message (user authentication with AD), but the GUI works. Right, that would have been it. I guess 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] [core] (JENKINS-25423) OS X installer should let user choose the user that will own jenkins
Mark Callow created JENKINS-25423 OS X installer should let user choose the user that will own jenkins Issue Type: Improvement Assignee: Unassigned Components: core Created: 04/Nov/14 8:24 AM Description: The OS X installer does not provide a way for its user to choose the name of the user that will own the jenkins installation and under whose ID the jenkins daemon will run. It should. It blindly creates a user "jenkins". Offering this choice is one way to fix issue #25422. Environment: OS X 10.9; Jenkins 1.585 Project: Jenkins Priority: Major Reporter: Mark Callow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25422) OS X installer creates local jenkins user even when network jenkins user exists
Daniel Beck commented on JENKINS-25422 OS X installer creates local jenkins user even when network jenkins user exists Actually, it tries to find existing users named jenkins: https://github.com/jenkinsci/jenkins/blob/master/osx/scripts/postinstall-launchd-jenkins#L13 And uses a deterministic approach to finding a UID below 500: https://github.com/jenkinsci/jenkins/blob/master/osx/scripts/postinstall-launchd-jenkins#L22 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin-proposals] (JENKINS-25415) Develop and implement a Continuous Integration Experience Index
Torsten Schlabach updated JENKINS-25415 Develop and implement a Continuous Integration Experience Index Change By: Torsten Schlabach (04/Nov/14 8:27 AM) Component/s: plugin-proposals Component/s: performance-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-25424) Exception when editing nodes
Andreas Holzmann created JENKINS-25424 Exception when editing nodes Issue Type: Bug Assignee: Unassigned Components: core Created: 04/Nov/14 8:26 AM Description: When I press the edit node link I get the following OOPS with Stack trace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.588.jar!/lib/form/descriptorList.jelly:78:49: j:forEach class hudson.plugins.xvnc.DisplayAllocator$Property is missing its descriptor at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) Environment: Jenkins ver. 1.588 Project: Jenkins Labels: exception Priority: Major Reporter: Andreas Holzmann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25423) OS X installer should let user choose the user that will own jenkins
Mark Callow updated JENKINS-25423 OS X installer should let user choose the user that will own jenkins Change By: Mark Callow (04/Nov/14 8:28 AM) Description: TheOSXinstallerdoesnotprovideawayforitsusertochoosethenameoftheuserthatwillownthejenkinsinstallationandunderwhoseIDthejenkinsdaemonwillrun.Itshould.Itblindlycreatesauserjenkins.Offeringthischoiceisonewaytofix [ issue#25422 |https://issues . jenkins-ci.org/browse/JENKINS-25422]. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-collector-plugin] (JENKINS-25425) Wrong link in Test Result column in custom view
Andreas Holzmann created JENKINS-25425 Wrong link in Test Result column in custom view Issue Type: Bug Assignee: Ulli Hafner Components: analysis-collector-plugin Created: 04/Nov/14 8:33 AM Description: I'm using the column "Test Result" with format "Test format 1" in a custom view. The link that is used here is for example http://server/view/Tests/view/Tests/job/Project/lastCompletedBuild/testReport/ The "view/Tests" part is duplicated and the link therefore does not work. This happens only on newly created views. The default "All" view uses the correct link with "view/Tests" part only once. Environment: Jenkins ver. 1.588, analysis-collector version 1.41 Project: Jenkins Labels: plugin Priority: Major Reporter: Andreas Holzmann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25423) OS X installer should let user choose the user that will own jenkins
Daniel Beck commented on JENKINS-25423 OS X installer should let user choose the user that will own jenkins If you want that level of control, don't use an installer. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gradle-jpi-plugin] (JENKINS-12193) Hook up injected tests
Daniel Spilker assigned JENKINS-12193 to Daniel Spilker Hook up injected tests Change By: Daniel Spilker (04/Nov/14 8:35 AM) Assignee: abayer DanielSpilker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-25405) Plugins depending on Analysis Core plugin fails with NoSuchMethodError
Ben Cooksley commented on JENKINS-25405 Plugins depending on Analysis Core plugin fails with NoSuchMethodError For those looking for an interim solution, downgrading "Static Code Analysis Plug-ins" to 1.62 appears to allow normal functionality to be restored. Could the maintainers of plugins which know they'll be a dependent chain please co-ordinate releases in the future? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25423) OS X installer should let user choose the user that will own jenkins
Mark Callow commented on JENKINS-25423 OS X installer should let user choose the user that will own jenkins The only choice beyond the installer seemed to be, "Here's the .war file; get on with with." I failed to find any instructions for manual installation on OS X. Without the installer where do I find the run script called by launchd, the code to put in /etc/newsyslog.d and all the other files that appear in the ~jenkins/Home in addition to the .war 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] [core] (JENKINS-25426) Input field slides in Google Chrome
Dmitrijs Sahlovs created JENKINS-25426 Input field slides in Google Chrome Issue Type: Bug Assignee: Unassigned Attachments: jenkins_bug.png Components: core Created: 04/Nov/14 8:49 AM Description: Not sure if I need to report this here or on the plugin's page. I am using Promoted build plugin. When I type long enough text in description text field, approver text field slides right(see screenshot). Environment: Jenkins 1.576 on windows Promoted Builds Plugin 2.17 Google Chrome 35.0.1916.11 Project: Jenkins Priority: Minor Reporter: Dmitrijs Sahlovs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25427) Build Pipleline Plugin no longer allows starting build with parameters
Johan Haleby created JENKINS-25427 Build Pipleline Plugin no longer allows starting build with parameters Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 04/Nov/14 8:51 AM Description: I just upgraded from 1.4.3 to 1.4.4 and now it seems like I no longer have to option to start the build pipeline (first job) with parameters which worked in the previous version. In version 1.4.3 when I pressed the "build now" button a modal window appeared where I could select my parameters for the first job. Now it just builds and automatically selects the pre-defined parameter values. For us this is critical since the initial job allows the user to select version numbers to download from git branches that are later packaged to a release. Project: Jenkins Priority: Critical Reporter: Johan Haleby This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25427) Build Pipleline Plugin no longer allows starting build with parameters
Johan Haleby updated JENKINS-25427 Build Pipleline Plugin no longer allows starting build with parameters Change By: Johan Haleby (04/Nov/14 8:52 AM) Environment: BuildPipelinePluginv1.4.4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-25425) Wrong link in Test Result column in custom view
Daniel Beck resolved JENKINS-25425 as Duplicate Wrong link in Test Result column in custom view Duplicates JENKINS-23583. Please search before filing a bug. Change By: Daniel Beck (04/Nov/14 8:54 AM) 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] [core] (JENKINS-25424) Exception when editing nodes
Daniel Beck commented on JENKINS-25424 Exception when editing nodes Is that the entire stack trace? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25423) OS X installer should let user choose the user that will own jenkins
Daniel Beck commented on JENKINS-25423 OS X installer should let user choose the user that will own jenkins https://github.com/jenkinsci/jenkins/tree/master/osx This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25426) Input field slides in Google Chrome
Daniel Beck commented on JENKINS-25426 Input field slides in Google Chrome Is that the only form where that happens? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-collector-plugin] (JENKINS-25425) Wrong link in Test Result column in custom view
Daniel Beck commented on JENKINS-25425 Wrong link in Test Result column in custom view Also, there's a reason we default to 'Minor', and it's not to make you perform an additional action. It's because most reported issues, including this one, really are minor. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-25405) Plugins depending on Analysis Core plugin fails with NoSuchMethodError
Daniel Beck commented on JENKINS-25405 Plugins depending on Analysis Core plugin fails with NoSuchMethodError It's the same author. It's just a simple mistake to make, because the change is compatible if it's in the same compile unit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25416) text parameter with newlines causing the default goal run
Thomas Wabner commented on JENKINS-25416 text parameter with newlines causing the default goal run Yes, I have tried with ant ... more or less the same result: testwebapp_svn_commit $ cmd.exe /C '"D:\applications\prg\jenkinsSlave1\tools\hudson.tasks.Ant_AntInstallation\ant-1.9.3\bin\ant.bat -Ddeployment_reason=a b c -Dpart_svn_url=trunk/devopts/testprojects clean exit %%ERRORLEVEL%%"' Buildfile: D:\applications\prg\jenkinsSlave1\workspace\test-webapp\testwebapp_svn_commit\build.xml test-offline: get-deps: the default goal is "package", but the goal configured is "clean" (which never tries to get the dependencies). With a one-liner it works. I have set for the parameter "deployment_reason" the content a b c I'm afraid that someone (the user) can also inject other commands into the command shell call and in the worst case hack or destroy the build agent (I have not started to check this ... but the escaping thing looks like a possible target) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25416) text parameter with newlines causing the default goal run
Daniel Beck updated JENKINS-25416 text parameter with newlines causing the default goal run Probably an issue with the Windows command line functions in core, so reassigning. Reducing priority as the obvious workaround is not using text parameters. Change By: Daniel Beck (04/Nov/14 9:05 AM) Priority: Major Minor Labels: buildjenkinsmaven3 parameter Component/s: core Component/s: maven-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-25424) Exception when editing nodes
Andreas Holzmann commented on JENKINS-25424 Exception when editing nodes The complete stacktrace is this: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.588.jar!/lib/form/descriptorList.jelly:78:49: j:forEach class hudson.plugins.xvnc.DisplayAllocator$Property is missing its descriptor at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) 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
[JIRA] [core] (JENKINS-25426) Input field slides in Google Chrome
Dmitrijs Sahlovs commented on JENKINS-25426 Input field slides in Google Chrome I have checked another parameters and find out that "Text parameter" form got same problem. Others seems to be ok. Also same problem persists in Internet Explorer 9. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25422) OS X installer creates local jenkins user even when network jenkins user exists
Mark Callow commented on JENKINS-25422 OS X installer creates local jenkins user even when network jenkins user exists Thanks for the feedback. The dscl command used at L13 will find only local users. I have never used dscl before so I can't say how to find networked users but I expect there is a way. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25426) Input field slides in Google Chrome
Dmitrijs Sahlovs updated JENKINS-25426 Input field slides in Google Chrome Change By: Dmitrijs Sahlovs (04/Nov/14 9:12 AM) Environment: Jenkins1.576onwindowsPromotedBuildsPlugin2.17GoogleChrome35.0.1916.11 /InternetExplorer9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [teamconcert-plugin] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
James Clark commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source Hi Heather, Had another hanging build today. Here is the Jenkins console output: Started by user anonymous Building on master in workspace /ccbdata/build/TRUNKP RTC : checkout... RTC : Build initiated by request from RTC RTC Checkout : Source control setup RTC Checkout : Fetching files to fetch destination "/ccbdata/build/TRUNKP/src" ... It got stuck there and just had the loading symbol. Thanks, James This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-25115) Recognize failures indicated by JUnit test result file
Thomas De Schampheleire commented on JENKINS-25115 Recognize failures indicated by JUnit test result file @Jan Feindt: I don't fully understand your use case. The code I proposed simply takes any failing test build and treats it as a failure cause using the name of the failing build, and showing the stacktrace. How would the regexp feature fit into this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-25428) Pending Gerrit Job details overlay the whole jenkins screen
Doron Shai created JENKINS-25428 Pending Gerrit Job details overlay the whole jenkins screen Issue Type: Bug Assignee: rsandell Attachments: GERRIT.jpg Components: gerrit-trigger-plugin Created: 04/Nov/14 10:07 AM Description: When there are pending Jobs with Gerrit event Listener the Gerrit Job details of the pending build overlay the whole jenkins screen in a way that is really disturbing. Environment: Jenkins ver. 1.588 Gerrit 2.11.1 Linux RHEL 6.5 Project: Jenkins Priority: Critical Reporter: Doron Shai This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24133) GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL
valentino miazzo commented on JENKINS-24133 GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL Jenkins ver. 1.580.1 Git Plugin 2.2.7 Bitbucket Plugin 1.0 The hook was JENKINS_URL/bitbucket-hook/ I noticed that GIT_BRANCH was broken (detached) even in builds (jobs) not configured with "Build when a change is pushed to BitBucket" but just SCM polling. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24948) Git/Gerrit environment Variables are not available in Maven projects
Doron Shai resolved JENKINS-24948 as Fixed Git/Gerrit environment Variables are not available in Maven projects Change By: Doron Shai (04/Nov/14 10:10 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-25390) New design breaks build history layout
Thorsten Meinl commented on JENKINS-25390 New design breaks build history layout This also affects a few others parts of the GUI, e.g. the JUnit results page or the build processor panel on the front page. In some cases the layout gets better if you make the browser windows smaller. Should I open separate issues for each of them? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-24377) Create Tag (Tag this build) Not working
Rasmus Pedersen commented on JENKINS-24377 Create Tag (Tag this build) Not working I'm seeing the same bug using Jenkins 1.588 with the Subversion Plug-in 2.4.4 on one of our servers. We have another server running the same versions but here tagging works. I can't figure out what the difference is between the two though - suggestions on what to look for? It's hard to figure out what exactly is wrong since there's no error message. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-25115) Recognize failures indicated by JUnit test result file
Jan Feindt commented on JENKINS-25115 Recognize failures indicated by JUnit test result file This is my use case: some integration tests test business logic where registry keys are used. Sometimes there are problems accessing the registry: Caused by: java.util.prefs.BackingStoreException: Could not open windowsregistry node Software\JavaSoft\Prefs at root 0x8001. This environment problem should be detected and displayed with an description different from other failing tests. The regexp in the given example: .Could not open windowsregistry 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] [build-failure-analyzer-plugin] (JENKINS-25115) Recognize failures indicated by JUnit test result file
Jan Feindt edited a comment on JENKINS-25115 Recognize failures indicated by JUnit test result file This is my use case: some integration tests test business logic where registry keys are used. Sometimes there are problems accessing the registry: Caused by: java.util.prefs.BackingStoreException: Could not open windowsregistry node Software\JavaSoft\Prefs at root 0x8001. This environment problem should be detected and displayed with an description different from other failing tests. The regexp in the given example: .Could not open windowsregistry 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] [analysis-core-plugin] (JENKINS-25405) Plugins depending on Analysis Core plugin fails with NoSuchMethodError
valentino miazzo edited a comment on JENKINS-25405 Plugins depending on Analysis Core plugin fails with NoSuchMethodError I fixed the issue by: Analysis Collector Plugin 1.41 -- 1.38 FindBugs Plugin 4.57 -- 4.56 PMD Plugin 3.39 -- 3.38 Static Code Analysis Plug-ins 1.64 -- 1.62 and then restarting Jenkins Jenkins ver. 1.580.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-25405) Plugins depending on Analysis Core plugin fails with NoSuchMethodError
valentino miazzo commented on JENKINS-25405 Plugins depending on Analysis Core plugin fails with NoSuchMethodError I fixed the issue by: Analysis Collector Plugin 1.41 -- 1.38 FindBugs Plugin 4.57 -- 4.56 PMD Plugin 3.39 -- 3.38 Static Code Analysis Plug-ins 1.64 -- 1.62 and then restarting 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] [jenkins-tracker] (JENKINS-17714) Add support to hide some specific job to users other than administrator
Karthick GRK resolved JENKINS-17714 as Not A Defect Add support to hide some specific job to users other than administrator Change By: Karthick GRK (04/Nov/14 10:57 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-17714) Add support to hide some specific job to users other than administrator
Karthick GRK commented on JENKINS-17714 Add support to hide some specific job to users other than administrator I have made it by using Project based authentication. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [active-directory-plugin] (JENKINS-13940) I'm trying to authenticate the Jenkins command line (CLI) and the system returns an error message (user authentication with AD), but the GUI works.
Dmitrijs Sahlovs commented on JENKINS-13940 Im trying to authenticate the Jenkins command line (CLI) and the system returns an error message (user authentication with AD), but the GUI works. If there are no quick workaround for this, could you please advice me if there is a possibility to run jenkins-cli automatically via passphrase protected ssh-key(Running script, providing password for key-file as a parameter). For now I can see, that the only way I can see how to use passphrase-protected keys is to type password by hands. Can this be automated? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25429) Build process not completed after the successful post build actions
Karthick GRK created JENKINS-25429 Build process not completed after the successful post build actions Issue Type: Bug Assignee: Unassigned Attachments: BuildHistory.JPG, console.JPG, homepage.JPG Components: core Created: 04/Nov/14 11:05 AM Description: I have a issue with Jenkins after done the successful post build actions. If my build fails the mail was sent successfully by Email extension plugin(last post build action I do in the job). After sending the email the job does not get end. It keep on loading in the home page and console log. But it ends in Build History of that specific job. I have attached screenshot of above three points. Environment: OS : Windows Jenkins version : Jenkins ver. 1.543 Email Extension plugin : 2.28 Project: Jenkins Labels: jenkins plugin email build build-action Priority: Blocker Reporter: Karthick GRK This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25416) text parameter with newlines causing the default goal run
Thomas Wabner commented on JENKINS-25416 text parameter with newlines causing the default goal run one additional note about the maven project: If the job is a maven project and you use such text parameter, also all pre- and post steps will fail (if they invoke for example a maven or ant tool). In such case you can "unset" the parameter with the env-inject plugin and remember it into another variable ... this variable will then not added as a parameter to the job ... but this is still very hackish. So the problem exists also for maven jobs with pre- or post-steps. I do not know, if it is a good idea to reduce the priority, because of the possibility to "destroy" the Jenkins slave with a unchecked parameter ... but I do not know enough about the JIRA rules for this project. Possible more investigation about the consequences should be made, to decide about the priority. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25429) Build process not completed after the successful post build actions
Daniel Beck resolved JENKINS-25429 as Not A Defect Build process not completed after the successful post build actions Not a bug: There's a phase after the build is considered finished while listeners are notified etc. You'll probably see what's going on on the /threadDump page. Change By: Daniel Beck (04/Nov/14 11:11 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25416) text parameter with newlines causing the default goal run
Daniel Beck updated JENKINS-25416 text parameter with newlines causing the default goal run You make a good point. Not enough to be considered a security issue IMO, but can still have very weird consequences. Change By: Daniel Beck (04/Nov/14 11:13 AM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-25115) Recognize failures indicated by JUnit test result file
Thomas De Schampheleire commented on JENKINS-25115 Recognize failures indicated by JUnit test result file Thanks, I understand now. However, in contrast with the currently proposed implementation, this does require some explicitly added entries in the known failure causes database. So in this case, the comments given by Tomas in the second comment (#comment-214614) do apply. I think such feature could co-exist with the current more simple implementation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25429) Build process not completed after the successful post build actions
Karthick GRK commented on JENKINS-25429 Build process not completed after the successful post build actions Then why does it keep on in building state in the home page for more than a day? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25429) Build process not completed after the successful post build actions
Daniel Beck commented on JENKINS-25429 Build process not completed after the successful post build actions That is unusual (and would have warranted mentioning in the original report). As it is, your report does not mention anything out of the ordinary. Again, /threadDump will help you determine what's going on. Try to find the thread for the build in question, and post it here for evaluation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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
Florian Hug commented on JENKINS-25144 Basic Authentication in combination with Session is broken For us this is a blocker since we are using the RTC Jazz (Ration Team Concert) plugin to trigger builds directly via the version control system. Since we have to use authentication (company policy) the version control system authenticates against Jenkins (using basic auth) and starts the build using its individual parameters. Since basic auth is broken, no build can be triggered via the version control system and this LTS version is completely useless for us. We would really appreciate a quick fix within Jenkins LTS. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25430) Clicking on console icon doesn't work
Johan Haleby created JENKINS-25430 Clicking on console icon doesnt work Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 04/Nov/14 12:14 PM Description: When running the build pipeline and clicking the "console" icon the modal window only shows (in Chrome) "Unable to resolve the server's DNS address." The problem is that clicking on the "console" icon tries to load the following address which obviously doesn't work: http://job/JobName/71/console Environment: Build Pipeline v1.4.4 Project: Jenkins Labels: plugin Priority: Major Reporter: Johan Haleby This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-25405) Plugins depending on Analysis Core plugin fails with NoSuchMethodError
Antoine Lorence commented on JENKINS-25405 Plugins depending on Analysis Core plugin fails with NoSuchMethodError Same for us, with Jenkins 1.580.1 LTS We resolved this issue by downgrading Static Code Analysis Plug-ins to 1.62 version In the plugins directory, delete analysis-core.jpi and analysis-core/ folder. Rename analysis-core.bak to analysis-core.jpi and restart 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-25431) Polling with include/exlude regions doesn't trigger builds
Dieter De Meyer created JENKINS-25431 Polling with include/exlude regions doesnt trigger builds Issue Type: Bug Assignee: Unassigned Attachments: git_polling.log Components: core Created: 04/Nov/14 12:37 PM Description: Polling private Github repositories doesn't seem to work anymore. We started with version 1.581 and it worked for a while, but then it just stopped. Then we upgraded to version 1.588. We use include and exclude regions but this doesn't seem to work anymore. Git polling log can be found in attachment. Environment: Jenkins v1.588 Git client plugin v1.11.0 Git plugin v2.2.7 Github API plugin v1.59 Github plugin v1.9.1 Project: Jenkins Priority: Critical Reporter: Dieter De Meyer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-25405) Plugins depending on Analysis Core plugin fails with NoSuchMethodError
Antoine Lorence edited a comment on JENKINS-25405 Plugins depending on Analysis Core plugin fails with NoSuchMethodError Same for us, with Jenkins 1.580.1 LTS, resolved by downgrading Static Code Analysis Plug-ins to 1.62 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-25405) Plugins depending on Analysis Core plugin fails with NoSuchMethodError
Antoine Lorence edited a comment on JENKINS-25405 Plugins depending on Analysis Core plugin fails with NoSuchMethodError Same for us, with Jenkins 1.580.1 LTS, resolved by downgrading Static Code Analysis Plug-ins to 1.62 (only this 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-25431) Polling with include/exlude regions doesn't trigger builds
Dieter De Meyer updated JENKINS-25431 Polling with include/exlude regions doesnt trigger builds Change By: Dieter De Meyer (04/Nov/14 12:40 PM) Description: PollingprivateGithubrepositoriesdoesntseemtoworkanymore.Westartedwithversion1.581anditworkedforawhile,butthenitjuststopped.Thenweupgradedtoversion1.588.Weuseincludeandexcluderegionsbutthisdoesntseemtoworkanymore.Gitpollinglogcanbefoundinattachment. Lookingatthepollinglog,someofthecommmitslistedshouldhavetriggeredabuildontherelatedjenkinsjob. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-25405) Plugins depending on Analysis Core plugin fails with NoSuchMethodError
Antoine Lorence edited a comment on JENKINS-25405 Plugins depending on Analysis Core plugin fails with NoSuchMethodError Same for us, with Jenkins 1.580.1 LTS, resolved by downgrading Static Code Analysis Plug-ins to 1.62. Warning plugin was kept in 4.43 and everything is ok. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [scriptler-plugin] (JENKINS-15878) scriptler explicit classpath
panticz commented on JENKINS-15878 scriptler explicit classpath as workarround you can put your jar file to default java classpath dir: /usr/java/packages/lib/ext/ see: http://stackoverflow.com/questions/26614316/connector-j-mysql-driver-in-jenkins-script-console-scriptler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [teamconcert-plugin] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
Heather Fraser-Dube commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source Hi James Can you look at the RTC Build result for this build that was started in RTC. When you open the build result there are tabs of different pieces of info. Is there an Activities tab? Does the Activities tab have any entries. Specifically I am interested in one that says "Fetching files" and whether it was complete or not. Can you tell if the source code was all loaded or not? Was the stack trace showing it was stuck in the same place again? Were there other threads (or the other executor) running and were any of them running RTC or Plugin code? Did the build prior to this one finish normally or was it cancelled? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [teamconcert-plugin] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
Heather Fraser-Dube commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source I have raised : 336647: Personal builds can encounter deadlock when fetching source for this in jazz.net This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option
Morne Joubert commented on JENKINS-25341 Improve reconcile by using -m option Is there anything i can help to get this functionality or help test this. If can can help modify the code etc then i am willing to pitch in. Most of our proxies are far away from the main server , and as i understand it the reconcile puts a load on proxy and the main 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] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option
Paul Allen commented on JENKINS-25341 Improve reconcile by using -m option At the moment P4Java at the top level API does not support the -m flag. It is possible to drop down a level to the exec map functions. To make the change I would need to add server protection code (to check the P4D version). There is a chance I could make the change this week; it would be great if you could test the changes. If you want to have a go yourself I would be happy to help set you up with a dev environment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-24608) Test result link displays twice on matrix project page
Stephen Cavender edited a comment on JENKINS-24608 Test result link displays twice on matrix project page Experiencing the same issue, has a workaround been found? My projects have two Test Results links (both pointing to the same, correct location) and two Test Result Trend graphs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-24608) Test result link displays twice on matrix project page
Stephen Cavender commented on JENKINS-24608 Test result link displays twice on matrix project page Experiencing the same issue, has a workaround been found? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14752) SCM Polling / Max # of concurrent polling = 1 hangs github polling
Jason Kushmaul commented on JENKINS-14752 SCM Polling / Max # of concurrent polling = 1 hangs github polling Same issue here. I reproduced this using the latest versions and documented my steps with an empty repo. Jenkins master Linux, CentOS 6.5 Jenkins ver. 1.588 Git Plugin 2.2.7 Git client plugin 1.11.0 Jenkins slave Windows 8.1 Pro using jnlp installed as service. E:\Jenkins\workspace\TestNewGitBranchC:\git\cmd\git.exe --version git version 1.9.4.msysgit.2 java -version java version "1.7.0_71" Java(TM) SE Runtime Environment (build 1.7.0_71-b14) Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode) Setup a new empty repo on git hosting (gitlab in this case) Make public ssh://g...@builds.me.local/jk/testgitreponewbranch.git I can clone it using Jenkin's key on slave, as the user the service is running as. Setup a new Jenkins job to be built on windows slave. Restrict to windows node Set git repo to above url ssh://g...@builds.me.local/jk/testgitreponewbranch.git Set branches to build to /release/ Set poll SCM to */1 * * * * (so we don't have to wait) Save Check Git Polling I see (No changes) That's good, we haven't pushed anything to a release/* branch yet. Just wait. Next you'll see git polling log hanging: Started on Nov 4, 2014 9:21:00 AM Polling SCM changes on WINDOWS Using strategy: Default "C:\git\cmd\git.exe" rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repositories "C:\git\cmd\git.exe" config remote.origin.url ssh://g...@builds.me.local/jk/testgitreponewbranch.git # timeout=10 Fetching upstream changes from ssh://g...@builds.me.local/jk/testgitreponewbranch.git "C:\git\cmd\git.exe" --version # timeout=10 "C:\git\cmd\git.exe" fetch --tags --progress ssh://g...@builds.me.local/jk/testgitreponewbranch.git +refs/heads/*:refs/remotes/origin/* However, running that last command manually (from a command prompt) does not result in hang, it exits immediately. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-14752) SCM Polling / Max # of concurrent polling = 1 hangs github polling
Jason Kushmaul edited a comment on JENKINS-14752 SCM Polling / Max # of concurrent polling = 1 hangs github polling Same issue here. I reproduced this using the latest versions and documented my steps with an empty repo. Jenkins master Linux, CentOS 6.5 Jenkins ver. 1.588 Git Plugin 2.2.7 Git client plugin 1.11.0 Jenkins slave Windows 8.1 Pro using jnlp installed as service. E:\Jenkins\workspace\TestNewGitBranchC:\git\cmd\git.exe --version git version 1.9.4.msysgit.2 java -version java version "1.7.0_71" Java(TM) SE Runtime Environment (build 1.7.0_71-b14) Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode) Setup a new empty repo on git hosting (gitlab in this case) Make public ssh://g...@builds.me.local/jk/testgitreponewbranch.git I can clone it using Jenkin's key on slave, as the user the service is running as. Setup a new Jenkins job to be built on windows slave. Restrict to windows node Set git repo to above url ssh://g...@builds.me.local/jk/testgitreponewbranch.git Set branches to build to */release/* Set poll SCM to */1 * * * * (so we don't have to wait) Save Check Git Polling I see (No changes) That's good, we haven't pushed anything to a release/* branch yet. Just wait. Next you'll see git polling log hanging: Started on Nov 4, 2014 9:21:00 AM Polling SCM changes on WINDOWS Using strategy: Default "C:\git\cmd\git.exe" rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repositories "C:\git\cmd\git.exe" config remote.origin.url ssh://g...@builds.me.local/jk/testgitreponewbranch.git # timeout=10 Fetching upstream changes from ssh://g...@builds.me.local/jk/testgitreponewbranch.git "C:\git\cmd\git.exe" --version # timeout=10 "C:\git\cmd\git.exe" fetch --tags --progress ssh://g...@builds.me.local/jk/testgitreponewbranch.git +refs/heads/*:refs/remotes/origin/* However, running that last command manually (from a command prompt) does not result in hang, it exits immediately. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option
Morne Joubert commented on JENKINS-25341 Improve reconcile by using -m option Let me know when you have something to test and i can do this for you. BTW does the reconcile put load on proxy only or on the main server 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] [core] (JENKINS-14752) SCM Polling / Max # of concurrent polling = 1 hangs github polling
Jason Kushmaul edited a comment on JENKINS-14752 SCM Polling / Max # of concurrent polling = 1 hangs github polling Same issue here. I reproduced this using the latest versions and documented my steps with an empty repo. Jenkins master Linux, CentOS 6.5 Jenkins ver. 1.588 Git Plugin 2.2.7 Git client plugin 1.11.0 Jenkins slave Windows 8.1 Pro using jnlp installed as service. E:\Jenkins\workspace\TestNewGitBranchC:\git\cmd\git.exe --version git version 1.9.4.msysgit.2 java -version java version "1.7.0_71" Java(TM) SE Runtime Environment (build 1.7.0_71-b14) Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode) Setup a new empty repo on git hosting (gitlab in this case) Make public ssh://g...@builds.me.local/jk/testgitreponewbranch.git I can clone it using Jenkin's key on slave, as the user the service is running as. Setup a new Jenkins job to be built on windows slave. Restrict to windows node Set git repo to above url ssh://g...@builds.me.local/jk/testgitreponewbranch.git Set branches to build to */release/* Set poll SCM to */1 * * * * (so we don't have to wait) Save Check Git Polling I see (No changes) That's good, we haven't pushed anything to a release/* branch yet. Just wait. Next you'll see git polling log hanging: Started on Nov 4, 2014 9:21:00 AM Polling SCM changes on WINDOWS Using strategy: Default "C:\git\cmd\git.exe" rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repositories "C:\git\cmd\git.exe" config remote.origin.url ssh://g...@builds.me.local/jk/testgitreponewbranch.git # timeout=10 Fetching upstream changes from ssh://g...@builds.me.local/jk/testgitreponewbranch.git "C:\git\cmd\git.exe" --version # timeout=10 "C:\git\cmd\git.exe" fetch --tags --progress ssh://g...@builds.me.local/jk/testgitreponewbranch.git +refs/heads/*:refs/remotes/origin/* You can see the process never ending in taskmgr However, running that last command manually (from a command prompt) does not result in hang, it exits immediately. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25432) Multi-module maven projects disappeared from UI after restart
Dmitrijs Sahlovs created JENKINS-25432 Multi-module maven projects disappeared from UI after restart Issue Type: Bug Assignee: Unassigned Components: core Created: 04/Nov/14 3:03 PM Description: After jenkins restart we can not see multiple-module maven projects in web-UI. Jobs are present on disk and in jenkins config, but do not load. This issues affects only multiple-module maven projects, others works ok. Environment: Jenkins v 1.576(runs on weblogic) on windows Maven Project Plugin v2.5 Project: Jenkins Priority: Critical Reporter: Dmitrijs Sahlovs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-14752) SCM Polling / Max # of concurrent polling = 1 hangs github polling
Jason Kushmaul edited a comment on JENKINS-14752 SCM Polling / Max # of concurrent polling = 1 hangs github polling Same issue here. I reproduced this using the latest versions and documented my steps with an empty repo. Jenkins master Linux, CentOS 6.5 Jenkins ver. 1.588 Git Plugin 2.2.7 Git client plugin 1.11.0 Jenkins slave Windows 8.1 Pro using jnlp installed as service. E:\Jenkins\workspace\TestNewGitBranchC:\git\cmd\git.exe --version git version 1.9.4.msysgit.2 java -version java version "1.7.0_71" Java(TM) SE Runtime Environment (build 1.7.0_71-b14) Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode) Setup a new empty repo on git hosting (gitlab in this case) Make public ssh://g...@builds.me.local/jk/testgitreponewbranch.git I can clone it using Jenkin's key on slave, as the user the service is running as. Setup a new Jenkins job to be built on windows slave. Restrict to windows node Set git repo to above url ssh://g...@builds.me.local/jk/testgitreponewbranch.git Set branches to build to */release/* Set poll SCM to */1 * * * * (so we don't have to wait) Save Check Git Polling I see (No changes) That's good, we haven't pushed anything to a release/* branch yet. Just wait. Next you'll see git polling log hanging: Started on Nov 4, 2014 9:21:00 AM Polling SCM changes on WINDOWS Using strategy: Default "C:\git\cmd\git.exe" rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repositories "C:\git\cmd\git.exe" config remote.origin.url ssh://g...@builds.me.local/jk/testgitreponewbranch.git # timeout=10 Fetching upstream changes from ssh://g...@builds.me.local/jk/testgitreponewbranch.git "C:\git\cmd\git.exe" --version # timeout=10 "C:\git\cmd\git.exe" fetch --tags --progress ssh://g...@builds.me.local/jk/testgitreponewbranch.git +refs/heads/*:refs/remotes/origin/* You can see the process never ending in taskmgr However, running that last command manually (from a command prompt) does not result in hang, it exits immediately. I should add that I do not have any other git polling jobs enabled. I do not have any other jobs referencing this git repo. Initially I did not have a branch at all. I tried adding one and pushing it "release/1.0" so that the job had something to do. This had no effect, the "Fetching upstream changes" process above still hangs, with SSH being the bottom most child process in procexp This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-25405) Plugins depending on Analysis Core plugin fails with NoSuchMethodError
Ryan Pavlik commented on JENKINS-25405 Plugins depending on Analysis Core plugin fails with NoSuchMethodError Also occurs here: using LTS Jenkins ver. 1.580.1, static analysis collector 1.41, static analysis util 1.64, and warnings 4.43. (Apologies if this isn't the right way to provide info to the community) Doesn't always occur - seems to happen more if I've got a more complex combination of warning settings, have recently added or removed the analysis "publisher" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [teamconcert-plugin] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
James Clark commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source Hi Heather, I've attached a screenshot of the activities tab for the build result as viewed in RTC to the jazz.net work item that you posted. I unfortunately can't tell if all the source code was loaded as subsequent personal builds have been done which have re-used the workspace. The thread dump is no longer available for that build, however I did look at it and it was waiting for a lock at the same place. I can't say for this build in particular but generally, we have 2 executors running and they will both be RTC builds. Therefore it is likely that there was another build running at the same time that would have checked out source from RTC etc. The previous personal build before that had failed for a legitimate reason. If you're talking about a build for any job that was running at the same time as the one that hanged, I'm not sure what build that was as the timing info for the hanging build has been lost after killing the Jenkins process. Thanks, James This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-25405) Plugins depending on Analysis Core plugin fails with NoSuchMethodError
Ryan Pavlik edited a comment on JENKINS-25405 Plugins depending on Analysis Core plugin fails with NoSuchMethodError Also occurs here: using LTS Jenkins ver. 1.580.1, static analysis collector 1.41, static analysis util 1.64, and warnings 4.43. (Apologies if this isn't the right way to provide info to the community) Doesn't always seem to occur - seems to happen more if I've got a more complex combination of warning settings, have recently added or removed the analysis "publisher". In any case, downgrading the static analysis util to 1.62 worked around it for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-25405) Plugins depending on Analysis Core plugin fails with NoSuchMethodError
wbauer commented on JENKINS-25405 Plugins depending on Analysis Core plugin fails with NoSuchMethodError Same issue here, Jenkins 1.588, analysis-core 1.64. Rolling back analysis-core to 1.62 made it work again. Looks like the return type of method hudson.plugins.analysis.core.ParserResult.addAnnotations has changed, which breaks the depending plugins calling that method. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option
Paul Allen commented on JENKINS-25341 Improve reconcile by using -m option Reconcile should only put load on a Master or Replica, not the Proxy. Reconcile is meta-data heavy and the Proxy only caches File Assets, not meta-data. When Reconcile has determined what needs to be updated the Sync command will hit the proxy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [scm-sync-configuration-plugin] (JENKINS-25434) SCM Sync Configuration Plugin Exception trying to set up initial sync
Stephen Tunney created JENKINS-25434 SCM Sync Configuration Plugin Exception trying to set up initial sync Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 04/Nov/14 4:35 PM Description: Trying to connect a fresh Jenkins install to a Git Server running on CentOS 7 x64. root@wat-build-head-git ~# git --version git version 1.8.3.1 User: wat-erp Repo: jenkins-erp IP: 10.17.19.26 Port:29418 Url: wat-erp@10.17.19.26:29418/jenkins-erp.git I can connect to the repo successfully with ssh:// in from from TortoiseGit Error while serving http://10.17.19.52:8080/plugin/scm-sync-configuration/reloadAllFilesFromScm java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) 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.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) 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.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
[JIRA] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option
Morne Joubert commented on JENKINS-25341 Improve reconcile by using -m option So if you have lots of builds using 1's of files and the Master is remote ( in another country) then the current behavior is going to be a problem correct ? I assume that is why the -m option was added to only do the delta with a reduced set of 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] [robot-plugin] (JENKINS-22546) Add REST API to robot framework plugin
Jose Sa commented on JENKINS-22546 Add REST API to robot framework plugin I've tested this plugin with version 1.5.0 and while the robot general information about the specific build is available (total number of tests, tests passed/failed, pecentage of tests passed), the information about the individual failed test cases is missing. Sample output using xml rest api: robotResult allFailedCase/ allFailedCase/ allFailedCase/ criticalFailed3/criticalFailed criticalPassed27/criticalPassed criticalTotal30/criticalTotal overallFailed3/overallFailed overallPassed27/overallPassed overallTotal30/overallTotal passPercentage90.0/passPercentage suite/ timeStamp20140523 15:24:06.067/timeStamp /robotResult I tried adding "?depth=2" or "?depth=3" to see if more information would be displayed on sub-levels but it returned the same output. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25432) Multi-module maven projects disappeared from UI after restart
Daniel Beck resolved JENKINS-25432 as Incomplete Multi-module maven projects disappeared from UI after restart Issue contains not nearly enough information to investigate further. Please read and follow https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue There's probably something logged in /log/all; possibly also something relevant in Old Data Monitor. This even reads like a request for assistance, those should be directed to jenkinsci-users mailing list, or #jenkins on Freenode. Change By: Daniel Beck (04/Nov/14 5:03 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] [analysis-core-plugin] (JENKINS-25405) Plugins depending on Analysis Core plugin fails with NoSuchMethodError
Oliver Gondža
updated JENKINS-25405
Plugins depending on Analysis Core plugin fails with NoSuchMethodError
Change By:
Oliver Gondža
(04/Nov/14 5:07 PM)
Description:
IvejustupgradedJenkinswithallplugins,andthewarningspluginthrowsanexception:{code}java.lang.NoSuchMethodError:hudson.plugins.analysis.core.ParserResult.addAnnotations(Ljava/util/Collection;)V athudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:405) athudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:321) athudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:319) athudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) athudson.model.Build$BuildExecution.post2(Build.java:183) athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) athudson.model.Run.execute(Run.java:1784) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:89) athudson.model.Executor.run(Executor.java:240){code}
h4.WorkaroundDowngradeanalysis-corepluginto1.62oranolderrelease.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [sauce-ondemand-plugin] (JENKINS-25435) Embedded Sauce Report does not show up when session ID present in xunit file
Oleg Nenashev moved JENKINS-25435 Embedded Sauce Report does not show up when session ID present in xunit file Change By: Oleg Nenashev (04/Nov/14 5:10 PM) Project: Infrastructure Jenkins Key: INFRA JENKINS - 194 25435 Workflow: jira JNJira Component/s: sauce-ondemand-plugin Component/s: ci This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [sauce-ondemand-plugin] (JENKINS-25435) Embedded Sauce Report does not show up when session ID present in xunit file
Oleg Nenashev commented on JENKINS-25435 Embedded Sauce Report does not show up when session ID present in xunit file I suspect it's an issue for a Jenkins plugin = project = JENKINS INFRA project targets Jenkins backend infrastructure. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [sauce-ondemand-plugin] (JENKINS-25435) Embedded Sauce Report does not show up when session ID present in xunit file
Oleg Nenashev assigned JENKINS-25435 to Kohsuke Kawaguchi Embedded Sauce Report does not show up when session ID present in xunit file Change By: Oleg Nenashev (04/Nov/14 5:10 PM) Assignee: R.TylerCroy KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-25436) Report failures by analyzing jenkins test report
Jan Feindt created JENKINS-25436 Report failures by analyzing jenkins test report Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 04/Nov/14 5:17 PM Description: Currently the only supported analyzing source is jenkins job console. In context of integration testing I would like to detect communication or configuration errors wich are not subjekt of the test itself. To check this i would like to use a multi-line regex for failure details, failure stacktrace, failure stderr and failure stdout. sample use case: some integration tests test business logic where registry keys are used. Sometimes there are problems accessing the registry: Caused by: java.util.prefs.BackingStoreException: Could not open windowsregistry node Software\JavaSoft\Prefs at root 0x8001. This environment problem should be detected and displayed with an description different from other failing tests. The regexp in the given example: .Could not open windowsregistry node. I started implementation (see https://github.com/jan-feindt/build-failure-analyzer-plugin/commit/3964ff86b2ca0bfc2ed45c8a5d28220a8385580b). I think I misused FoundIndication.matchingFile to change the URL-Part from consoleFull to testReport (see TestResultFailureReader line 142). This should be solved in any other way. The implementation requires a Post-build action to 'publish JUnit test report', because it depends on the Jenkins API on TestResult objects. Project: Jenkins Priority: Major Reporter: Jan Feindt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option
Paul Allen commented on JENKINS-25341 Improve reconcile by using -m option A Forwarding Replica would be an ideal solution; perfect for remote Jenkins operations, but it would make your proxy obsolete. The reconcile command in preview mode is read-only and would only hit the replica. Syncs would use the Forwarding Replica for meta-data and assets, only the updates to the db.have table would be passed through to the Master. There are even newer technologies like Edge/Commit Servers if you like cutting/bleeding edge. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-25437) Report failures by analyzing jenkins test report
Jan Feindt created JENKINS-25437 Report failures by analyzing jenkins test report Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 04/Nov/14 5:33 PM Description: Currently the only supported analyzing source is jenkins job console. In context of integration testing I would like to detect communication or configuration errors wich are not subjekt of the test itself. To check this i would like to use a multi-line regex for failure details, failure stacktrace, failure stderr and failure stdout. sample use case: some integration tests test business logic where registry keys are used. Sometimes there are problems accessing the registry: Caused by: java.util.prefs.BackingStoreException: Could not open windowsregistry node Software\JavaSoft\Prefs at root 0x8001. This environment problem should be detected and displayed with an description different from other failing tests. The regexp in the given example: .Could not open windowsregistry node. I started implementation (see https://github.com/jan-feindt/build-failure-analyzer-plugin/commit/3964ff86b2ca0bfc2ed45c8a5d28220a8385580b). I think I misused FoundIndication.matchingFile to change the URL-Part from consoleFull to testReport (see TestResultFailureReader line 142). This should be solved in any other way. The implementation requires a Post-build action to 'publish JUnit test report', because it depends on the Jenkins API on TestResult objects. Project: Jenkins Priority: Major Reporter: Jan Feindt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-25437) Report failures by analyzing jenkins test report
Jan Feindt commented on JENKINS-25437 Report failures by analyzing jenkins test report see also https://issues.jenkins-ci.org/browse/JENKINS-25115 and my comments there. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-25115) Recognize failures indicated by JUnit test result file
Jan Feindt commented on JENKINS-25115 Recognize failures indicated by JUnit test result file opened https://issues.jenkins-ci.org/browse/JENKINS-25437 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-25438) JellyTagException Instead of Test Results
Curtis Salisbury created JENKINS-25438 JellyTagException Instead of Test Results Issue Type: Bug Assignee: Unassigned Components: jenkins-tracker, junit-plugin Created: 04/Nov/14 5:37 PM Description: Getting an error when attempting to view test results. The error is below: Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.588.jar!/lib/hudson/failed-test.jelly:30:58: st:include No page found '/lib/hudson/test/failed-test.jelly' for class hudson.tasks.junit.TestResult at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) 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
[JIRA] [core] (JENKINS-21618) wrong Load statistics: busy executors in minus
Alexis Morelle edited a comment on JENKINS-21618 wrong Load statistics: busy executors in minus Got the same in Jenkins ver. 1.565.2 Daniel's comment is relevant, seems to always come with a negative spike of available executors. nevermind... didn't see the PR. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21618) wrong Load statistics: busy executors in minus
Alexis Morelle commented on JENKINS-21618 wrong Load statistics: busy executors in minus Got the same in Jenkins ver. 1.565.2 Daniel's comment is relevant, seems to always come with a negative spike of available executors. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21618) wrong Load statistics: busy executors in minus
Alexis Morelle updated JENKINS-21618 wrong Load statistics: busy executors in minus Change By: Alexis Morelle (04/Nov/14 5:49 PM) Attachment: negative-busy-executors.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25438) JellyTagException Instead of Test Results
Daniel Beck updated JENKINS-25438 JellyTagException Instead of Test Results Shouldn't even happen as 1.588 bundles JUNit 1.2-beta-3. Make sure that plugin is installed in that version and enabled. Change By: Daniel Beck (04/Nov/14 5:56 PM) Labels: jenkins Component/s: core Component/s: jenkins-tracker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25438) JellyTagException Instead of Test Results
Oleg Nenashev commented on JENKINS-25438 JellyTagException Instead of Test Results @Curtis What junit-plugin version do you use? Probably, it has been caused by https://github.com/jenkinsci/jenkins/commit/12f5dec0edd09db797fab31bd9e68d8c5bac923c Related discussion: https://github.com/jenkinsci/jenkins/commit/12f5dec0edd09db797fab31bd9e68d8c5bac923c This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25438) JellyTagException Instead of Test Results
Daniel Beck commented on JENKINS-25438 JellyTagException Instead of Test Results If I'm right, there should be a message on the /manage page that says: This version of Jenkins comes with new versions of the following plugins that are currently pinned in the plugin manager. It is recommended to upgrade them to at least the version bundled with 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-18351) Fingerprinting seems to leak Files
SCM/JIRA link daemon commented on JENKINS-18351 Fingerprinting seems to leak Files Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/DirectoryBrowserSupport.java http://jenkins-ci.org/commit/jenkins/2ea0276e7b4ea9614961a530382320c49ab626a2 Log: CID-1205053 - Resource leak on fingerprint calculation in DirectoryBrowserSupport The issue is related to JENKINS-18351. Signed-off-by: Oleg Nenashev o.v.nenas...@gmail.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18351) Fingerprinting seems to leak Files
Jesse Glick commented on JENKINS-18351 Fingerprinting seems to leak Files https://github.com/jenkinsci/jenkins/pull/1434 may fix another issue here, not sure. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
