[JIRA] [build-publisher] (JENKINS-21946) Build Publisher Pluging https authentication does not work
tapiomtr created JENKINS-21946 Build Publisher Pluging https authentication does not work Issue Type: Bug Assignee: vjuranek Components: build-publisher Created: 25/Feb/14 8:08 AM Environment: Windows/Linux Project: Jenkins Priority: Major Reporter: tapiomtr This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-publisher] (JENKINS-21946) Build Publisher Pluging when using https the jenkins loging does not work
tapiomtr updated JENKINS-21946 Build Publisher Pluging when using https the jenkins loging does not work Change By: tapiomtr (25/Feb/14 8:14 AM) Summary: BuildPublisherPluging whenusing https authentication thejenkinsloging doesnotwork Description: SSLlevelhandshakeseamstoworkasexpected,butafterthat,whentheplugingisrequiredtologginintotoourmasterJenkinsthelogginfailed.WhenusinghttpprotocoltoouroldJenkins,theJenkinslogginseamstoworkasexpected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyarchiver] (JENKINS-21945) Builds get stuck and after aborting throws ERROR: Publisher hudson.tasks.ArtifactArchiver aborted due to exception
Shobha Dashottar updated JENKINS-21945 Builds get stuck and after aborting throws ERROR: Publisher hudson.tasks.ArtifactArchiver aborted due to exception Change By: Shobha Dashottar (25/Feb/14 8:17 AM) Environment: JenkinsmasterWindows2K8R2.Jenkinsversion1.538Tomcat7Slave:Win2K3VMs. Description: Ithoughttherewasbugreportedaroundthisproblemthatwasfixedinearlierversions(issue19752)(issue19947)buttheproblemstillpersistsforme.Thebuildshanganduponcancellation,itthrowsanerrorArchivingartifacts22:27:06ERROR:Publisherhudson.tasks.ArtifactArchiverabortedduetoexception22:27:06java.lang.InterruptedException22:27:06 atjava.lang.Object.wait(NativeMethod)22:27:06 athudson.remoting.Request.call(Request.java:146)22:27:06 athudson.remoting.Channel.call(Channel.java:714)22:27:06 athudson.FilePath.act(FilePath.java:906)22:27:06 athudson.FilePath.act(FilePath.java:890)22:27:06 athudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:138)22:27:06 athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)22:27:06 athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:781)22:27:06 athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:753)22:27:06 athudson.model.Build$BuildExecution.post2(Build.java:183)22:27:06 athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706)22:27:06 athudson.model.Run.execute(Run.java:1704)22:27:06 athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)22:27:06 athudson.model.ResourceController.execute(ResourceController.java:88)22:27:06 athudson.model.Executor.run(Executor.java:230) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-publisher] (JENKINS-21946) Build Publisher Pluging when using https the jenkins loging does not work
tapiomtr updated JENKINS-21946 Build Publisher Pluging when using https the jenkins loging does not work Change By: tapiomtr (25/Feb/14 8:20 AM) Description: SSLlevelhandshakeseamstoworkasexpected,butafterthat,whentheplugingisrequiredtologginintotoourmasterJenkinsthelogginfailed.
[JIRA] [maven] (JENKINS-21554) NPE after Waiting for Jenkins to finish collecting data
Juha Syrjälä commented on JENKINS-21554 NPE after Waiting for Jenkins to finish collecting data My case also seems to be often but not allways triggered when tests fail. Cleaning workspace fixes problem, but still the end of the console log shows nullpointerexception: Waiting for Jenkins to finish collecting data channel stopped my-app $ /bin/sh -xe /tmp/hudson4500268711121840097.sh + echo 305 + echo 107213 Archiving artifacts FATAL: null java.lang.NullPointerException This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
Mathias Maak commented on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials workaround for us: connect to a cli on the jenkins server make an initial svn checkout to the svn url in a temp folder login to the svn an save password unencrypted now you should have in jenkins home a folder .subversion/auth/svn.simple/ with the credentials these credentials are used from svn tagging plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20682) Starting Jenkins with defined --webroot or JETTY_HOME not working.
Geoff Cummings commented on JENKINS-20682 Starting Jenkins with defined --webroot or JETTY_HOME not working. The following worked better for me: Set the jetty.home to Jenkins directory on the java opts when starting Jenkins -Djetty.home=$JENKINS_HOME Create a directory called "work" in Jenkins Home directory, or wherever you have set jetty.home That will cause Jetty to use that work directory instead of whatever the java.io.tmpdir property is set to. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21876) Error when save new Subversion Authentication
Serok Ferej commented on JENKINS-21876 Error when save new Subversion Authentication Same behavior even when saving SVN credentials. In my previous configured build it is working but when trying to configure Jenkins to use SVN credentials, this error occurs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21936) Git Plugin 2.0.2 and later NullPointerException onNotifyCommit
ritzmann commented on JENKINS-21936 Git Plugin 2.0.2 and later NullPointerException onNotifyCommit It is easy to reproduce the issue. Just put A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:381) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:685) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:587) at org.kohsuke.stapler.Stapler.service(Stapler.java:218) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Thorsten Stahl commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials I've got the same error since we updated the Subversion-Plugin from 1.54 to 2.2. I found a pattern in my case. This only happens with our repository trigger and only with jobs, which have a special svn:externals definition. The svn:externals are defined absolute (not relative) and refer another repository on the same host. 'Add additional credentials' don't work in all experiments with any kind of name-permutation in the 'Realm' field. Other jobs with svn:externals relative to their own repository works fine, even if i start the problem jobs manually. As work around i add the regarding external-url to the 'Source Code Management' section in the job configuration page and set the the repository depth to 'empty' and the 'Local module directory' to 'dummy_xxx'. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
Andrey Stegantsov commented on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials @Mathias Maak make an initial svn checkout to the svn url in a temp folder Could you please explain how to call "svn co" using jenkins cli ( https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI )? I only found groovysh. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Jose Sa commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials I had enable the polling from master option on startup "-Dhudson.scm.SubversionSCM.pollFromMaster=true" and after disabling it and restarting server, rechecking the polling from the slave instead of master now all urls fail to check with same stack trace. svn checkout doesn't seem to have a problem. Tested with Jenkins LTS 1.532.2 and svn plugin 2.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
Mathias Maak commented on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials @Andrey Stegantsov Could you please explain how to call "svn co" using jenkins cli ( https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI )? I only found groovysh. I did't mean Jenkins CLI. Connect to your Jenkins Server (Linux) via ssh (ssh user@jenkinsserver). Change to user jenkins (su - jenkins) and make the svn co. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-13140) Disconnected slaves come back online within a few minutes
mwebber reopened JENKINS-13140 Disconnected slaves come back online within a few minutes This is still an issue, at least as of Jenkins 1.522. I note that there are two actions you can take for a node: "mark temporarily offline" which keeps the slave.jar running, but doesn’t send any new jobs to the slave "disconnect" which means kill the slave.jar process (however, the slave process will be restarted in a few minutes) There is no option to actually kill the slave process, and stop it restarting. Also, there is confusion in the Jenkins code about what these options mean. If I "mark temporarily offline", then on the node staus page, it says "disconnected by ...", which is just mixing up two things that are supposed to be distinct. A rethink of what the options are is needed. Change By: mwebber (25/Feb/14 10:38 AM) Resolution: NotADefect Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix-combinations-parameter] (JENKINS-21816) Rebuild plugin support by Matrix Combinations plugin
ikedam resolved JENKINS-21816 as Fixed Rebuild plugin support by Matrix Combinations plugin supported in 1.0.5. Change By: ikedam (25/Feb/14 10:41 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-13140) Disconnected slaves come back online within a few minutes
mwebber commented on JENKINS-13140 Disconnected slaves come back online within a few minutes The original poster said: An alternative option is the "temporarily remove" a slave. This does what I had in mind. Jenkins ignores this slave and does not bring it back online There's no such option as "temporarily remove", at least in recent Jenkins releases. Perhaps he meant "mark temporarily offline". Although this does means Jenkins ignores the slave, it stil leaves the slave process running. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Mark Waite commented on JENKINS-20196 Failed to connect to URL (status = 404) Did you configure a credential for that bitbucket repository from the "Manage Jenkins" page, then use that credential from within the job definition? What version of the multiple SCM plugin are you using? My understanding is that there is a bug in the multiple SCM plugin 0.3 which causes it to not work correctly with the git plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-21330) java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful
Mohd Ali commented on JENKINS-21330 java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful @greg huber: Why do you say that this is not a problem? I mean the builds succeed but the errors in the log are annoying and not there in the previous version. DO you think other wise? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command
Dietmar Suoch commented on JENKINS-20387 Timeout (10min) on git clone command updated jenkins and some plugins yesterday and now have exactly the same issue when cloning or fetching our repo. my config: Jenkins: 1.551 GIT client plugin: 1.6.3 GIT plugin: 2.0.3 happy to read that it should be fixed since git-client-plugin 1.6.2 and git-plugin 2.0.2, so i don't have to downgrade again. can anyone confirm that this is working? also where is the GUI option for configuration? i don't find anything. or can somebody explain how to set this timeout manually? thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21944) Documentation contains broken link
Mark Waite resolved JENKINS-21944 as Fixed Documentation contains broken link I edited that wiki page. I'm not sure why the submitter chose not to edit the wiki page, but the edit was easy enough. Change By: Mark Waite (25/Feb/14 11:41 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21944) Documentation contains broken link
Mark Waite closed JENKINS-21944 as Fixed Documentation contains broken link Change By: Mark Waite (25/Feb/14 11:41 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command
Mark Waite commented on JENKINS-20387 Timeout (10min) on git clone command In the job configuration page under the Git plugin section, there is a drop-down list "Add". Within that dropdown list there is a selection "Advanced clone behaviours". When you add the advanced clone behaviors, you'll see a field for "Timeout (in minutes) for clone and fetch operation". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command
Mark Waite closed JENKINS-20387 as Fixed Timeout (10min) on git clone command Change By: Mark Waite (25/Feb/14 12:06 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-21330) java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful
Greg Huber commented on JENKINS-21330 java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful Well, I was initially complaining about my build not working, where it would not update from the svn, but miss understood the exception as an error. I think it does this when the build fails? I installed the poll plugin to force an update from the svn I guess it would be better to clean up the java.nio.file.DirectoryNotEmptyException message, to avoid this kind of confusion. Cheers Greg. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-21330) java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful
Mohd Ali commented on JENKINS-21330 java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful Ya . I agree. Going to reopen this as this seems to be coping in the stable release versions as well This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-21330) java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful
Greg Huber reopened JENKINS-21330 java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful other reporters also. Change By: Greg Huber (25/Feb/14 12:33 PM) Resolution: NotADefect 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command
Dietmar Suoch commented on JENKINS-20387 Timeout (10min) on git clone command and there it is - thank you very much Mark!!! i looked only under jenkins configuration. but makes sense to put it as a per job setting (forgot to look there). and i think also the shallow clone option helped to make the checkout faster ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21933) PermGen leaks
Heather Fraser-Dube commented on JENKINS-21933 PermGen leaks Is it a single build you are building over and over when it runs out of permgen space? Does the build run any ant tasks? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21298) Git polling not ignoring excluded users
Moosh Ben commented on JENKINS-21298 Git polling not ignoring excluded users The solution works, thanks. You can close this 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/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-21947) add job-dsl-plugin support for m2release plugin
Matthias Balke created JENKINS-21947 add job-dsl-plugin support for m2release plugin Issue Type: New Feature Affects Versions: current Assignee: Matthias Balke Components: job-dsl-plugin Created: 25/Feb/14 1:20 PM Description: Currently the job-dsl-plugin does not include DSL support for the m2release plugin. I'm currently extending the job-dsl-plugin to support this. https://github.com/matthiasbalke/job-dsl-plugin I will send a pull request, as soon, as it is tested. Project: Jenkins Priority: Major Reporter: Matthias Balke This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prqa] (JENKINS-21588) PRQA plugin runs if previous build steps failed ( praqma case 10681 )
Jason Masters commented on JENKINS-21588 PRQA plugin runs if previous build steps failed ( praqma case 10681 ) Hi Mikko, PRQA projects are more portable now than in older versions of the tool. The project files now support relative paths, both in reference to the files and include paths in the analyser personalities. Which version of the tool are you using? I have created a ticket for this issue – number 21316. This will provide an option in the post build section called 'Don't run post build step if build step fails’ which: if enabled, the PRQA post build step is not executed if previous Jenkins job steps failed if disabled the PRQA post build step will always be executed Best Regards, Jason This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-21947) add job-dsl-plugin support for m2release plugin
Matthias Balke started work on JENKINS-21947 add job-dsl-plugin support for m2release plugin Change By: Matthias Balke (25/Feb/14 1:23 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Flavio Donzé commented on JENKINS-20196 Failed to connect to URL (status = 404) "Multiple SCMs plugin" version 0.3 I do have some old credentials in the "manage jenkins" area, but I'm not using them in the job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21948) Exception thrown when trying to extract date from current build change set
Moosh Ben
created JENKINS-21948
Exception thrown when trying to extract date from current build change set
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
git, git-client
Created:
25/Feb/14 1:34 PM
Description:
Version 1.6.3 .
Using Force polling using workspace
Date parsing fails when trying to access date field in groovy:
Code used:
def thr = Thread.currentThread();
def currentBuild = thr?.executable;
def changes = currentBuild.getChangeSet();
changes.getItems().each {
ChangeLogSet.Entry lastChange = (ChangeLogSet.Entry)it;
lastChange.getTimestamp();
}
Exception:
ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com
java.lang.NumberFormatException: For input string: "1970-01-17T05:02:10+0200 +0200"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Long.parseLong(Long.java:441)
at java.lang.Long.parseLong(Long.java:483)
at hudson.plugins.git.GitChangeSet.getTimestamp(GitChangeSet.java:194)
at hudson.plugins.git.GitChangeSet$getTimestamp.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112)
at Script1$_run_closure1.doCall(Script1.groovy:23)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903)
at groovy.lang.Closure.call(Closure.java:415)
at groovy.lang.Closure.call(Closure.java:428)
at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1379)
at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1351)
at org.codehaus.groovy.runtime.dgm$170.invoke(Unknown Source)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
at Script1.run(Script1.groovy:20)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:650)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:636)
at hudson.plugins.groovy.SystemGroovy.perform(SystemGroovy.java:82)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:899)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:666)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:565)
at hudson.model.Run.execute(Run.java:1670)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
Project:
Jenkins
Priority:
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Jens Nielsen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access I'm seeing the same issue on the latest LTS release (1.532.2) downgrading to 1.532.1 fixes it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19312) Trigger an email after running the Poll SCM
Alex Earl commented on JENKINS-19312 Trigger an email after running the Poll SCM Waiting for this (https://github.com/jenkinsci/jenkins/pull/1051) to make it into an LTS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21465) java.io.IOException: remote file operation failed
Artem Alexandrov updated JENKINS-21465 java.io.IOException: remote file operation failed Change By: Artem Alexandrov (25/Feb/14 2:11 PM) Description: Gettingthisexceptionwhentryingtowipeoutaworkspacelastbuiltonremoteslave:java.io.IOException:remotefileoperationfailed:/Volumes/Store2/Jenkins/workspace/project1athudson.remoting.Channel@6a3d610d:macservXCode5 athudson.FilePath.act(FilePath.java:910) athudson.FilePath.act(FilePath.java:887) athudson.FilePath.deleteRecursive(FilePath.java:1076) athudson.model.AbstractProject.doDoWipeOutWorkspace(AbstractProject.java:2093) atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:606) atorg.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) atorg.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) atorg.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) atorg.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:631) atorg.kohsuke.stapler.Stapler.service(Stapler.java:225) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
[JIRA] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
SANJAY TIWARI commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails I do not see any recent update to this issue. What is the conclusion on resolving this issue? What I see is that jenkins must be run as service Linux/Windows, does that mean you need to have a dedicated Linux/Windows account for it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-21949) ec2: if spot insantce goes away, ec2 plugin crashes
Ryan Vanderwerf created JENKINS-21949 ec2: if spot insantce goes away, ec2 plugin crashes Issue Type: Bug Affects Versions: current Assignee: Francis Upton Components: ec2 Created: 25/Feb/14 2:33 PM Description: I created a slave with a spot instance in ec2 config, however I shut it down over a weekend. Come monday the instance ID isn't recognized by aws, and it causes the ec2 plugin to crash and no longer function (no new slaves, etc). Feb 24, 2014 11:55:24 PM hudson.plugins.ec2.EC2Cloud provision WARNING: Failed to count the # of live instances on EC2 Status Code: 400, AWS Service: AmazonEC2, AWS Request ID: 48ef733c-28c1-423e-9900-62de12315457, AWS Error Code: InvalidSpotInstanceRequestID.NotFound, AWS Error Message: The spot instance request ID 'sir-f43fdc4f' does not exist at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:614) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:312) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:165) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:6047) at com.amazonaws.services.ec2.AmazonEC2Client.describeSpotInstanceRequests(AmazonEC2Client.java:3068) at hudson.plugins.ec2.EC2Cloud.provision(EC2Cloud.java:331) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:281) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:51) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:366) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 1) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) 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:724) And now I get this over and over: Feb 24, 2014 11:55:53 PM hudson.node_monitors.ResponseTimeMonitor$1 monitor WARNING: Making 541693b6-21dc-4c5d-b98b-717d03349d20 offline because it’s not responding however it will not launch any new slaves, even if I have the executor limit on the ec2 plugin set to 20. I'm not sure how to clear the history of all executors, so I am stuck without any slaves now. Environment: 1.551 ubuntu native package, ec2 plugin v 1.20 Project: Jenkins Priority: Critical Reporter: Ryan Vanderwerf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-21949) ec2: if spot insantce goes away, ec2 plugin crashes
Ryan Vanderwerf commented on JENKINS-21949 ec2: if spot insantce goes away, ec2 plugin crashes I'm stuck in an endless loop as well, trying to delete the slave results in a NPE: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Caused by: java.lang.NullPointerException at hudson.plugins.ec2.EC2SpotSlave.terminate(EC2SpotSlave.java:51) at hudson.plugins.ec2.EC2Computer.doDoDelete(EC2Computer.java:168) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at
[JIRA] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Mark Waite commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails Jenkins may be run as a service on both Linux and Windows. When Jenkins is installed using the Windows (MSI) installer, it runs by default with the permissions of a service, similar to many other Windows services. No dedicated Windows account is required for it. When Jenkins is installed using the Debian package manager (Debian, Ubuntu, etc.), a "jenkins" user is created and that user is the user which runs Jenkins. When Jenkins is installed using the Red Hat package manager (Red Hat, CentOS, Scientific Linux, Oracle Linux, etc.), I believe a "jenkins" user is created and that is the user which runs Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21298) Git polling not ignoring excluded users
Mark Waite resolved JENKINS-21298 as Fixed Git polling not ignoring excluded users Change By: Mark Waite (25/Feb/14 3:06 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Mark Waite edited a comment on JENKINS-20533 Git2 plugin and HTTP-authentication fails Jenkins may be run as a service on both Linux and Windows. When Jenkins is installed using the Windows (MSI) installer, it is installed as a service and runs with the permissions of a service, similar to many other Windows services. No dedicated Windows account is required for it. When Jenkins is installed using the Debian package manager (Debian, Ubuntu, etc.), a "jenkins" user is created and that user is the user which runs Jenkins. When Jenkins is installed using the Red Hat package manager (Red Hat, CentOS, Scientific Linux, Oracle Linux, etc.), I believe a "jenkins" user is created and that is the user which runs Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21298) Git polling not ignoring excluded users
Mark Waite closed JENKINS-21298 as Fixed Git polling not ignoring excluded users Change By: Mark Waite (25/Feb/14 3:06 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21769) NoClassDefFoundError on Job page when checkstyle not installed
Francis Labrie edited a comment on JENKINS-21769 NoClassDefFoundError on Job page when checkstyle not installed I have the same problem on Mac OS X 10.9 Mavericks, and I get it whenever the CheckStyle plugin is installed or not. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21769) NoClassDefFoundError on Job page when checkstyle not installed
Francis Labrie commented on JENKINS-21769 NoClassDefFoundError on Job page when checkstyle not installed I have the same problem on Mac OS X 10.9 Mavericks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-20426) FATAL: The IdentityManagementService is not available from the server
SCM/JIRA link daemon commented on JENKINS-20426 FATAL: The IdentityManagementService is not available from the server Code changed in jenkins User: Vladimir Kralik Path: src/main/java/hudson/plugins/tfs/model/FakeIdentityManagementService.java src/main/java/hudson/plugins/tfs/model/Project.java http://jenkins-ci.org/commit/tfs-plugin/3890309736132177bea3f4dd9b2eca1abc657132 Log: JENKINS-20426:If IdentityManagementService is not available on server, the fake implementation is used. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21948) Exception thrown when trying to extract date from current build change set
Mark Waite updated JENKINS-21948 Exception thrown when trying to extract date from current build change set I believe this stack trace is close enough to JENKINS-21906 to be a duplicate of that bug. Change By: Mark Waite (25/Feb/14 3:11 PM) Component/s: git-client This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21948) Exception thrown when trying to extract date from current build change set
Mark Waite edited a comment on JENKINS-21948 Exception thrown when trying to extract date from current build change set I believe this stack trace is close enough to JENKINS-21906 to be a duplicate of that bug. The bug may be related to change https://github.com/jenkinsci/git-plugin/commit/430bdc9b6ed121d653ef2633d2109b259aa8687b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21948) Exception thrown when trying to extract date from current build change set
Mark Waite resolved JENKINS-21948 as Duplicate Exception thrown when trying to extract date from current build change set Duplicate of JENKINS-21906 Change By: Mark Waite (25/Feb/14 3:14 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21944) Documentation contains broken link
cowwoc commented on JENKINS-21944 Documentation contains broken link Sorry. I remember looking for an Edit button, but at the time I did not see it. I see it now, though. Thanks for the head's up. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
cowwoc commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Jesse, Will this fix jobs where malformed culprits were being copied from earlier builds, or do we need to manually "flush" the job history somehow? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-20426) FATAL: The IdentityManagementService is not available from the server
SCM/JIRA link daemon commented on JENKINS-20426 FATAL: The IdentityManagementService is not available from the server Code changed in jenkins User: Olivier "Oli" Dagenais Path: src/main/java/hudson/plugins/tfs/model/LegacyIdentityManagementService.java src/main/java/hudson/plugins/tfs/model/Project.java http://jenkins-ci.org/commit/tfs-plugin/f746124c4e532eeedaa097d6da914092ef99241e Log: Merge pull request #23 from jenkinsci/JENKINS-20426 JENKINS-20426 Support TFS 2008 This is done through a fall-back implementation of `IIdentityManagementService` that does not require TFS 2010 but also currently can't resolve a user's display name or e-mail address. Compare: https://github.com/jenkinsci/tfs-plugin/compare/10098fe700ad...f746124c4e53 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-12353) Git command fails on Windows when git installed in default place (C:\Program Files\Git).
Mark Waite commented on JENKINS-12353 Git command fails on Windows when git installed in default place (C:\Program Files\Git). I can't duplicate this bug report. Most of the Windows machines I configure have Git in the PATH, just as described in this bug report, and they work quite well. I don't configure the location of Git in the Jenkins administration, and I don't make any changes to other Git related configuration and it works great for me. Can you offer other insights about what might be different in your environment compared to mine? I add the Git\bin directory to the PATH, not the Git\cmd directory, since I've seen bug reports that it is not sufficient to add the Git\cmd directory to the PATH. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-12087) git: support 'git svn' integration
Mark Waite resolved JENKINS-12087 as Wont Fix git: support git svn integration Considering the already complex workflows available from the Git plugin and the Git client plugin, and the availability of the Subversion plugin for Jenkins, I'm marking this as "Won't fix". I think it would not be helpful to add even more complexity to the Git plugin workflow (how to configure git svn, how to recover when git svn has a problem, etc.). Change By: Mark Waite (25/Feb/14 3:25 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/groups/opt_out.
[JIRA] [tfs] (JENKINS-20426) FATAL: The IdentityManagementService is not available from the server
Olivier Dagenais commented on JENKINS-20426 FATAL: The IdentityManagementService is not available from the server Pull request #22 was replaced by pull request #23 and merged. Changes will appear in the next release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Jesse Glick commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification This fix will not handle all cases involving historical records. If a new build is run after upgrade whose changelog mentions the given committer’s full name, that name will be properly registered and you should not see the problem for that user again. The main problem I can foresee is a build which was failing at the time of upgrade, and continues to fail without new changes being committed (to that or other jobs developed by the same people), and is using an email trigger configured to repeatedly send mail for every unstable build. Again there are no “malformed” culprits fields here. The culprits list is correct; the problem only arises when the culprits list contains the only record of a given user in the system. You ought to be able to work around the problem for a given user by visiting that user’s page as hyperlinked from a changelog (logged in as an administrator), and explicitly setting a full name (and/or email address). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-19863) Can we get more colors for promotion stars?
Marvi Benedet resolved JENKINS-19863 as Fixed Can we get more colors for promotion stars? pulled https://github.com/jenkinsci/promoted-builds-plugin/pull/36 Change By: Marvi Benedet (25/Feb/14 3:58 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [naginator] (JENKINS-21950) Naginator retries jobs on manual cancel
Jonathan Rogers created JENKINS-21950 Naginator retries jobs on manual cancel Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: naginator Created: 25/Feb/14 4:24 PM Description: If I cancel a job manually, naginator retries it as if it had failed. Project: Jenkins Priority: Minor Reporter: Jonathan Rogers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
cowwoc commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification I see. So just to make sure I understand correctly: Until a user makes a new commit, any existing jobs will keep on using the incorrect email address. Once a user makes a new commit, his email address will get corrected system-wide across all jobs. Alternatively, deleting the contents of the "builds" directory will remove all changelogs and force re-evaluation of the email address. Is that correct? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21936) Git Plugin 2.0.2 and later NullPointerException onNotifyCommit
Deniz Bahadir commented on JENKINS-21936 Git Plugin 2.0.2 and later NullPointerException onNotifyCommit I am experiencing the exact same behavior. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Jesse Glick commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Until a user makes a new commit, any existing jobs will keep on using the incorrect email address. Once a user makes a new commit, his email address will get corrected system-wide across all jobs. Right. You can simply look in $JENKINS_HOME/users/ to see whether the user has been defined or not. deleting the contents of the "builds" directory will remove all changelogs and force re-evaluation of the email address. No. If you deleted all historical builds, then either the next build has commits from the relevant user(s), in which case their email addresses will be recorded; or it does not, in which case the culprits list for that build will simply be empty and no email will be sent (unless you have an unconditional recipient configured in the job). In the former case, deleting the old build records does not improve your situation at all. In the latter case, deleting them could make the new build’s status be “unstable” due to test failures or whatever, rather than “failed” due to an attempt to send mail to bogus addresses, but the email addresses of users mentioned in those old builds would still be missing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-3785) Add option to perform labeling for each TFS build
Olivier Dagenais closed JENKINS-3785 as Fixed Add option to perform labeling for each TFS build Fixed in release 3.1.1 Change By: Olivier Dagenais (25/Feb/14 4:44 PM) Status: Resolved Closed Assignee: redsolo jeffolson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-20426) FATAL: The IdentityManagementService is not available from the server
Olivier Dagenais resolved JENKINS-20426 as Fixed FATAL: The IdentityManagementService is not available from the server Fixed in release 3.1.1 Change By: Olivier Dagenais (25/Feb/14 4:44 PM) Status: InProgress Resolved Assignee: OlivierDagenais KyleOConnor Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20548) View - Filter Build Executors always filters based on the default view
clint axeda commented on JENKINS-20548 View - Filter Build Executors always filters based on the default view anybody even lookin at this 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/groups/opt_out.
[JIRA] [core] (JENKINS-16959) No notification e-mail when build fails due to broken communication channel to slave
evernat commented on JENKINS-16959 No notification e-mail when build fails due to broken communication channel to slave Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [embeddable-build-status] (JENKINS-21951) Support running status with correct background in the embeddable-build-status plugin.
Christophe Juniet created JENKINS-21951 Support running status with correct background in the embeddable-build-status plugin. Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: embeddable-build-status Created: 25/Feb/14 6:09 PM Description: Add three different icons for running builds while preserving the previous status background color. This should better follow "animated" BallColors. Project: Jenkins Priority: Trivial Reporter: Christophe Juniet This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-13140) Disconnected slaves come back online within a few minutes
Daniel Beck commented on JENKINS-13140 Disconnected slaves come back online within a few minutes Can the 'Availability' option in the slave config be used to not reconnect automatically? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [buildgraph-view] (JENKINS-19470) Build Graph not displaying
Luke Woydziak commented on JENKINS-19470 Build Graph not displaying another +1 here This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work
Damien Nozay updated JENKINS-20879 SSH Credentials (private key with passphrase) do not work Change By: Damien Nozay (25/Feb/14 7:27 PM) Summary: SSHCredentials (privatekeywithpassphrase) donotwork toconnecttoprivateGitHubrepository This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work
Damien Nozay updated JENKINS-20879 SSH Credentials (private key with passphrase) do not work The issue is not limited to private GitHub repositories. I have confirmed on my system that a non-empty passphrase is the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work
Damien Nozay commented on JENKINS-20879 SSH Credentials (private key with passphrase) do not work /var/log/secure when attempting to use credentials that have a passphrase Feb 25 11:16:57 git sshd32273: Failed password for jenkins from X.X.X.X port 57524 ssh2 Feb 25 11:16:57 git sshd32273: Failed password for jenkins from X.X.X.X port 57524 ssh2 Feb 25 11:16:57 git sshd32274: Connection closed by X.X.X.X /var/log/secure when attempting to use credentials that do not have a passphrase Feb 25 11:17:00 git sshd32276: Accepted publickey for jenkins from X.X.X.X port 57526 ssh2 Feb 25 11:17:00 git sshd32276: pam_unix(sshd:session): session opened for user jenkins by (uid=0) Feb 25 11:17:00 git sshd32279: Received disconnect from X.X.X.X: 11: disconnected by user Feb 25 11:17:00 git sshd32276: pam_unix(sshd:session): session closed for user jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21730) Allow for selection of Bcc: for email recipients on global recipient list
Tyler Fitch assigned JENKINS-21730 to Tyler Fitch Allow for selection of Bcc: for email recipients on global recipient list Change By: Tyler Fitch (25/Feb/14 7:39 PM) Assignee: TylerFitch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21730) Allow for selection of Bcc: for email recipients on global recipient list
Tyler Fitch resolved JENKINS-21730 as Fixed Allow for selection of Bcc: for email recipients on global recipient list Since the Pull Request was merged to master I thought I'd help with a little house keeping and mark the issue as fixed. Since there's only one Fix Version available I used 'current'. Change By: Tyler Fitch (25/Feb/14 7:40 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16959) No notification e-mail when build fails due to broken communication channel to slave
tazle commented on JENKINS-16959 No notification e-mail when build fails due to broken communication channel to slave It's difficult to say. The SSH issues have since stopped. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [master-slave] (JENKINS-15247) Windows Slave ERROR: Message not found for errorCode: 0x00001031
Peter Kolínek commented on JENKINS-15247 Windows Slave ERROR: Message not found for errorCode: 0x1031 This could be added to Wiki page with hints about Windows slaves: https://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21871) Websphere deploy plugin
Greg Peters assigned JENKINS-21871 to Greg Peters Websphere deploy plugin Change By: Greg Peters (25/Feb/14 8:06 PM) Assignee: GregPeters This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21871) Websphere deploy plugin
Greg Peters commented on JENKINS-21871 Websphere deploy plugin This plugin must connect to the WebSphere Admin Console over HTTPS. Make sure the port is open. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21871) Websphere deploy plugin
Greg Peters resolved JENKINS-21871 as Wont Fix Websphere deploy plugin Validate port is open over HTTPS and make sure cert for admin console is used. Change By: Greg Peters (25/Feb/14 8:06 PM) Status: Open Resolved Fix Version/s: current 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/groups/opt_out.
[JIRA] [git] (JENKINS-20445) Git plugin timeout is too small
Josh Santangelo commented on JENKINS-20445 Git plugin timeout is too small I have the Git plugin 2.0.3, and Git Client Plugin 1.6.3, but I don't see any new option. Am I just missing it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Greg Peters started work on JENKINS-21863 WebSphere deployer: deploy to cluster Change By: Greg Peters (25/Feb/14 8:08 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Greg Peters assigned JENKINS-21863 to Greg Peters WebSphere deployer: deploy to cluster Change By: Greg Peters (25/Feb/14 8:08 PM) Assignee: GregPeters This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
Greg Peters resolved JENKINS-21643 as Wont Fix Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) Seems this issue is related to port not being open on WebSphere so that Jenkins can upload artifact. Change By: Greg Peters (25/Feb/14 8:12 PM) Status: InProgress Resolved Fix Version/s: current 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/groups/opt_out.
[JIRA] [git] (JENKINS-20445) Git plugin timeout is too small
Mark Waite closed JENKINS-20445 as Fixed Git plugin timeout is too small Change By: Mark Waite (25/Feb/14 8:13 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20445) Git plugin timeout is too small
Mark Waite commented on JENKINS-20445 Git plugin timeout is too small In the job configuration page under the Git plugin section, there is a drop-down list "Add". Within that dropdown list there is a selection "Advanced clone behaviours". When you add the advanced clone behaviors, you'll see a field for "Timeout (in minutes) for clone and fetch operation". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21129) Unable to test multiple connections without restarting Jenkins server
Greg Peters resolved JENKINS-21129 as Wont Fix Unable to test multiple connections without restarting Jenkins server No response was given, closing issue. If this is still an issue using plugin v1.2 you may reopen it but only if you can provide the steps needed to reproduce. Change By: Greg Peters (25/Feb/14 8:13 PM) Status: Reopened 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/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Greg Peters commented on JENKINS-21863 WebSphere deployer: deploy to cluster Can you confirm that cluster and cell are the only required inputs? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Mark Waite commented on JENKINS-20196 Failed to connect to URL (status = 404) You might try defining a test job which uses only Git with your bitbucket repository. If that clones successfully, then the problem is likely an interaction between the multiple SCM plugin and the Git plugin. If that doesn't clone successfully, then you might try placing the user name and password as a credential in Jenkins, then reference the credential from the job definition. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21769) NoClassDefFoundError on Job page when checkstyle not installed
Daniel Kirkdorffer commented on JENKINS-21769 NoClassDefFoundError on Job page when checkstyle not installed Same problem for me. Jenkins 1.528 Analysis Collector Plugin 1.39 1.38 PMD Plugin 3.38 3.37 Static Analysis Utilities 1.55 1.54 javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/home/build/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven-plugin.jar!/hudson/maven/MavenModuleSet/index.jelly:71:70: st:include hudson/plugins/checkstyle/CheckStyleProjectAction 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:674) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:685) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:685) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:587) at org.kohsuke.stapler.Stapler.service(Stapler.java:218) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 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.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at
[JIRA] [analysis-core] (JENKINS-21769) NoClassDefFoundError on Job page when checkstyle not installed
knalli commented on JENKINS-21769 NoClassDefFoundError on Job page when checkstyle not installed Yep, same here. Reverting to Analysis Collector Plugin 1.38 solves the issue. Running the current LTS. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21769) NoClassDefFoundError on Job page when checkstyle not installed
Tamas Papp commented on JENKINS-21769 NoClassDefFoundError on Job page when checkstyle not installed Downgrading Analysis Collector Plugin to 1.38 is a good workaround (works for me). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21769) NoClassDefFoundError on Job page when checkstyle not installed
Daniel Kirkdorffer commented on JENKINS-21769 NoClassDefFoundError on Job page when checkstyle not installed I rolled back all three that I'd updated at the same time and it solves my issue: Analysis Collector Plugin 1.39 to 1.38 PMD Plugin 3.38 to 3.37 Static Analysis Utilities 1.55 to 1.54 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-status] (JENKINS-19445) Jobs randomly stuck with building remotely on slave-name message
VladDRussian commented on JENKINS-19445 Jobs randomly stuck with building remotely on slave-name message Thought i'd throw in my errors. We are seeing HTTP stop responding and visualVM can't take a dump once it fails. Memory is fine, but threads just keep increasing, once they hit 550-600 active it just stops and says memory issue won't respond till the master is restarted. Jenkins 1.484, win2k3 (master) win2k8/win2k3 (slaves) Feb 25, 2014 9:21:06 AM hudson.model.DownloadService$Downloadable doPostBack INFO: Obtained the updated data file for hudson.tools.JDKInstaller Feb 25, 2014 9:21:06 AM hudson.model.DownloadService$Downloadable doPostBack INFO: Obtained the updated data file for hudson.tasks.Ant.AntInstaller Feb 25, 2014 9:21:06 AM org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception java.io.IOException: Unable to delete E:\jenkins\updates\hudson.tasks.Maven.MavenInstaller at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:112) at hudson.util.TextFile.write(TextFile.java:81) at hudson.model.DownloadService$Downloadable.doPostBack(DownloadService.java:260) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) 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 org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [cucumber-reports] (JENKINS-21703) Cucumber Test results plugin
Sandro Simas commented on JENKINS-21703 Cucumber Test results plugin I'm getting this exception too. Does anybody knows how to solve that ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cucumber-testresult] (JENKINS-21835) Cucumber Test Result Plugin does not correctly parse Scenario Outline results
Sandro Simas commented on JENKINS-21835 Cucumber Test Result Plugin does not correctly parse Scenario Outline results I'm getting this error too. Does anybody knows how to solve that ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-1948) Intermittent slave disconnections with secondary symptoms
jminne commented on JENKINS-1948 Intermittent slave disconnections with secondary symptoms I'm also seeing this only on an OSX slave. Windows and linux slaves are fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan Pauxberger created JENKINS-21952 Git Plugin fails to resolve tags containing a slash since 2.0.1 Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 25/Feb/14 9:19 PM Description: Since updating from 2.0.1 to 2.0.3, a job which uses tags containing a slash as "branch" do not work anymore (rel/x.y.z-... in my case) Build results in "Couldn't find any revision to build. Verify the repository and branch configuration for this job." Downgrading to 2.0.1 solves the problem. The problem has already been discussed in JENKINS-14206, but the applied fix only works for slash-less tags Project: Jenkins Priority: Critical Reporter: Stephan Pauxberger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21933) PermGen leaks
Heather Fraser-Dube commented on JENKINS-21933 PermGen leaks Thought about this more. We shouldn't be using Antrunner afik. Is this happening with a single job with a single toolkit and a single build user defined? If the answer is No... How many toolkits do you have defined? How many any other jobs on your Jenkins instance? Do they use different toolkits? Different build users ids? Is polling enabled? If so at what frequency and for how many jobs? What version of the toolkit are you using? Which version of Jenkins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21933) PermGen leaks
Heather Fraser-Dube commented on JENKINS-21933 PermGen leaks Are you using a build definition or a build workspace? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nodejs] (JENKINS-21953) NodeJs plugin doesn't work on windows based Jenkins machine
Jesse Sanders
created JENKINS-21953
NodeJs plugin doesnt work on windows based Jenkins machine
Issue Type:
Bug
Assignee:
Unassigned
Components:
nodejs
Created:
25/Feb/14 9:55 PM
Description:
Using the instructions provided, I setup the plugin locally and point it to my existing installation of NodeJs (since it is a windows machine). I then setup my job to use an execute script to get my node version, which works. When I add a execute nodejs script to my build with this in it:
var sys = require('sys');
sys.puts('build number:' + process.envBUILD_NUMBER);
sys.puts('current directory: ' + process.cwd());
I get this error when I run the job:
Building in workspace C:\Program Files (x86)\Jenkins\jobs\NodeJs\workspace
workspace $ sh -xe C:\Windows\TEMP\hudson3559847244933178029.sh
+ node --version
v0.10.26
workspace $ C:\Windows\TEMP\hudson6840666181877118834.js
%1 is not a valid Win32 application
FATAL: command execution failed
java.io.IOException: Cannot run program "C:\Windows\TEMP\hudson6840666181877118834.js" (in directory "C:\Program Files (x86)\Jenkins\jobs\NodeJs\workspace"): CreateProcess error=193, %1 is not a valid Win32 application
at java.lang.ProcessBuilder.start(Unknown Source)
at hudson.Proc$LocalProc.init(Proc.java:244)
at hudson.Proc$LocalProc.init(Proc.java:216)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:773)
at jenkins.plugins.nodejs.tools.DecoratedLauncher.launch(DecoratedLauncher.java:49)
at jenkins.plugins.nodejs.tools.NpmPackagesBuildWrapper$2.launch(NpmPackagesBuildWrapper.java:88)
at hudson.Launcher$ProcStarter.start(Launcher.java:353)
at hudson.Launcher$ProcStarter.join(Launcher.java:360)
at jenkins.plugins.nodejs.NodeJsCommandInterpreter.perform(NodeJsCommandInterpreter.java:84)
at jenkins.plugins.nodejs.NodeJsCommandInterpreter.perform(NodeJsCommandInterpreter.java:42)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784)
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:565)
at hudson.model.Run.execute(Run.java:1670)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
Caused by: java.io.IOException: CreateProcess error=193, %1 is not a valid Win32 application
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.init(Unknown Source)
at java.lang.ProcessImpl.start(Unknown Source)
... 19 more
Build step 'Execute NodeJS script' marked build as failure
Finished: FAILURE
Environment:
Windows 2012, Jenkins 1.552, and NodeJS Plugin 0.2.1
Project:
Jenkins
Priority:
Major
Reporter:
Jesse Sanders
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
