[JIRA] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Markus Wagner commented on JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. Same here, but I'm not sure if this also occurred with 1.588. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Jennifer Hofmeister edited a comment on JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. Thanks a lot! Actually, I upgraded Jenkins to 1.580 two days ago (because of the SVN trouble, I preferred to stick with the stable versions). And it seems that the problem is now "gone" ... or at least, in the state as described above, meaning it does occur but not recur, which seems heavenly after many many weeks of pain. Just for the record, I logged all outgoing Jenkins connections to SVN, namely svnkit-network and hudson.scm.CredentialsSVNAuthenticationProviderImpl, but I couldn't find anything unusual. Welp. Seems there is no explanation, but at least a solution! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [vsphere-cloud-plugin] (JENKINS-25380) Allow parameterizing vSphere host and credentials
Oleg Nenashev started work on JENKINS-25380 Allow parameterizing vSphere host and credentials Change By: Oleg Nenashev (13/Nov/14 8:44 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-25588) Integrate authentication options with Credentials plugin
Oleg Nenashev created JENKINS-25588 Integrate authentication options with Credentials plugin Issue Type: Improvement Assignee: Oleg Nenashev Components: vsphere-cloud-plugin Created: 13/Nov/14 8:49 AM Project: Jenkins Priority: Minor Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-25589) Add a hostname provider extension point to vSphere Cloud plugin
Oleg Nenashev created JENKINS-25589 Add a hostname provider extension point to vSphere Cloud plugin Issue Type: New Feature Assignee: Oleg Nenashev Components: vsphere-cloud-plugin Created: 13/Nov/14 8:52 AM Description: This option would be useful in order to avoid the hardcoding of parameters. Project: Jenkins Priority: Minor Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-25588) Integrate vSphere Cloud plugin with Credentials plugin (auth options)
Oleg Nenashev updated JENKINS-25588 Integrate vSphere Cloud plugin with Credentials plugin (auth options) Change By: Oleg Nenashev (13/Nov/14 8:53 AM) Summary: Integrate authenticationoptions vSphereCloudplugin withCredentialsplugin (authoptions) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [vsphere-cloud-plugin] (JENKINS-25588) Integrate vSphere Cloud plugin with Credentials plugin (auth options)
Oleg Nenashev commented on JENKINS-25588 Integrate vSphere Cloud plugin with Credentials plugin (auth options) This feature is required to avoid keeping credentials in Node/Cloud configuration files. In our company passwords have a limited lifetime, so it becomes a mess This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [vsphere-cloud-plugin] (JENKINS-25380) Allow parameterizing vSphere host and credentials
Oleg Nenashev commented on JENKINS-25380 Allow parameterizing vSphere host and credentials A straightforward approach does not make sense. Credentials - Integrate with Credentials plugin (JENKINS-25588) Hostname - Add a new extension point if it is really required (JENKINS-25589) JENKINS-25588 with a proper CredentialsProvider would be enough IMO This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [vsphere-cloud-plugin] (JENKINS-25380) Allow parameterizing vSphere host and credentials
Oleg Nenashev edited a comment on JENKINS-25380 Allow parameterizing vSphere host and credentials A straightforward approach does not make sense. I would propose the following: Credentials - Integrate with Credentials plugin (JENKINS-25588) Hostname - Add a new extension point if it is really required (JENKINS-25589) JENKINS-25588 with a proper CredentialsProvider would be enough IMO This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [android-emulator-plugin] (JENKINS-25229) Update of sdk and build-tools for android-21 fails
Carlo Bongiovanni commented on JENKINS-25229 Update of sdk and build-tools for android-21 fails For anybody interested, the right command should be /data/jenkins/tools/android-sdk/tools/android update sdk -u -t tool,platform-tool -a The -a at the end makes the update process working. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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 Tested 1.0.20, i can see the client spec has modtime set and that the files have their local sync times. I still need the "verbosity" feature JENKINS-25468 so i can actually see what is going on, and the JENKINS-24741 to see if it speeds up the reconcile but i can see the reconcile has the modtime set so i trust Perforce that things will be better than before. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [checkstyle-plugin] (JENKINS-25511) Checkstyle double-escapes content
Alexander Obuhovich commented on JENKINS-25511 Checkstyle double-escapes content Also the apos; is being used (the XML only thing) instead of #39; when outputing to JSON. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25490) Slave JLNP client stops working with Unable to launch the application when master is stopped
Henrik Skupin commented on JENKINS-25490 Slave JLNP client stops working with Unable to launch the application when master is stopped So I already tried the way via the terminal by connecting the slave via javaws, but the client dies the same way when the master gets shutdown. So this is not a workaround. And this only happens on Linux and OS X. I re-tested with Windows and I cannot observe this behavior. There the client re-connects successfully once the master is back online. I'm not that happy with the 'java' workaround given that it would require us to update all of our 70 machines, by downloading the slave.jar file first. Also not sure how often it was required to re-download it given updates to that file. I'm working on a puppet configuration for us but that is not ready yet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [artifactory-plugin] (JENKINS-25590) Artifactory plugin is not deploying when there is cobertura:cobertura goal
Wisen Tanasa created JENKINS-25590 Artifactory plugin is not deploying when there is cobertura:cobertura goal Issue Type: Bug Assignee: yossis Components: artifactory-plugin Created: 13/Nov/14 10:32 AM Description: Some of our projects are not deploying their artefacts when cobertura:cobertura goal exist in the maven build step. Current behaviour: INFO Cobertura Report generation was successful. INFO Artifactory Build Info Recorder: Saving Build Info to '/data/jenkins/jobs/myproject/workspace/target/build-info.json' JENKINS Archiving disabled Expectation: INFO Cobertura Report generation was successful. INFO Artifactory Build Info Recorder: Saving Build Info to '/data/jenkins-slaves/slave1/workspace/myproject/target/build-info.json' INFO Deploying artifact: http://myproject.artifactory:8061/artifactory/libs-snapshot-local/com/myproject/lib-parent/5.2-SNAPSHOT/lib-parent-5.2-SNAPSHOT.pom INFO Deploying artifact: http://myproject.artifactory:8061/artifactory/libs-snapshot-local/com/myproject/libs/depmgmt-parent/5.2-SNAPSHOT/depmgmt-parent-5.2-SNAPSHOT.pom INFO Deploying artifact: http://myproject.artifactory:8061/artifactory/libs-snapshot-local/com/myproject/libs/depmgmt/depmgmt-common/5.2-SNAPSHOT/depmgmt-common-5.2-SNAPSHOT.pom INFO Deploying artifact: http://myproject.artifactory:8061/artifactory/libs-snapshot-local/com/myproject/libs/depmgmt/depmgmt-shared/5.2-SNAPSHOT/depmgmt-shared-5.2-SNAPSHOT.pom INFO Artifactory Build Info Recorder: Deploying build info ... INFO Deploying build info to: http://myproject.artifactory:8061/artifactory/api/build INFO Build successfully deployed. Browse it in Artifactory under http://myproject.artifactory:8061/artifactory/webapp/builds/myproject/24/2014-11-13T02:25:37.171-0600/ JENKINS Archiving disabled Environment: Jenkins Version: 1.532.2 Artifactory Plugin Version: 2.2.4 Artifactory Version: 3.3.0.1 Project: Jenkins Priority: Major Reporter: Wisen Tanasa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [artifactory-plugin] (JENKINS-25590) Artifactory plugin is not deploying when there is cobertura:cobertura goal
Wisen Tanasa updated JENKINS-25590 Artifactory plugin is not deploying when there is cobertura:cobertura goal Change By: Wisen Tanasa (13/Nov/14 10:34 AM) Description: Someofourprojectsarenotdeployingtheirartefactswhencobertura:coberturagoalexistinthemavenbuildstep.IhaveenabledJenkinsloggertoorg.jfrogbutfoundnothinginteresting.Currentbehaviour (thisisfromthebuggyjob) :[INFO]CoberturaReportgenerationwassuccessful.[INFO]ArtifactoryBuildInfoRecorder:SavingBuildInfoto/data/jenkins/jobs/myproject/workspace/target/build-info.json[JENKINS]ArchivingdisabledExpectation (thisisfromotherjobsthathavecobertura : coberturagoalaswell): [INFO]CoberturaReportgenerationwassuccessful.[INFO]ArtifactoryBuildInfoRecorder:SavingBuildInfoto/data/jenkins-slaves/slave1/workspace/myproject/target/build-info.json[INFO]Deployingartifact:http://myproject.artifactory:8061/artifactory/libs-snapshot-local/com/myproject/lib-parent/5.2-SNAPSHOT/lib-parent-5.2-SNAPSHOT.pom[INFO]Deployingartifact:http://myproject.artifactory:8061/artifactory/libs-snapshot-local/com/myproject/libs/depmgmt-parent/5.2-SNAPSHOT/depmgmt-parent-5.2-SNAPSHOT.pom[INFO]Deployingartifact:http://myproject.artifactory:8061/artifactory/libs-snapshot-local/com/myproject/libs/depmgmt/depmgmt-common/5.2-SNAPSHOT/depmgmt-common-5.2-SNAPSHOT.pom[INFO]Deployingartifact:http://myproject.artifactory:8061/artifactory/libs-snapshot-local/com/myproject/libs/depmgmt/depmgmt-shared/5.2-SNAPSHOT/depmgmt-shared-5.2-SNAPSHOT.pom[INFO]ArtifactoryBuildInfoRecorder:Deployingbuildinfo...[INFO]Deployingbuildinfoto:http://myproject.artifactory:8061/artifactory/api/build[INFO]Buildsuccessfullydeployed.BrowseitinArtifactoryunderhttp://myproject.artifactory:8061/artifactory/webapp/builds/myproject/24/2014-11-13T02:25:37.171-0600/[JENKINS]Archivingdisabled This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [artifactory-plugin] (JENKINS-25590) Artifactory plugin is not deploying when there is cobertura:cobertura goal
Wisen Tanasa updated JENKINS-25590 Artifactory plugin is not deploying when there is cobertura:cobertura goal Change By: Wisen Tanasa (13/Nov/14 10:33 AM) Description: Someofourprojectsarenotdeployingtheirartefactswhencobertura:coberturagoalexistinthemavenbuildstep. IhaveenabledJenkinsloggertoorg.jfrogbutfoundnothinginteresting. Currentbehaviour:[INFO]CoberturaReportgenerationwassuccessful.[INFO]ArtifactoryBuildInfoRecorder:SavingBuildInfoto/data/jenkins/jobs/myproject/workspace/target/build-info.json[JENKINS]ArchivingdisabledExpectation:[INFO]CoberturaReportgenerationwassuccessful.[INFO]ArtifactoryBuildInfoRecorder:SavingBuildInfoto/data/jenkins-slaves/slave1/workspace/myproject/target/build-info.json[INFO]Deployingartifact:http://myproject.artifactory:8061/artifactory/libs-snapshot-local/com/myproject/lib-parent/5.2-SNAPSHOT/lib-parent-5.2-SNAPSHOT.pom[INFO]Deployingartifact:http://myproject.artifactory:8061/artifactory/libs-snapshot-local/com/myproject/libs/depmgmt-parent/5.2-SNAPSHOT/depmgmt-parent-5.2-SNAPSHOT.pom[INFO]Deployingartifact:http://myproject.artifactory:8061/artifactory/libs-snapshot-local/com/myproject/libs/depmgmt/depmgmt-common/5.2-SNAPSHOT/depmgmt-common-5.2-SNAPSHOT.pom[INFO]Deployingartifact:http://myproject.artifactory:8061/artifactory/libs-snapshot-local/com/myproject/libs/depmgmt/depmgmt-shared/5.2-SNAPSHOT/depmgmt-shared-5.2-SNAPSHOT.pom[INFO]ArtifactoryBuildInfoRecorder:Deployingbuildinfo...[INFO]Deployingbuildinfoto:http://myproject.artifactory:8061/artifactory/api/build[INFO]Buildsuccessfullydeployed.BrowseitinArtifactoryunderhttp://myproject.artifactory:8061/artifactory/webapp/builds/myproject/24/2014-11-13T02:25:37.171-0600/[JENKINS]Archivingdisabled This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-19775) Github plugin - Set build status on github commit - No result
Marius Gedminas commented on JENKINS-19775 Github plugin - Set build status on github commit - No result It would also be useful to know what permissions are needed for the GitHub plugin when creating the OAuth token. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-jira-issue-updater] (JENKINS-25591) jenkins is crashing
amit anand created JENKINS-25591 jenkins is crashing Issue Type: Bug Assignee: Unassigned Components: jenkins-jira-issue-updater Created: 13/Nov/14 11:20 AM Environment: Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/root/.hudson/war/WEB-INF/lib/jenkins-core-1.588.jar!/hudson/model/View/index.jelly:42:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/root/.hudson/war/WEB-INF/lib/jenkins-core-1.588.jar!/lib/hudson/projectView.jelly:67:24: d:invokeBody java.lang.NullPointerException 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:813) 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.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.marvelution.jenkins.plugins.jira.filter.OAuthServletFilter.doFilter(OAuthServletFilter.java:70) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.marvelution.jenkins.plugins.jira.filter.StreamsServletFilter.doFilter(StreamsServletFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.marvelution.jenkins.plugins.jira.filter.ApplinksServletFilter.doFilter(ApplinksServletFilter.java:91) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.marvelution.jenkins.plugins.jira.oauth.OAuthFilter.doFilter(OAuthFilter.java:77) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:197) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:171) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [other] (JENKINS-25592) Jenkins UserID's with \ in the name results in not loading of pages
Jan-Jaap Spijkerman created JENKINS-25592 Jenkins UserIDs with \ in the name results in not loading of pages Issue Type: Bug Assignee: Unassigned Components: other Created: 13/Nov/14 11:53 AM Description: We are using "Delegate to servlet container" as access control for Jenkins in combination with Waffle because the users use smartcards and not a username/password. When using the latest LST version os Jenkins (1.580.1) we are having issues that users get an the same UserID as the name "DOMAIN\Username". This results in not being able to edit the user and not being able to create views or projects since it will try to open an URL with a "\" in the name. In our current Jenkins environment (1.509.4) the "\" of the name is translated to a "_" in it's UserID and therefor it works fine. I've tried both upgrading our existing environment to 1.580.1 with the same plugin versions and installing a clean 1.509.4 environment, which both resulted in the same problemens as mentioned before. I could not find any solution for this on tje Jira board, so hopefully anyone has an idea how to solve this. Environment: Jenkins ver. 1.580.1 waffle-jna-1.7.jar waffle-tomcat8-1.7.jar Project: Jenkins Labels: jenkins Priority: Minor Reporter: Jan-Jaap Spijkerman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [groovy-plugin] (JENKINS-25392) Post Build Steps still running regardless of Pre Step Groovy Script failure
Omar Ahmad commented on JENKINS-25392 Post Build Steps still running regardless of Pre Step Groovy Script failure Hi, that sounds great. Did you manage to get round to confirming the result of this check? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [groovy-plugin] (JENKINS-25392) Post Build Steps still running regardless of Pre Step Groovy Script failure
vjuranek commented on JENKINS-25392 Post Build Steps still running regardless of Pre Step Groovy Script failure Sorry, not yet. Hopefully with get to it today evening or tomorrow. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-25521) How to fix 'stapler-class is deprecated' warning?
Alex Earl resolved JENKINS-25521 as Not A Defect How to fix stapler-class is deprecated warning? This is most likely because email-ext is built against an older version of Jenkins. I am not sure at what point they changed this, if it was after the next LTS I am going to be migrating the plugin to, the warnings will still be there. I don't consider this a bug. Change By: Alex Earl (13/Nov/14 12:26 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Shannon Kerr commented on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed @Del, Yes, you cannot set BUILD_ID for a slave setting. It is set by Jenkins on a per build basis. You'd either have to set it in the batch section of the job itself (we did this for our most frequently used builds) or if you call a batch script or some other script, you can put it 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] [email-ext-plugin] (JENKINS-23834) Add option to remove Email Template Testing links
Alex Earl resolved JENKINS-23834 as Fixed Add option to remove Email Template Testing links This should be fixed in 2.39. I revamped how the project actions were done so that it would do the correct checks. Change By: Alex Earl (13/Nov/14 12:30 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25490) Slave JLNP client stops working with Unable to launch the application when master is stopped
Henrik Skupin commented on JENKINS-25490 Slave JLNP client stops working with Unable to launch the application when master is stopped So I also tried to install jenkins as service via the JNLP connection window, but that failed on OS X. So it looks like we really have to use the 'java' command for now on both affected platforms. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-19691) Make the lifetime of queue items cache configurable
SCM/JIRA link daemon commented on JENKINS-19691 Make the lifetime of queue items cache configurable Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/Queue.java http://jenkins-ci.org/commit/jenkins/227b73e081d5063895ba1a7438a99a5989f275ae Log: FIXED JENKINS-19691 - Added the hudson.model.Queue.cacheRefreshPeriod option The option allows to manage the refresh period of the internal queue cache. Signed-off-by: Oleg Nenashev o.v.nenas...@gmail.com (cherry picked from commit 0d825984ff7460f988b0a272a33dc60acc30e415) (cherry picked from commit 05cb8b2ec6b7e7ca688cfbcf4711bb2d14950eff) Compare: https://github.com/jenkinsci/jenkins/compare/0e6f09c402e8^...227b73e081d5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
Alex Earl commented on JENKINS-25535 Exception if email trigger enabled but no recipient specified When you say no recipients, do you mean that there is nothing in the recipient list AND no groups (culprits, developers, etc) are selected? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [rqm-plugin] (JENKINS-25593) Integration with credentials (case 11026)
Mads Nielsen created JENKINS-25593 Integration with credentials (case 11026) Issue Type: Improvement Assignee: Praqma Support Components: rqm-plugin Created: 13/Nov/14 1:12 PM Project: Jenkins Priority: Major Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25552) Git Polling with keys fails for Windows master and OSX slave
Mark Waite commented on JENKINS-25552 Git Polling with keys fails for Windows master and OSX slave Nicolae Ghimbovschi the message ssh: command not found fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. indicates that the git program did not have its PATH correctly configured to find the ssh executable which it uses for authenticated access to the remote server. If that job was configured with "Force polling using workspace", then that means the machine on which the workspace exists does not have the ssh command in its PATH. You can check that by creating a job which runs on that same machine and reports the value of the PATH environment variable. You can also review the environment variables of the slave through the "nodes" panel in Jenkins (http://localhost:8080/computer/). Each node has a "System Information" link which shows a page of the various settings used as defaults on that node. Those are defaults, and can be overridden by jobs, but it may be worth checking that the defaults are what you expect for that computer and operating system. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25580) Git plugin polls incorrect branch
Mark Waite resolved JENKINS-25580 as Wont Fix Git plugin polls incorrect branch Thanks for your comments. Unfortunately, it can't be fixed without a significant risk of breaking compatibility with many of the existing users of the git plugin. That simplified syntax is used by many jobs in many locations and changing its behavior is likely to have many unintended side effects. That is why Alexander Link's changes to allow refs/heads syntax were used instead of altering the behavior of the existing syntax. The refs/heads syntax allows unambiguous specification of the branch name without altering the meaning of the existing simplified syntax. That is also why the description of the regex form of branch specification was added to the online help about the same time. The regex form of branch specification had been in the code for quite a while, without online help, when Alexander and I discovered it lurking there. Since it was in the code, we included it in the online help as another way of handling this condition. There are too many users of the git plugin using it in too many diverse and interesting ways for us to change so fundamental a behavior, even if the behavior seems flawed. Change By: Mark Waite (13/Nov/14 1:20 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25580) Git plugin polls incorrect branch
Mark Waite edited a comment on JENKINS-25580 Git plugin polls incorrect branch Thanks for your comments. Unfortunately, it can't be fixed without a significant risk of breaking compatibility with many of the existing users of the git plugin. That simplified syntax is used by many jobs in many locations and changing its behavior is likely to have many unintended side effects. That is why Alexander Link's changes to allow refs/heads syntax were used instead of altering the behavior of the existing syntax. The refs/heads syntax allows unambiguous specification of the branch name without altering the meaning of the existing simplified syntax. That is also why the description of the regex form of branch specification was added to the online help about the same time. The regex form of branch specification had been in the code for quite a while, without online help, when Alexander and I discovered it lurking there. Since it was in the code, we included it in the online help as another way of handling this condition. There are too many users of the git plugin using it in too many diverse and interesting ways for us to change so fundamental a behavior, even if the behavior seems flawed. For a good discussion of the challenges associated with the branches to build specification, refer to commit 1, commit 2, commit 3, commit 4, and commit 5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
Alex Earl commented on JENKINS-25535 Exception if email trigger enabled but no recipient specified I can't seem to replicate this issue by just having an empty recipient list AND/OR not have any recipients defined for the trigger. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [rqm-plugin] (JENKINS-25593) Integration with credentials (case 11026)
Mads Nielsen resolved JENKINS-25593 as Fixed Integration with credentials (case 11026) Change By: Mads Nielsen (13/Nov/14 1:30 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
Alex Earl resolved JENKINS-25535 as Duplicate Exception if email trigger enabled but no recipient specified Change By: Alex Earl (13/Nov/14 1:31 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25594) Tried to install latest war file and gt error and reverted to old war 1.572 and still get errors..
Justin Yesudasan created JENKINS-25594 Tried to install latest war file and gt error and reverted to old war 1.572 and still get errors.. Issue Type: Bug Assignee: Unassigned Attachments: catalina.out, config.xml Components: core Created: 13/Nov/14 1:34 PM Description: I dropped new war file started and it failed startup, reverted to old war and same error.. Please help as error on startup is series of plugin errors cannot find manifest.. Attaching log files.. Nov 13, 2014 8:05:11 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Inspecting plugin /srv/nfs/relmgt/hudson/home/plugins/javadoc.jpi java.io.IOException: Plugin installation failed. No manifest at /srv/nfs/relmgt/hudson/home/plugins/javadoc/META-INF/MANIFEST.MF Thanks for help Environment: apache-tomcat-6.0.20, linux, OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode), Linux cla3065.ccrt.us 2.6.18-371.9.1.el5 #1 SMP Tue Jun 10 17:36:16 CDT 2014 x86_64 x86_64 x86_64 GNU/Linux Project: Jenkins Priority: Blocker Reporter: Justin Yesudasan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25594) Tried to install latest war file and gt error and reverted to old war 1.572 and still get errors..
Justin Yesudasan commented on JENKINS-25594 Tried to install latest war file and gt error and reverted to old war 1.572 and still get errors.. Caused by: java.io.IOException: Unable to read /srv/nfs/relmgt/hudson/home/config.xml at hudson.XmlFile.unmarshal(XmlFile.java:165) at jenkins.model.Jenkins$17.run(Jenkins.java:2572) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:885) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: com.thoughtworks.xstream.converters.ConversionException: hudson.security.ProjectMatrixAuthorizationStrategy : hudson.security.ProjectMatrixAuthorizationStrategy Debugging information message : hudson.security.ProjectMatrixAuthorizationStrategy cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassException cause-message : hudson.security.ProjectMatrixAuthorizationStrategy class : hudson.model.Hudson required-type : hudson.model.Hudson converter-type : hudson.util.RobustReflectionConverter path: /hudson/authorizationStrategy line number : 11 version : not available --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189) at hudson.util.XStream2.unmarshal(XStream2.java:113) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173) at hudson.XmlFile.unmarshal(XmlFile.java:163) ... 9 more Caused by: com.thoughtworks.xstream.mapper.CannotResolveClassException: hudson.security.ProjectMatrixAuthorizationStrategy at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:55) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:74) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.SecurityMapper.realClass(SecurityMapper.java:71) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at
[JIRA] [cloudbees-folder-plugin] (JENKINS-25595) After copying a Folder, all jobs within it are disabled
Aritz Bastida created JENKINS-25595 After copying a Folder, all jobs within it are disabled Issue Type: Bug Assignee: Jesse Glick Attachments: copied_folder_page.png, job_page.png Components: cloudbees-folder-plugin Created: 13/Nov/14 1:56 PM Description: After copying a Folder, I notice that none of the jobs within it can be launched (see "copied_folder_page.png" snapshot). Notice that we have a Test1 job, but there is no "Build Now" button to launch it. As we can see in the snapshot "job_page.png", the project seems to be enabled (i.e. we still have a button to disable it), but, at the same time, the "Build Now" button in the left menu is gone. The only workaround for this is disabling the job and enabling it again. Environment: Jenkins 1.588 Project: Jenkins Labels: plugin folder Priority: Major Reporter: Aritz Bastida This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-25595) After copying a Folder, all jobs within it are disabled
Aritz Bastida updated JENKINS-25595 After copying a Folder, all jobs within it are disabled Change By: Aritz Bastida (13/Nov/14 1:58 PM) Environment: Jenkins1.588 cloudbees-folder-plugin4.7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25596) NPE during polling with matrix build
Nick Poole created JENKINS-25596 NPE during polling with matrix build Issue Type: Bug Assignee: Paul Allen Components: p4-plugin Created: 13/Nov/14 2:03 PM Description: Parent build fails with NPE when build is started by an SCM change deted by polling. Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on Win7x64 (ntx64) in workspace c:\jenkins\workspace\pallen-test FATAL: null java.lang.NullPointerException at org.jenkinsci.plugins.p4.workspace.Workspace.set(Workspace.java:104) at org.jenkinsci.plugins.p4.PerforceScm.setBuildLabel(PerforceScm.java:241) at org.jenkinsci.plugins.p4.PerforceScm.checkout(PerforceScm.java:202) at hudson.model.AbstractProject.checkout(AbstractProject.java:1259) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) at hudson.model.Run.execute(Run.java:1759) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:306) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43) Project: Jenkins Priority: Blocker Reporter: Nick Poole This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-25597) Move icon not shown correctly in some job types
Aritz Bastida created JENKINS-25597 Move icon not shown correctly in some job types Issue Type: Bug Assignee: Jesse Glick Attachments: move_icon_not_shown.png Components: cloudbees-folder-plugin Created: 13/Nov/14 2:07 PM Description: The "Move" icon from the cloudbees-folder-plugin is not shown correctly for some Jenkins job types, such as multi-configuration jobs or multi-module Maven2/3 jobs. Please see attached snapshot. Probably, the move icon is not applicable in these cases, as it is nonsensical to move a particular configuration or module to a different folder, and should be removed altogether... What do you think? Environment: Jenkins 1.588 Folder 4.7 Project: Jenkins Priority: Minor Reporter: Aritz Bastida This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25598) Cannot start pipeline when the first job is a parameterized build within a Folder
Aritz Bastida created JENKINS-25598 Cannot start pipeline when the first job is a parameterized build within a Folder Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 13/Nov/14 2:11 PM Description: If the first job in a pipeline is a parameterized build, and this job is located within a folder (cloudbees-folder-plugin), the job won't start. No dialog error is shown. Environment: Jenkins 1.588 Folder 4.7 Build-Pipeline-Plugin 1.4.3 Project: Jenkins Priority: Minor Reporter: Aritz Bastida This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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 The 15.1 reconcile improvements will be much better as we store the have sync time and use that for updates. Modtime has the downside of using the date/time of the file as it was submitted, which might be an earlier time than your last build and so fool your build system into not updating the object files (make/jam). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [disk-usage-plugin] (JENKINS-25599) NPE: failed to send event to listener of class hudson.plugins.disk_usage.DiskUsageItemListener
Verny Quartara Gutierrez created JENKINS-25599 NPE: failed to send event to listener of class hudson.plugins.disk_usage.DiskUsageItemListener Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage-plugin Created: 13/Nov/14 2:23 PM Description: I ofted read the following stack trance in my Jenkins log. Despite this, the plugin seems to work properly, correctly displaying disk usage. Nov 13, 2014 3:10:02 PM hudson.model.listeners.ItemListener$1 run WARNING: failed to send event to listener of class hudson.plugins.disk_usage.DiskUsageItemListener java.lang.NullPointerException at hudson.plugins.disk_usage.DiskUsageUtil.loadData(DiskUsageUtil.java:84) at hudson.plugins.disk_usage.DiskUsageUtil.addProperty(DiskUsageUtil.java:64) at hudson.plugins.disk_usage.DiskUsageItemListener.onUpdated(DiskUsageItemListener.java:40) at hudson.model.listeners.ItemListener$4.apply(ItemListener.java:201) at hudson.model.listeners.ItemListener$4.apply(ItemListener.java:199) at hudson.model.listeners.ItemListener$1.run(ItemListener.java:166) at hudson.security.ACL.impersonate(ACL.java:144) at hudson.model.listeners.ItemListener.forAll(ItemListener.java:174) at hudson.model.listeners.ItemListener.fireOnUpdated(ItemListener.java:199) at hudson.model.AbstractProject.makeDisabled(AbstractProject.java:706) at hudson.model.AbstractProject.enable(AbstractProject.java:725) at com.github.mjdetullio.jenkins.plugins.multibranch.FreeStyleMultiBranchProject._syncBranches(FreeStyleMultiBranchProject.java:1115) at com.github.mjdetullio.jenkins.plugins.multibranch.FreeStyleMultiBranchProject.syncBranches(FreeStyleMultiBranchProject.java:1020) at com.github.mjdetullio.jenkins.plugins.multibranch.SyncBranchesTrigger.run(SyncBranchesTrigger.java:98) at hudson.triggers.Trigger.checkTriggers(Trigger.java:266) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:214) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Environment: Jenkins v.1588 Project: Jenkins Priority: Minor Reporter: Verny Quartara Gutierrez This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-19728) Much needed dependency management between jobs
Kevin Phillips commented on JENKINS-19728 Much needed dependency management between jobs Presuming you do not want to manually code these dependencies, you need some kind of tool which can inspect your sources and figure them out. Correct. Unfortunately we haven't found a tool capable of doing this inspection / analysis automatically - at least not for C++ / Visual Studio projects. Thus we have little choice other than manually coding / recoding the dependencies in Jenkins. It is annoying and fragile, I know, but in the absence of any other reasonable alternative we have no other choice. The problem I have is that, even when I want to do this manual configuration myself I currently need to make use of at least a dozen different plugins to accomplish the task, and since each plugin is developed by different individuals they vary in quality and compatibility. On more than one occasion I've had to take extensive measures to work around compatibility issues between plugins where some don't work quite properly with others. My hope is that if this basic job-dependency management logic were incorporated into the core Jenkins architecture the results of these efforts would be more fruitful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-19728) Much needed dependency management between jobs
Kevin Phillips commented on JENKINS-19728 Much needed dependency management between jobs NOTE: If it would help move this initiative forward, I could provide some very specific examples of the kinds of problems / behaviors we'd be looking to avoid / achieve so as to help clarify the expectations of this (self-admittedly) vague improvement request. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-19775) Github plugin - Set build status on github commit - No result
Marius Gedminas commented on JENKINS-19775 Github plugin - Set build status on github commit - No result I figured this out, eventually: http://stackoverflow.com/a/26910986/110151 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25578) Internet Explorer Compatibility
Aaron Kalsnes updated JENKINS-25578 Internet Explorer Compatibility Change By: Aaron Kalsnes (13/Nov/14 3:03 PM) Issue Type: Improvement Bug This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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 so from Perforce point of view, which is the better option to use ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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 15.1 is not released yet, so '-m' is all I can use for the moment. Depending on your build system (if it depends on date/time of source files) then the balance is between the reconcile time without '-m' vs a clean build. If your build does not use the date/time of the source files then '-m' 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] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option
Morne Joubert commented on JENKINS-25341 Improve reconcile by using -m option We have a BUILD directory where all object and other generated files are stored. This directory gets removed as a pre-scm step. I want to pick the mode that will put the least amount of strain on the P4 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] [xvnc-plugin] (JENKINS-25424) Exception when editing nodes
Jay Berkenbilt reopened JENKINS-25424 Exception when editing nodes I don't think the fix was complete. After applying the fix and restarting, I am still seeing this behavior on slaves starting after they have run Xvnc. If you aren't seeing it, I will try to create a quick formula for reproducing it. We're running the latest LTS. Change By: Jay Berkenbilt (13/Nov/14 3:40 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [youtrack-plugin] (JENKINS-24333) No action for executing command from build step
Wolfgang Ziegler commented on JENKINS-24333 No action for executing command from build step Thanks, I tested the experiemental plugin. Having the YOUTRACK_CHANGES variables is great and it seems to generally work except for the option "find issues ids in text" as it still parses the wrong issue IDs for me. I tried it with the YOUTRACK_CHANGES variable as well as with customly entered text - it always parses the issue ID "XYZ" instead of "#XYZ-123". I tried it with DEV and ORD prefixes, but obviously the project shortnames do not matter - the number is missing while the prefix is parsed. E.g., it tried to post to the youtrack issue "DEV" and "ORD" what obviously fails. When I enter an issue ID in the search query, it's working as it should. I'm curious, is that YOUTRACK_CHANGES variable now available in oder build steps as well or just for those youtrack plugin related settings? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25596) NPE during polling with matrix build
SCM/JIRA link daemon commented on JENKINS-25596 NPE during polling with matrix build Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java http://jenkins-ci.org/commit/p4-plugin/e6f59ff55686a18006d994d609aeba0ecae1371d Log: Fix null formatTags in Workspace Fix null formatTags in Workspace, by loading label from the cloned workspace. JENKINS-25596 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-19728) Much needed dependency management between jobs
Kevin Phillips commented on JENKINS-19728 Much needed dependency management between jobs To get the ball rolling, here is an example of some use cases that are difficult if not impossible to achieve at the moment which I would hope would be solved by this improvement: "Part 1: Job Dependency" Suppose a project has a low level 'framework' module and a higher level 'application' module which depends on it. It stands to reason that after building the 'framework' module successfully we should run a build of the 'application' module automatically so as to incorporate those framework changes. In this situation the latter, which we'll refer to as "Job A" depends on the latter which we'll refer to as "Job F". In this situation the expected behavior would be as follows: Job F would only run when changes are made to Job F Job A would be run in either of the following scenarios: Job A has changes made to it Job F has changes to it and those changes have been rebuilt successfully If Job A is currently running and Job F is triggered through some other means it will block until Job A completes If Job F is currently running and Job A is triggered through some other means it will block until Job F completes If builds of both Job A and Job F are pending in a build queue Job F will be run before Job A even if they were triggered in the opposite order In this scenario, the first 2 bullet points are more-or-less built into the Jenkins core via 'triggers', with the exception of item 2.2. So far as I can tell there is no way to prevent dependent projects from building when their upstreams are broken - via plugins or otherwise. Items 3 and 4 are supported by the Jenkins core but for some reason they are disabled by default. IMO if Jenkins implemented correct dependency management these options would be enabled by default. Item 5 is achievable with a fair amount of work through the use of plugins and an assortment of 'tweaks' to the Jenkins configuration. "Part 2: Parallel Dependencies Now, lets extend our example to include a server module, which we'll refer to as "Job S". This module will again depend on Job F - the common framework - but will be completely independent to Job A - the application. So in this case this new job would need to exhibit the same behavior as described for "Job A" above, which has the following implications: When changes are made to Job A only Job A will be rebuilt - Job F and Job S will not When changes are made to Job S only Job S will be rebuilt - Job F and Job A will not When changes are made to Job F and those changes are built successfully, both Job A and Job S will be rebuilt to integrate the changes When Job F is building and either Job A or Job S (or both) get triggered through some other means, they will block until Job F has completed successfully Job A and Job S should be able to build in parallel If both Job A and Job S are queued for execution, the order of execution does not matter (ie: FIFO priority would seem appropriate to make the order more explicit) If Job A, Job S and Job F all have builds waiting in the queue, Job F should be scheduled to run before either of Job A or Job S regardless of the chronological order in which the builds were triggered. So again, support for the first 3 items is supported by Jenkins core. Item 4 is partially support, with the exception that there is no mechanism that prevents Job A and Job S from building through independent triggers when Job F has finished building unsuccessfully. Items 5 and 6 are inherently supported by the Jenkins core. Finally, item 7 is supported via plugins with some monkeying with the configurations and triggers a bit. "Part 3: Dreaded Diamond Dependency" Finally, lets extend our example to include a dreaded diamond dependency. Suppose now we add a forth job to our configuration which 'packages' the artifacts of all three jobs (ie: creates an installer for them). Let's call this Job I. In this situation Job I requires all other jobs to be built successfully for it to work correctly. This has the following implications: If Job I gets triggered through some means and any of the other jobs are currently running, it must block until their builds are complete If any of the other jobs are broken Job I should not be allowed to build (no files have been built so there is nothing to package) If Job F receives changes, after those changes have been successfully built Job A and Job S must be triggered
[JIRA] [core] (JENKINS-24895) An existing connection was forcibly closed by the remote host
Andy Waterson commented on JENKINS-24895 An existing connection was forcibly closed by the remote host Same problem here. Unfortunately, I have no control over when SEP updates are done. The end result is randomly disconnecting jobs make the build/test process unreliable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25596) NPE during polling with matrix build
Paul Allen closed JENKINS-25596 as Fixed NPE during polling with matrix build 1.0.21 Change By: Paul Allen (13/Nov/14 4:15 PM) Status: Open Closed 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-25594) Tried to install latest war file and gt error and reverted to old war 1.572 and still get errors..
Daniel Beck resolved JENKINS-25594 as Not A Defect Tried to install latest war file and gt error and reverted to old war 1.572 and still get errors.. Not a bug, as downgrading is not generally supported. For assistance in running newer versions, please ask on the jenkinsci-users mailing list, or on #jenkins on Freenode. Change By: Daniel Beck (13/Nov/14 4:17 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24895) An existing connection was forcibly closed by the remote host
Daniel Beck commented on JENKINS-24895 An existing connection was forcibly closed by the remote host Is anyone experiencing this problem without running a tool that forces disconnecting established network connections? Sharon? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-19728) Much needed dependency management between jobs
Jesse Glick commented on JENKINS-19728 Much needed dependency management between jobs even when I want to do this manual configuration myself I currently need to make use of at least a dozen different plugins to accomplish the task Not when using Workflow. One job with one Groovy script which can work however you like, with no additional plugins. In the case of your diamond dependency scenario, I think all that is really missing today is the aforementioned operator to skip a stage when there are no SCM changes in that area. If you do have dozens of dependencies, it would be convenient to have a library to implement this model based on a simple configuration DSL. I do not think anything like this will or should become part of “basic Jenkins infrastructure”. The dependency triggering logic built into Jenkins core is already far too complex. That is why we created Workflow—the existing system did not scale up to more sophisticated scenarios. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-10442) RestartNotSupportedException when trying to do safeRestart
Daniel Beck updated JENKINS-10442 RestartNotSupportedException when trying to do safeRestart Change By: Daniel Beck (13/Nov/14 4:21 PM) Component/s: safe-restart Component/s: saferestart-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-19728) Much needed dependency management between jobs
Kevin Phillips commented on JENKINS-19728 Much needed dependency management between jobs I just wanted to make one further clarification in response to Jesse's comment above. Correct me if I'm mistaken, but I think in your comment you may be confusing the concept of "code dependencies" or "build dependencies" with "operational dependencies". What I mean to say is that, while it is true that as developers we probably tend to model Jenkins' job dependencies on our code modules' dependencies, there is not always a 1:1 relationship in that mapping. Often times we'll need to have operations executed as part of the automation process that have nothing to do with compilation but are still required by business processes. For example, if the code for Module A depends on the code of Module B and we use two separate Jenkins jobs to compile each of these then it's pretty clear what the dependencies must be (ie: this is where make and other such tools come into play). However, suppose we have 3 "phases" of a build process: compile, test, package, each of which managed by a separate job. Who is to say how those three jobs should relate / depend on one another? Should packages be dependent on tests? That depends on the context and the policies that govern your release process. This, imo, is where tools like Jenkins really need to shine. Sure the code dependencies need to be taken into account, and granted most of my earlier examples tend to favor such examples, but they are by no means the only source of dependencies your system needs to model. Consequently, I don't think you can ever get away from having to manually model your release process in the tool of your choice, Jenkins or otherwise. At best you can extract parts of that model from tools and build scripts, but you'll never quite get everything you need from there - at least not when you work at scale. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Neal Storey commented on JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. I reverted back to 1.586 which is actually what I was on prior to the upgrade (typo above). Node is back online. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xshell-plugin] (JENKINS-25600) XShell does not kill running process if job is getting aborted
Henrik Skupin created JENKINS-25600 XShell does not kill running process if job is getting aborted Issue Type: Bug Assignee: Unassigned Components: xshell-plugin Created: 13/Nov/14 4:42 PM Description: As we have seen lately XShell is not able to kill a running process once it is running on the slave, and the user aborts the job on the master machine. Current result is that the job is marked as aborted on the master, but it is still running on the client. This totally breaks our testruns because Jenkins thinks the node is free again, and schedules the next job for this node. But given that by our definition only a single job can run on a node, it will fail. The Jenkins log shows the following when aborting a job: mozilla-aurora_update #2 aborted java.lang.InterruptedException: sleep interrupted at java.lang.Thread.sleep(Native Method) at hudson.plugins.xshell.XShellBuilder.perform(XShellBuilder.java:158) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585) at hudson.model.Run.execute(Run.java:1684) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Environment: Jenkins 1.580.1 with XShell 0.9 Project: Jenkins Priority: Critical Reporter: Henrik Skupin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25601) JDK9 with jigsaw file layer is not detected as valid JDK
Eric Barboni created JENKINS-25601 JDK9 with jigsaw file layer is not detected as valid JDK Issue Type: Bug Assignee: Unassigned Components: core Created: 13/Nov/14 4:45 PM Description: Hi, The new jigsaw jdk is not detected as valid jdk because tools.jar and dt.jar are removed from the lib path but are needed by jenkins for detection. file: hudson/model/JDK.java method: checkHomeDirectory Not sure how to make a nice validation for current and jigsaw jdk. As a workaround having void tools.jar and dt.jar allow jdk detection by jenkins. Environment: - fedora 20. jdk8_25 - build jigsaw jdk: build 1.9.0-ea-jigsaw-nightly-h1689-20141110-b38, mixed mode Project: Jenkins Priority: Minor Reporter: Eric Barboni This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-25597) Move icon not shown correctly in some job types
Jesse Glick started work on JENKINS-25597 Move icon not shown correctly in some job types Change By: Jesse Glick (13/Nov/14 4:49 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19728) Much needed dependency management between jobs
Kevin Phillips commented on JENKINS-19728 Much needed dependency management between jobs Not when using Workflow. One job with one Groovy script which can work however you like, with no additional plugins. This does sound promising. From what I understand this plugin isn't yet available on the Jenkins plugin 'store', correct? Do you have any thoughts as to when it will be "production ready"? I definitely would like to give it a try when it is deemed "stable". The biggest issue I'd have with it would be having to take the time to learn Groovy and the plugin and then to write a script to handle some of these seemingly trivial use cases, but it's one of those things where if there are no other options at our disposal then we may have no other choice. The other thing we'd need to test in-house as well is to make sure that adopting a new plugin such as this wouldn't have an adverse effect on the dozens of other plugins we're currently using. As I mentioned before, we have experienced numerous inter-relationship problems between plugins in the past. I do not think anything like this will or should become part of “basic Jenkins infrastructure”. Obviously I'm not familiar with the internals of the tool itself, nor am I a maintainer or even an active contributor to the project (yet), so obviously I can't speak to whether such features will be incorporated into the core. However, given the importance and benefits of supporting correct dependency management I think it is pretty clear that these features should be incorporated into the core. The architecture would need to model the concepts of dependencies from the bottom up in order for it to be robustly supported - across plugins, across configurations, etc. The dependency triggering logic built into Jenkins core is already far too complex. That is why we created Workflow—the existing system did not scale up to more sophisticated scenarios. I suspected this was the case. It sounds like some of that code needs to be refactored to compensate for the added complexity. I probably should say that I do understand that what I am proposing here would likely be invasive and would require a lot of work, but as a result I believe that doing so would be a game changer for Jenkins which would further encourage it's adoption in the corporate world where such things are of critical importance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-19728) Much needed dependency management between jobs
Kevin Phillips edited a comment on JENKINS-19728 Much needed dependency management between jobs Not when using Workflow. One job with one Groovy script which can work however you like, with no additional plugins. This does sound promising. From what I understand this plugin isn't yet available on the Jenkins plugin 'store', correct? Do you have any thoughts as to when it will be "production ready"? I definitely would like to give it a try when it is deemed "stable". The biggest issue I'd have with it would be having to take the time to learn Groovy and the plugin and then to write a script to handle some of these seemingly trivial use cases, but it's one of those things where if there are no other options at our disposal then we may have no other choice. The other thing we'd need to do is test in-house as well is to make sure that adopting a new plugin such as this wouldn't have an adverse effect on the dozens of other plugins we're currently using. As I mentioned before, we have experienced numerous inter-relationship problems between plugins in the past. I do not think anything like this will or should become part of “basic Jenkins infrastructure”. Obviously I'm not familiar with the internals of the tool itself, nor am I a maintainer or even an active contributor to the project (yet), so obviously I can't speak to whether such features will be incorporated into the core. However, given the importance and benefits of supporting correct dependency management I think it is pretty clear that these features should be incorporated into the core. The architecture would need to model the concepts of dependencies from the bottom up in order for it to be robustly supported - across plugins, across configurations, etc. The dependency triggering logic built into Jenkins core is already far too complex. That is why we created Workflow—the existing system did not scale up to more sophisticated scenarios. I suspected this was the case. It sounds like some of that code needs to be refactored to compensate for the added complexity. I probably should say that I do understand that what I am proposing here would likely be invasive and would require a lot of work, but as a result I believe that doing so would be a game changer for Jenkins which would further encourage it's adoption in the corporate world where such things are of critical importance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-19728) Much needed dependency management between jobs
Kevin Phillips edited a comment on JENKINS-19728 Much needed dependency management between jobs Not when using Workflow. One job with one Groovy script which can work however you like, with no additional plugins. This does sound promising. From what I understand this plugin isn't yet available on the Jenkins plugin 'store', correct? Do you have any thoughts as to when it will be "production ready"? I definitely would like to give it a try when it is deemed "stable". The biggest issue I'd have with it would be having to take the time to learn Groovy and the plugin and then to write a script to handle some of these seemingly trivial use cases, but it's one of those things where if there are no other options at our disposal then we may have no other choice. The other thing we'd need to do is test the plugin in-house to make sure that adopting a new plugin such as this wouldn't have an adverse effect on the dozens of other plugins we're currently using. As I mentioned before, we have experienced numerous inter-relationship problems between plugins in the past. I do not think anything like this will or should become part of “basic Jenkins infrastructure”. Obviously I'm not familiar with the internals of the tool itself, nor am I a maintainer or even an active contributor to the project (yet), so obviously I can't speak to whether such features will be incorporated into the core. However, given the importance and benefits of supporting correct dependency management I think it is pretty clear that these features should be incorporated into the core. The architecture would need to model the concepts of dependencies from the bottom up in order for it to be robustly supported - across plugins, across configurations, etc. The dependency triggering logic built into Jenkins core is already far too complex. That is why we created Workflow—the existing system did not scale up to more sophisticated scenarios. I suspected this was the case. It sounds like some of that code needs to be refactored to compensate for the added complexity. I probably should say that I do understand that what I am proposing here would likely be invasive and would require a lot of work, but as a result I believe that doing so would be a game changer for Jenkins which would further encourage it's adoption in the corporate world where such things are of critical importance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25584) Improve error outputs if IOException happens on the disk overflow
Oleg Nenashev updated JENKINS-25584 Improve error outputs if IOException happens on the disk overflow Not a bug in any case. I'm not sure if the proposed improvement can be implemented in general case. Any disk operation in Jenkins core or plugin may fail, hence it's hard to handle a specific disk overflow case everywhere. The current behavior in enough IMO Change By: Oleg Nenashev (13/Nov/14 4:59 PM) Summary: changedescriptorleadstoRuntimeException ImproveerroroutputsifIOExceptionhappensonthediskoverflow Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-19728) Much needed dependency management between jobs
Jesse Glick commented on JENKINS-19728 Much needed dependency management between jobs I don't think you can ever get away from having to manually model your release process in the tool of your choice, Jenkins or otherwise. At best you can extract parts of that model from tools and build scripts, but you'll never quite get everything you need from there Agreed, and I was not suggesting otherwise. Just saying that there are cases where you have a large number of modules with a completely consistent, homogeneous model—each has a static dependency list on other modules, and each accepts a predefined “build test” command which is considered a prerequisite for building downstream modules. For this scenario, it is helpful to have some kind of tool which either automatically scans for dependencies, or accepts a DSL with a manually managed yet concise description of dependencies, and implements the minimal build sequence (with topological sorting, or automatic parallelization, etc.). For example, if you are using Maven with a reactor build (one big repository with lots of submodules with SNAPSHOT dependencies), and can determine which modules have changes according to the file list in the changelog of the current build, you can pass that module list as --also-make-dependents B,K,P,Q --threads 2.0C and get an easy parallelized, minimal build. There are of course other scenarios where every dependency is idiosyncratic enough that you have to model the whole behavior from scratch. And there is often some kind of setup stage and/or final deployment stage that falls outside a fixed dependency model. Neither poses any problem for Workflow. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25582) Installing Jenkins service the slave cannot re-connect after first system restart
Oleg Nenashev updated JENKINS-25582 Installing Jenkins service the slave cannot re-connect after first system restart Change By: Oleg Nenashev (13/Nov/14 5:05 PM) Labels: servicewinsw This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25582) Installing Jenkins service the slave cannot re-connect after first system restart
Oleg Nenashev commented on JENKINS-25582 Installing Jenkins service the slave cannot re-connect after first system restart It happens due to TCP Timeout and PingThread on the master. Jenkins master consider a slave as connected if... There's no failed requests from master to slave PingThread has not failed with 4-minutes timeout (it's hardcoded now) In order to fix the issue, reconfigure the reconnect interval in Slave Service configuration. It will decrease the frequency of connection attempts. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xshell-plugin] (JENKINS-25600) XShell does not kill running process if job is getting aborted
Henrik Skupin commented on JENKINS-25600 XShell does not kill running process if job is getting aborted Could this have been caused by https://github.com/jenkinsci/xshell-plugin/pull/8? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-19728) Much needed dependency management between jobs
Kevin Phillips edited a comment on JENKINS-19728 Much needed dependency management between jobs Not when using Workflow. One job with one Groovy script which can work however you like, with no additional plugins. This does sound promising. From what I understand this plugin isn't yet available on the Jenkins plugin 'store', correct? Do you have any thoughts as to when it will be "production ready"? I definitely would like to give it a try when it is deemed "stable". The biggest issue I'd have with it would be having to take the time to learn Groovy and the plugin and then to write a script to handle some of these seemingly trivial use cases, but it's one of those things where if there are no other options at our disposal then we may have no other choice. The other thing we'd need to do is test the plugin in-house to make sure that adopting a new plugin such as this wouldn't have an adverse effect on the dozens of other plugins we're currently using. As I mentioned before, we have experienced numerous inter-relationship problems between plugins in the past. I do not think anything like this will or should become part of “basic Jenkins infrastructure”. Obviously I'm not familiar with the internals of the tool itself, nor am I a maintainer or even an active contributor to the project (yet), so obviously I can't speak to whether such features will be incorporated into the core. However, given the importance and benefits of supporting correct dependency management I think it is pretty clear that these features should be incorporated into the core. The architecture would need to model the concepts of dependencies from the bottom up in order for it to be robustly supported - across plugins, across configurations, etc. The dependency triggering logic built into Jenkins core is already far too complex. That is why we created Workflow—the existing system did not scale up to more sophisticated scenarios. I suspected this was the case. It sounds like some of that code needs to be refactored to compensate for the added complexity. I probably should say that I do understand that what I am proposing here would likely be invasive and would require a lot of work, but as a result I believe that doing so would be a game changer for Jenkins which would further encourage it's adoption in the corporate world where such things are of critical importance. For example, if the core architecture supported dependency management and these features were exposed on the Jenkins UI via easy to understand interfaces then even non-developers can get involved with the automated process management. Exposing this feature via a scripting environment, while very flexible and powerful I'm sure, does preclude / discourage non-developers from using it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xshell-plugin] (JENKINS-25600) XShell does not kill running process if job is getting aborted
Henrik Skupin commented on JENKINS-25600 XShell does not kill running process if job is getting aborted Oh, and this is indeed a regression between version 0.8 and 0.9. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19728) Much needed dependency management between jobs
Jesse Glick commented on JENKINS-19728 Much needed dependency management between jobs From what I understand this plugin isn't yet available on the Jenkins plugin 'store', correct? There are beta releases available on the experimental update center. Please see its project page for details, or use jenkinsci-dev for questions. Do you have any thoughts as to when it will be "production ready"? 1.0 is expected very soon, for what that’s worth. I cannot promise this would solve all of your requirements (even if and when a changelog operator is implemented), but it is the only plausible candidate, which is why Kohsuke I have been spending so much time on it. Your use cases are exactly in line with what we envisioned as the interesting problems to be solved—the things that just could not be done as separate jobs with triggers without losing your mind. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-25595) After copying a Folder, all jobs within it are disabled
Jesse Glick resolved JENKINS-25595 as Duplicate After copying a Folder, all jobs within it are disabled Change By: Jesse Glick (13/Nov/14 5:11 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19728) Much needed dependency management between jobs
Kevin Phillips commented on JENKINS-19728 Much needed dependency management between jobs Thanks for clarifying. Ironically, I have been reading a lot about Maven lately since our company does have a small Java development team that uses it, and I'm trying to evaluate whether any of those tools may be usable by our native development teams. So far it's not looking good. I do have to say that on some level I am, as a mainly native C++ developer, jealous at the tools available to Java developers, most notably Maven. They do provide a lot of features that are sadly missing or, at best, very difficult to find in native toolsets. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-19728) Much needed dependency management between jobs
Kevin Phillips commented on JENKINS-19728 Much needed dependency management between jobs the things that just could not be done as separate jobs with triggers without losing your mind. Very well put! Unfortunately I think I lost my mind on this stuff at least a year ago or more. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [lockable-resources-plugin] (JENKINS-25569) Lockable resource job stuck at default is still in the queue: Waiting for resources [my_resource]
Jonathan Strickland commented on JENKINS-25569 Lockable resource job stuck at default is still in the queue: Waiting for resources [my_resource] Found that the QueueTaskDispatcher is being called multiple times (LockableResourcesQueueTaskDispatcher) but is appears that there is no distinction in when its being called at different points in the queue. Appears since its being called multiple times and attempting to queue up resources each time that basically get stuck waiting for resources. See below: Nov 13, 2014 11:56:51 AM INFO hudson.WebAppMain$3 run Jenkins is fully up and running Nov 13, 2014 12:11:41 PM INFO org.jenkins.plugins.lockableresources.queue.LockableResourcesQueueTaskDispatcher canRun Full stack trace is in canRun: java.lang.Thread.getStackTrace(Thread.java:1568), org.jenkins.plugins.lockableresources.queue.LockableResourcesQueueTaskDispatcher.canRun(LockableResourcesQueueTaskDispatcher.java:41), hudson.model.Queue.isBuildBlocked(Queue.java:949), hudson.model.Queue.maintain(Queue.java:1018), hudson.model.Queue$1.call(Queue.java:316), hudson.model.Queue$1.call(Queue.java:313), jenkins.util.AtmostOneTaskExecutor$1.call(AtmostOneTaskExecutor.java:94), jenkins.util.AtmostOneTaskExecutor$1.call(AtmostOneTaskExecutor.java:84), java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334), java.util.concurrent.FutureTask.run(FutureTask.java:166), hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:104), java.lang.Thread.run(Thread.java:724) Nov 13, 2014 12:11:41 PM INFO org.jenkins.plugins.lockableresources.queue.LockableResourcesQueueTaskDispatcher canRun Reserve_Upgrade9k trying to reserve 1 of ASR9K Nov 13, 2014 12:11:41 PM INFO org.jenkins.plugins.lockableresources.queue.LockableResourcesQueueTaskDispatcher canRun PROJECT FULLNAME:Reserve_Upgrade9k NAME:Reserve_Upgrade9k Nov 13, 2014 12:11:41 PM INFO org.jenkins.plugins.lockableresources.LockableResourcesManager queue Selecting resources for queueItemId:1 queueItemProject:Reserve_Upgrade9k number:1 Nov 13, 2014 12:11:41 PM INFO org.jenkins.plugins.lockableresources.LockableResourcesManager queue Checking resource ASR9K with project name null with queueItemsId 0 Nov 13, 2014 12:11:41 PM INFO org.jenkins.plugins.lockableresources.LockableResourcesManager queue Validating rs ASR9K isReserved:false isLocked:false isQueue:false Nov 13, 2014 12:11:41 PM INFO org.jenkins.plugins.lockableresources.LockableResourcesManager queue Selected size is 1 Nov 13, 2014 12:11:41 PM INFO org.jenkins.plugins.lockableresources.queue.LockableResourcesQueueTaskDispatcher canRun Reserve_Upgrade9k reserved resources ASR9K Nov 13, 2014 12:11:41 PM INFO org.jenkins.plugins.lockableresources.LockableResourcesManager lock Entering lock resources Nov 13, 2014 12:11:41 PM INFO org.jenkins.plugins.lockableresources.LockableResourcesManager lock Full stack trace is: java.lang.Thread.getStackTrace(Thread.java:1568), org.jenkins.plugins.lockableresources.LockableResourcesManager.lock(LockableResourcesManager.java:157), org.jenkins.plugins.lockableresources.queue.LockRunListener.onStarted(LockRunListener.java:48), org.jenkins.plugins.lockableresources.queue.LockRunListener.onStarted(LockRunListener.java:28), hudson.model.listeners.RunListener.fireStarted(RunListener.java:213), hudson.model.Run.execute(Run.java:1755), hudson.matrix.MatrixBuild.run(MatrixBuild.java:306), hudson.model.ResourceController.execute(ResourceController.java:89), hudson.model.Executor.run(Executor.java:240), hudson.model.OneOffExecutor.run(OneOffExecutor.java:43) Nov 13, 2014 12:11:41 PM INFO org.jenkins.plugins.lockableresources.LockableResourcesManager lock Exiting lock resources with true Nov 13, 2014 12:11:41 PM INFO org.jenkins.plugins.lockableresources.queue.LockableResourcesQueueTaskDispatcher canRun Full stack trace is in canRun: java.lang.Thread.getStackTrace(Thread.java:1568), org.jenkins.plugins.lockableresources.queue.LockableResourcesQueueTaskDispatcher.canRun(LockableResourcesQueueTaskDispatcher.java:41), hudson.model.Queue.isBuildBlocked(Queue.java:949), hudson.model.Queue.maintain(Queue.java:1018), hudson.model.Queue$1.call(Queue.java:316), hudson.model.Queue$1.call(Queue.java:313), jenkins.util.AtmostOneTaskExecutor$1.call(AtmostOneTaskExecutor.java:94), jenkins.util.AtmostOneTaskExecutor$1.call(AtmostOneTaskExecutor.java:84), java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334),
[JIRA] [cloudbees-folder-plugin] (JENKINS-25595) After copying a Folder, all jobs within it are disabled
Daniel Beck commented on JENKINS-25595 After copying a Folder, all jobs within it are disabled Any job you copy is disabled (or rather, not buildable) by default. You usually don't recognize it because the form opens and you generally change things, and upon Saving the job becomes buildable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-25595) After copying a Folder, all jobs within it are disabled
Aritz Bastida commented on JENKINS-25595 After copying a Folder, all jobs within it are disabled Thanks! It was confusing to me, but I understand now that it has been implemented this way to prevent accidental runs... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25602) Testing connection to an SSL server fails with 'Connection Error.'
Matthew Douglass commented on JENKINS-25602 Testing connection to an SSL server fails with Connection Error. I have verified that the correct Trust parameter is set in the credentials for this connection. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25602) Testing connection to an SSL server fails with 'Connection Error.'
Matthew Douglass created JENKINS-25602 Testing connection to an SSL server fails with Connection Error. Issue Type: Bug Assignee: Rob Petti Components: perforce-plugin Created: 13/Nov/14 6:15 PM Description: The following messages appear in the Jenkins System Log: Nov 13, 2014 3:33:30 AM SEVERE org.jenkinsci.plugins.p4.client.ConnectionHelper connect P4: Unable to connect: com.perforce.p4java.exception.ConnectionException: The authenticity of '*** removed ***' can't be established, this may be your first attempt to connect to this Perforce server. The fingerprint for the public key sent to your client is *** removed *** To allow connection use the 'addTrust' method with the 'autoAccept' option. Environment: Jenkins 1.585 p4 1.0.20 Project: Jenkins Priority: Major Reporter: Matthew Douglass This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25602) Testing connection to an SSL server fails with 'Connection Error.'
Rob Petti updated JENKINS-25602 Testing connection to an SSL server fails with Connection Error. Filed under the wrong component. Change By: Rob Petti (13/Nov/14 6:21 PM) Component/s: p4-plugin Component/s: perforce-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] [p4-plugin] (JENKINS-25602) Testing connection to an SSL server fails with 'Connection Error.'
Rob Petti assigned JENKINS-25602 to Unassigned Testing connection to an SSL server fails with Connection Error. Change By: Rob Petti (13/Nov/14 6:21 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-25595) After copying a Folder, all jobs within it are disabled
Jesse Glick commented on JENKINS-25595 After copying a Folder, all jobs within it are disabled Specifically to prevent scheduled triggers from running until after you have verified that the new version of the job is actually right. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ghprb-plugin] (JENKINS-25603) PR's are stuck using old configuration values
Travis Johnson created JENKINS-25603 PRs are stuck using old configuration values Issue Type: Bug Assignee: Honza Brázdil Components: ghprb-plugin Created: 13/Nov/14 6:39 PM Description: it appears once a PR is created (and detected by ghprb) the current configuration values are copied into the PR object. As a result, changes in configuration (whitelist, admins, trigger commands, etc) are not reflected in existing PR's. Project: Jenkins Priority: Minor Reporter: Travis Johnson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ghprb-plugin] (JENKINS-25603) PR's are stuck using old configuration values
Travis Johnson updated JENKINS-25603 PRs are stuck using old configuration values Change By: Travis Johnson (13/Nov/14 6:40 PM) Environment: Jenkins:1.580.1ghprb-plugin:1.16-5OS:Ubuntu12.04.5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-3761) When login j_acegi_security_check return a 404 error
Oliver Gondža updated JENKINS-3761 When login j_acegi_security_check return a 404 error Change By: Oliver Gondža (13/Nov/14 6:44 PM) Component/s: matrix-auth-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] [active-directory-plugin] (JENKINS-3761) When login j_acegi_security_check return a 404 error
Oliver Gondža updated JENKINS-3761 When login j_acegi_security_check return a 404 error Change By: Oliver Gondža (13/Nov/14 6:44 PM) Component/s: matrix-project-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] [ghprb-plugin] (JENKINS-25603) PR's are stuck using old configuration values
Travis Johnson commented on JENKINS-25603 PRs are stuck using old configuration values I have a PR that I believe fixes this: https://github.com/jenkinsci/ghprb-plugin/pull/60/files (along with others). It warrants some of it's own tests, but that may take me a while as I'm not familiar with testing jenkins plugins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [checkstyle-plugin] (JENKINS-25511) Checkstyle double-escapes content
Ulli Hafner commented on JENKINS-25511 Checkstyle double-escapes content Seems that Java Checkstyle also escapes entities so it should be easy to get this right for both worlds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25594) Tried to install latest war file and gt error and reverted to old war 1.572 and still get errors..
Justin Yesudasan closed JENKINS-25594 as Not A Defect Tried to install latest war file and gt error and reverted to old war 1.572 and still get errors.. Change By: Justin Yesudasan (13/Nov/14 7:15 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25580) Git plugin polls incorrect branch
Nathan Gray commented on JENKINS-25580 Git plugin polls incorrect branch As somebody who has done way too much git scripting I can appreciate how tricky this stuff is, but the plugin is just plain doing the wrong thing. I've specified an unambiguous branch and it's randomly dropped part of the name. I've asked it to poll "origin/release/flow" and it's polling "flow". The "origin" part is correctly removed but what happened to "release"? Note that this is a regression from the last version of the plugin I used, where "origin/release/flow" did the right thing. I'm not asking for behavior to change, I'm asking for previously working branch names to work again. Looking at the code, normalizeBranchSpec is broken (and there's even a comment in the code saying so). Taking the last component of the branch name is going to be wrong a lot. I wonder if you're aware that git already provides branch normalization with "git rev-parse --symbolic-full-name": [nathangray@n8bookpro]% git rev-parse --symbolic-full-name release/flow refs/heads/release/flow [nathangray@n8bookpro]% git rev-parse --symbolic-full-name heads/release/flow refs/heads/release/flow [nathangray@n8bookpro]% git rev-parse --symbolic-full-name origin/release/flow refs/remotes/origin/release/flow [nathangray@n8bookpro]% git rev-parse --symbolic-full-name remotes/origin/release/flow refs/remotes/origin/release/flow Couldn't you use that instead of trying to do it yourself? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22486) API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception.
Steve Storey commented on JENKINS-22486 API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception. I've made some changes to add Maven 3.2 support specifically for the purposes of supporting multi-threaded builds there. Pull requests https://github.com/jenkinsci/maven-interceptors/pull/5 and https://github.com/jenkinsci/maven-plugin/pull/32 cover the functionality. For those happy to build + install their own plugin (these instructions skip tests for expediency - you should be able to run the tests too!): git clone https://github.com/Wahanda/maven-interceptors.git cd maven-interceptors mvn install -DskipTests cd .. git clone https://github.com/Wahanda/maven-plugin.git cd maven-plugin mvn package -DskipTests You should then have an HPI file than can be uploaded to you Jenkins install in maven-plugin/target/maven-plugin.hpi. Following installation you should be able to use the -T4 and -T1C syntax. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [chef-identity-plugin] (JENKINS-25555) Delete .chef folder after job has ran
Tyler Fitch started work on JENKINS-2 Delete .chef folder after job has ran Change By: Tyler Fitch (13/Nov/14 7:27 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-25605) More easily map build instances to the configuration it was run it
Ken Beal created JENKINS-25605 More easily map build instances to the configuration it was run it Issue Type: New Feature Assignee: Mirko Friedenhagen Components: jobconfighistory-plugin Created: 13/Nov/14 7:32 PM Description: It would be useful to be able to see, at a glance, the configuration change lines with the build(s) that were done between them, interspersed. This way it would be easier to determine which build instances were run with which configuration change. One way could be to "draw lines" from the builds in the left column, to the configuration that build was run in, but I'm not sure whether line-drawing across columns can be done. The benefit to this is it wouldn't take any more screen real-estate. Another way is to put the builds that were run in between; in the below, each of the "#nn" would be a link to that build instance, like the builds in the left column; the "Build" line indicates that that (or those) build(s) was (were) done using the configuration line directly below it: Build #12, #13, #14 2014-11-11_17-31-35 Changed kbeal View as XML (RAW) 2014-11-11_17-30-29 Changed kbeal View as XML (RAW) Restore Build #11 2014-11-11_17-28-46 Changed kbeal View as XML (RAW) Restore 2014-11-10_18-46-38 Changed kbeal View as XML (RAW) Restore 2014-11-10_18-38-30 Changed kbeal View as XML (RAW) Restore Build #10, #9, #8 2014-11-10_18-37-43 Changed kbeal View as XML (RAW) Restore 2014-11-10_18-35-54 Changed kbeal View as XML (RAW) Restore Build #7 2014-11-10_18-32-34 Changed kbeal View as XML (RAW) Restore Build #6 2014-11-10_18-32-33 Changed kbeal View as XML (RAW) Restore Build #5 2014-11-10_18-32-32 Changed kbeal View as XML (RAW) Restore Build #4 2014-11-10_18-32-28 Created SYSTEM View as XML (RAW) Restore Build #3, #2, #1 2014-11-10_18-32-27 Changed kbeal View as XML (RAW) Restore Project: Jenkins Priority: Minor Reporter: Ken Beal This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cli] (JENKINS-25606) PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source
Joshua Strouse created JENKINS-25606 PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source Issue Type: Bug Assignee: Unassigned Attachments: mvnout.txt Components: cli Created: 13/Nov/14 8:00 PM Description: When building Jenkins from source (using the command 'mvn -Plight-test install'), the following error is given during test execution: PrivateKeyProviderTest.initializationError » IllegalState Failed to transform I followed the build instructions at: https://wiki.jenkins-ci.org/display/JENKINS/Building+Jenkins The full output of Maven is attached. Environment: Jenkins source code tag jenkins-1.589. Java 1.8.0-25. Maven 3.2.3. Windows 7 x64 and Mac OS X 10.9 Project: Jenkins Priority: Blocker Reporter: Joshua Strouse This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [checkstyle-plugin] (JENKINS-25511) Checkstyle double-escapes content
Alexander Obuhovich commented on JENKINS-25511 Checkstyle double-escapes content Thanks for looking into it. Same thing might be happening with /pmdResult/api/json page as well. I guess there is some central place, that once fixed will fix all such result pages. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
