[JIRA] [testlink] (JENKINS-17608) Test Link plugin, show the test results in the category "notes"
Jeanjean LaGuigne reopened JENKINS-17608 Test Link plugin, show the test results in the category "notes" Change By: Jeanjean LaGuigne (25/Nov/13 8:25 AM) Resolution: Postponed 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] [clearcase-ucm] (JENKINS-20747) CCUCM 1.5.0 on RHEL 5.6 fails to list baselines (our case 10335)
Mads Nielsen created JENKINS-20747 CCUCM 1.5.0 on RHEL 5.6 fails to list baselines (our case 10335) Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: clearcase-ucm Created: 25/Nov/13 8:44 AM Description: Caught exception in GetRemoteBaselineFromStream: net.praqma.clearcase.exceptions.UnableToListBaselinesException: net.praqma.util.execute.AbnormalProcessTerminationException: bash: line 0: fg: no job control Command: cleartool lsbl -fmt %Xn;%Nd\n -component component:_COMP@/OUR_pvob -stream stream:stream7_INT@/OUR_pvob Path: null Fix Versions: current Project: Jenkins Priority: Major Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-20193) disk usage plugin seems to scan /
Lucie Votypkova commented on JENKINS-20193 disk usage plugin seems to scan / Disk usage controls the modules too, so it could be this reason, please can send me all build.xml files on my e-mail lvoty...@redhat.com?. I can clearly check what is wrong. I think that it was really caused by custom workspace. I think that disk usage should separate custom workspaces from ordinary workspaces. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [clearcase-ucm] (JENKINS-20748) Self polling returns null as computername on linux when creating viewtag (our case 10336)
Mads Nielsen created JENKINS-20748 Self polling returns null as computername on linux when creating viewtag (our case 10336) Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: clearcase-ucm Created: 25/Nov/13 8:46 AM Fix Versions: current Project: Jenkins Priority: Major Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extreme-feedback] (JENKINS-20749) Some jobs are missing in "Available jobs" multichoice window
Michal Tyde created JENKINS-20749 Some jobs are missing in "Available jobs" multichoice window Issue Type: Bug Affects Versions: current Assignee: emanuelez Components: extreme-feedback Created: 25/Nov/13 9:28 AM Description: When I edit settings from plugin Extreme Feedback Panel I do not see all of the jobs inside multichoice window (I am missing the newest jobs from Jenkins). When I create new panel and I use Extreme Feedback Panel I can see all of the jobs inside "Available jobs" (the newest jobs are included). I have rebooted Jenkins and machine. The situation still occurs. Due Date: 31/Dec/13 12:00 AM Environment: org.jenkins-ci.plugins:xfpanel:1.2.2 Linux lsc02lnx02 2.6.18-238.el5 #1 SMP Sun Dec 19 14:22:44 EST 2010 x86_64 x86_64 x86_64 GNU/Linux Project: Jenkins Labels: plugin Priority: Major Reporter: Michal Tyde This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20750) Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error
Pavel Kudrys created JENKINS-20750 Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 25/Nov/13 9:31 AM Description: Last week I started to experience some weird problems with the GIT fetch. As far as I remember, I did not update Jenkins or any of its plugins and I'm also not aware of any company GIT/networks changes. All of sudden, jobs started to fail fetching. And the problem is it happens randomly. Sometimes it works as before, sometimes it don't. Here is a typical error I'm getting: Started by timer Building on master in workspace C:\Documents and Settings\Tester\.jenkins\jobs\litebox3d_tiff_32_64\workspace Updating svn://krivan/Ranorex/trunk/xSpector at revision '2013-11-25T02:14:53.975 +0100' At revision 260 no change for svn://krivan/Ranorex/trunk/xSpector since the previous build Fetching changes from the remote Git repository Fetching upstream changes from git@swserv:litebox3d ERROR: Timeout after 10 minutes FATAL: Failed to fetch from git@swserv:litebox3d hudson.plugins.git.GitException: Failed to fetch from git@swserv:litebox3d at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:612) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:836) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:861) at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:117) at hudson.model.AbstractProject.checkout(AbstractProject.java:1412) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557) at hudson.model.Run.execute(Run.java:1679) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43) Caused by: hudson.plugins.git.GitException: Command "fetch -t git@swserv:litebox3d +refs/heads/:refs/remotes/origin/" returned status code -1: stdout: stderr: Could not create directory 'c/Documents and Settings/Tester/.ssh'. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:981) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:920) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.fetch(CliGitAPIImpl.java:187) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:229) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:610) ... 12 more It does not happen always! Just from time to time, but enought frequently to break our build/test workflow. What's really weird is this error: stderr: Could not create directory 'c/Documents and Settings/Tester/.ssh'. Please notice the missing colon character in the path! In any case, the pointed path exists (of course, only if the colon is available) so there should be no reason for such error, except if the reason is missing colon? But then why it does not happen always? I also noticed, that after this failure, it's impossible to manually delete the content of the workspace/.git folder, because of some locked files. And it does not help to just stop Jenkins. The machine must be restarted to be able to delete the remaining files. I'm aware of the issue JENKINS-20445 (too small Git plugin timeout) and while it appears to be also my problem, the reason/source of problem seems to something else? Up to last week, I never experienced such timeout problem. Please don't hesitate to contact me in case of questions regarding our jenkins/jobs setup. Project: Jenkins Priority: Major Reporter:
[JIRA] [testlink] (JENKINS-17608) Test Link plugin, show the test results in the category "notes"
Jeanjean LaGuigne commented on JENKINS-17608 Test Link plugin, show the test results in the category "notes" Hi bruno, I'm fine thanks ^^. I'm ok to reopen this issue And I'll open another issue cause i've some problemes of communication between testlink and testLink 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] [slave-setup] (JENKINS-13869) [Unexpected termination of the channel] for Unix SSH slaves
Uldis Karlovs-Karlovskis commented on JENKINS-13869 [Unexpected termination of the channel] for Unix SSH slaves Hi everyone. Is any development continued on this issue? We are getting these quite often and JVM tuning doesn't help any plans when it could be 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] [integrity-plugin] (JENKINS-20751) PTC_Integrity Plugin- file exclude filter not working for multiple entries
Matthias Rump created JENKINS-20751 PTC_Integrity Plugin- file exclude filter not working for multiple entries Issue Type: Bug Assignee: Cletus D'Souza Components: integrity-plugin Created: 25/Nov/13 9:36 AM Description: There is an error in the implementation of the EXCLUDE filter. In contrast to Include filters, multiple Excludes must be AND combined. Bugfix already implemented and Pull Request is pending. Environment: any Project: Jenkins Labels: plugin ptc integrity exclude Priority: Major Reporter: Matthias Rump This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [testlink] (JENKINS-20752) TestLink is unable to get the devKey
Jeanjean LaGuigne created JENKINS-20752 TestLink is unable to get the devKey Issue Type: Bug Assignee: Bruno P. Kinoshita Components: testlink Created: 25/Nov/13 9:50 AM Description: Hi, i am making some test automation with Jenkins and testlink, but when I launch a build, Jenkins's build failed because the plugin testlink can't read the developer's key. This is the error output : Preparing TestLink client API. Using TestLink URL: https://testlink-test-transport.parkeon.com/lib/api/xmlrpc/v1/xmlrpc.php FATAL: Error verifying developer key: Failed to read server's response: java.security.cert.CertificateException: No subject alternative DNS name matching testlink-test-transport.parkeon.com found. br.eti.kinoshita.testlinkjavaapi.util.TestLinkAPIException: Error verifying developer key: Failed to read server's response: java.security.cert.CertificateException: No subject alternative DNS name matching testlink-test-transport.parkeon.com found. I am using Testlink 1.9.8, Jenkins 1.536, testLink Plugin 3.8 Plz help me Bruno ^^ Environment: Testlink 1.9.8, Jenkins 1.536, testLink Plugin 3.8 Project: Jenkins Priority: Major Reporter: Jeanjean LaGuigne This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-13869) [Unexpected termination of the channel] for Unix SSH slaves
Henri Gomez commented on JENKINS-13869 [Unexpected termination of the channel] for Unix SSH slaves It seems this issue has been fixed in Jenkins 1.536 : See JENKINS-18836, JENKINS-18879 and JENKINS-19619 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cli] (JENKINS-20744) Don't hold off building until saved for jobs copied from CLI
SCM/JIRA link daemon commented on JENKINS-20744 Don't hold off building until saved for jobs copied from CLI Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/cli/CopyJobCommand.java test/src/test/java/hudson/cli/CopyJobCommandTest.java http://jenkins-ci.org/commit/jenkins/19a2246fe67d938b7f4574dce9180b1d37bd3201 Log: [FIXED JENKINS-20744] Don't hold off building jobs copied from CLI This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cli] (JENKINS-20744) Don't hold off building until saved for jobs copied from CLI
SCM/JIRA link daemon resolved JENKINS-20744 as Fixed Don't hold off building until saved for jobs copied from CLI Change By: SCM/JIRA link daemon (25/Nov/13 9:58 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] [cli] (JENKINS-20744) Don't hold off building until saved for jobs copied from CLI
SCM/JIRA link daemon commented on JENKINS-20744 Don't hold off building until saved for jobs copied from CLI Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/cli/CopyJobCommand.java test/src/test/java/hudson/cli/CopyJobCommandTest.java http://jenkins-ci.org/commit/jenkins/67f2fe64098f0ff683d2242d48a272a1bfbb3488 Log: Merge pull request #1034 from daniel-beck/fix-copy-job-command [FIXED JENKINS-20744] Don't hold off building jobs copied from CLI This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [testlink] (JENKINS-20752) TestLink is unable to get the devKey
Jeanjean LaGuigne updated JENKINS-20752 TestLink is unable to get the devKey Change By: Jeanjean LaGuigne (25/Nov/13 10:02 AM) Description: Hi,i am making some test automation with Jenkins and testlink, but when I launch a build, Jenkins's build failed because the plugin testlink can't read the developer's key.This is the error output :Preparing TestLink client API.Using TestLink URL: https://testlink- test-transport compagnie . parkeon. com/lib/api/xmlrpc/v1/xmlrpc.phpFATAL: Error verifying developer key: Failed to read server's response: java.security.cert.CertificateException: No subject alternative DNS name matching testlink- test-transport compagnie . parkeon. com found.br.eti.kinoshita.testlinkjavaapi.util.TestLinkAPIException: Error verifying developer key: Failed to read server's response: java.security.cert.CertificateException: No subject alternative DNS name matching testlink- test-transport compagnie . parkeon. com found.I am using Testlink 1.9.8, Jenkins 1.536, testLink Plugin 3.8Plz help me Bruno ^^ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [extended-choice-parameter] (JENKINS-17262) Remotely triggered build with parameters failing with extended choice parameters
Bao Xiaopan(Bob) reopened JENKINS-17262 Remotely triggered build with parameters failing with extended choice parameters when I use remote trigger by using extended choice parameters plugin, I can't assign a value which not in the first value of the list, for e.g: the extended choice list is(param): a b c d "a" is the first value, when I use: curl -s www.xxx.com/joba/buildWithParameters?token=SecretOnlyForjoba\¶m=b" coz b is not the first value of the list, so the job can't recognized it. so job is fail... pls help to check whether this is a bug or not. Change By: Bao Xiaopan(Bob) (25/Nov/13 10:06 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extended-choice-parameter] (JENKINS-17262) Remotely triggered build with parameters failing with extended choice parameters
vimil commented on JENKINS-17262 Remotely triggered build with parameters failing with extended choice parameters Can you confirm you're using v0.28 of the 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] [jclouds-jenkins] (JENKINS-18173) JClouds fails accessing OpenStack-nova (java.lang.NullPointerException: tenant)
Jaroslav Henner commented on JENKINS-18173 JClouds fails accessing OpenStack-nova (java.lang.NullPointerException: tenant) Sorry to not updating this bug, but there is a way! Use tenantName:userName. I am leaving this bug open because I think the error message/inputs validation should be done better. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [jclouds-jenkins] (JENKINS-18173) JClouds fails accessing OpenStack-nova (java.lang.NullPointerException: tenant)
Jaroslav Henner commented on JENKINS-18173 JClouds fails accessing OpenStack-nova (java.lang.NullPointerException: tenant) I have also updated the JClouds plugin wiki to not let other people fall into same trap. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cli] (JENKINS-20744) Don't hold off building until saved for jobs copied from CLI
dogfood commented on JENKINS-20744 Don't hold off building until saved for jobs copied from CLI Integrated in jenkins_main_trunk #3076 [FIXED JENKINS-20744] Don't hold off building jobs copied from CLI (Revision 19a2246fe67d938b7f4574dce9180b1d37bd3201) Result = UNSTABLE daniel-beck : 19a2246fe67d938b7f4574dce9180b1d37bd3201 Files : test/src/test/java/hudson/cli/CopyJobCommandTest.java core/src/main/java/hudson/cli/CopyJobCommand.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-13869) [Unexpected termination of the channel] for Unix SSH slaves
Uldis Karlovs-Karlovskis commented on JENKINS-13869 [Unexpected termination of the channel] for Unix SSH slaves Hi, last Friday we upgraded to 1.540. Indeed, situation seems better but still we got one build failed with following error: 10:49:07 FATAL: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown 10:49:07 hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown 10:49:07 at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) 10:49:07 at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) 10:49:07 at hudson.remoting.Request.call(Request.java:174) 10:49:07 at hudson.remoting.Channel.call(Channel.java:722) 10:49:07 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167) 10:49:07 at $Proxy55.join(Unknown Source) 10:49:07 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:925) 10:49:07 at hudson.Launcher$ProcStarter.join(Launcher.java:360) 10:49:07 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:94) 10:49:07 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:63) 10:49:07 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 10:49:07 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) 10:49:07 at hudson.model.Build$BuildExecution.build(Build.java:199) 10:49:07 at hudson.model.Build$BuildExecution.doRun(Build.java:160) 10:49:07 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566) 10:49:07 at hudson.model.Run.execute(Run.java:1679) 10:49:07 at hudson.matrix.MatrixRun.run(MatrixRun.java:146) 10:49:07 at hudson.model.ResourceController.execute(ResourceController.java:88) 10:49:07 at hudson.model.Executor.run(Executor.java:230) 10:49:07 Caused by: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown 10:49:07 at hudson.remoting.Request.abort(Request.java:299) 10:49:07 at hudson.remoting.Channel.terminate(Channel.java:782) 10:49:07 at hudson.remoting.Channel$CloseCommand.execute(Channel.java:927) 10:49:07 at hudson.remoting.Channel$2.handle(Channel.java:461) 10:49:07 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) 10:49:07 Caused by: hudson.remoting.Channel$OrderlyShutdown 10:49:07 ... 3 more 10:49:07 Caused by: Command close created at 10:49:07 at hudson.remoting.Command.(Command.java:56) 10:49:07 at hudson.remoting.Channel$CloseCommand.(Channel.java:921) 10:49:07 at hudson.remoting.Channel$CloseCommand.(Channel.java:919) 10:49:07 at hudson.remoting.Channel.close(Channel.java:1002) 10:49:07 at hudson.remoting.Channel.close(Channel.java:985) 10:49:07 at hudson.remoting.Channel$CloseCommand.execute(Channel.java:926) 10:49:07 ... 2 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-20753) Explain "Append Hudson Build Number"
Anders Hammar created JENKINS-20753 Explain "Append Hudson Build Number" Issue Type: Improvement Assignee: teilo Components: m2release Created: 25/Nov/13 11:57 AM Description: It would be good with a help text (or at least in the plugin's page) explaining what the "Append Hudson Build Number" check box does. I looked at the code but can't see it being used. How is the build number appended? Environment: n/a Project: Jenkins Priority: Minor Reporter: Anders Hammar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-14405) When 'Discard old builds' is specified using 'Max # of builds to keep' in matrix job - all job history is deleted on master together with folder for the last label used
Adam H commented on JENKINS-14405 When 'Discard old builds' is specified using 'Max # of builds to keep' in matrix job - all job history is deleted on master together with folder for the last label used in the job Still in 1.522 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [jobconfighistory] (JENKINS-14295) WARNING: Called getInputStream after getParameter ... error
Adam H commented on JENKINS-14295 WARNING: Called getInputStream after getParameter ... error I can see this on Jenkins 1.522. Currently updating all my plugins to see if it changes anything. If it goes away I can provide a screenshot of before / after versions of my plugins. May this link be related? https://github.com/rhuss/jolokia/issues/25 Kind regards This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-pipeline] (JENKINS-19870) Status of the existing pipeline job is not updated after a failure or aborted build. Downstream job trigger is not enabled after the build succeeds
David Fuenmayor commented on JENKINS-19870 Status of the existing pipeline job is not updated after a failure or aborted build. Downstream job trigger is not enabled after the build succeeds Same issue on Jenkins LTS 1.509.4 with plugin version 1.4.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-19343) Always allow manual trigger on pipeline steps does not allow re-triggering
David Fuenmayor commented on JENKINS-19343 Always allow manual trigger on pipeline steps does not allow re-triggering Same issue with version 1.4.1 on Jenkins LTS 1.509.4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-14295) WARNING: Called getInputStream after getParameter ... error
Adam H commented on JENKINS-14295 WARNING: Called getInputStream after getParameter ... error Found another server with the error and much less plugins installed. It is also running 1.522. Here is a screenshot: http://i.imgur.com/Ta6iWL9.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
David Fuenmayor commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline I am getting exactly the same problem and stacktrace (version 1.4.1 with Jenkins LTS 1.509.4) After triggering the same downstream project from two different upstream projects Steps to reproduce: 1. Create a downstream project D 2. Create Projects A and B. As post-build action select "Build Other Projects (manual step)" and select for both: Project D. Add some predefined parameters: (e.g MY_VAR = VALUE) 3. Create two Build Pipeline Views: One for Project A and one for Project B 4. Trigger downstream project D from Project A using its corresponding Build Pipeline View 5. Trigger downstream project D from Project B using its corresponding Build Pipeline View 6. Repeat 4 and 5 a couple of times. D runs broken and cannot be aborted This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [jacoco] (JENKINS-20754) Jacoco coverage reports built from Jenkins are inconsistent.
Joel Costigliola created JENKINS-20754 Jacoco coverage reports built from Jenkins are inconsistent. Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco Created: 25/Nov/13 12:29 PM Description: I have a maven multi module project and I want my build to fail if code coverage is insufficient. I'm using jacoco maven plugin for this, I had no problem with local builds but when building my project on Jenkins I have found jacoco reports to be inconsistent. This is a blocking problem to me because the build fails when coverage expectations are not met. Here's two extract of failed build with no SCM changes between them. build #89 [WARNING] Insufficient code coverage for COMPLEXITY: 60,52% < 63,14% [WARNING] Insufficient code coverage for METHOD: 64,28% < 67,84% build #90 [WARNING] Insufficient code coverage for BRANCH: 70,00% < 75,00% [WARNING] Insufficient code coverage for COMPLEXITY: 57,89% < 63,14% [WARNING] Insufficient code coverage for METHOD: 64,28% < 67,84% Previous build was successful with the same code coverage expectations. I have tried with different jacoco versions (0.6.2.201302030002 and 0.6.3.201306030806) without luck. I have reported this problem in jenkins issue tracker since I have only seen it my Jenkins build and not in my local builds but I may be wrong. I understand this is not easy to fix or investigate, I just thought it was important to report it. Kind regards, Joel Environment: Jenkins version: 1.523 Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100) Maven home: C:\webintlab\apache-maven-3.0.5 Java version: 1.7.0_15, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.7.0_15\jre Default locale: fr_FR, platform encoding: Cp1252 OS name: "windows server 2008", version: "6.0", arch: "amd64", family: "windows" Project: Jenkins Priority: Critical Reporter: Joel Costigliola This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [deploy] (JENKINS-20755) After Installation
mack james created JENKINS-20755 After Installation Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: deploy Created: 25/Nov/13 12:52 PM Description: After installation, it keeps on browsing and showing message: "Please wait while Jenkins is getting ready to work.. Your browser will reload automatically when Jenkins is ready." How much time it takes to load? it's been 4-5 hours since it is showing this message. Due Date: 26/Nov/13 12:00 AM Fix Versions: current Project: Jenkins Priority: Critical Reporter: mack james This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20675) Java platform binary has stopped working message appears when starting Jenkins 1.540
Jean-Francois Allot commented on JENKINS-20675 Java platform binary has stopped working message appears when starting Jenkins 1.540 Same issue with the just release 1.541 version. Child process [4996 - D:\Jenkins\jre\bin\java -Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "D:\Jenkins\jenkins.war" --httpPort=8080 --prefix=/jenkins -Djava.io.tmpdir="D:\Jenkins/temp"] terminated with 255 Faulting application name: java.exe, version: 7.0.250.17, time stamp: 0x51c4b3fd Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521ea8e7 Exception code: 0xc374 Fault offset: 0x000ce753 Faulting process id: 0x1384 Faulting application start time: 0x01cee9de3a902f8d Faulting application path: D:\Jenkins\jre\bin\java.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: 97ccae38-55d1-11e3-a661-005056ae0038 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [delivery-pipeline] (JENKINS-20756) Dont work with Folders plugin
Patrik Boström created JENKINS-20756 Dont work with Folders plugin Issue Type: Bug Assignee: Unassigned Components: delivery-pipeline Created: 25/Nov/13 1:24 PM Description: Plugin does not work with Folders plugin https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Folders+Plugin Project: Jenkins Priority: Major Reporter: Patrik Boström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [delivery-pipeline] (JENKINS-20756) Dont work with Folders plugin
Patrik Boström assigned JENKINS-20756 to Patrik Boström Dont work with Folders plugin Change By: Patrik Boström (25/Nov/13 1:24 PM) Assignee: Patrik Boström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [delivery-pipeline] (JENKINS-20756) Dont work with Folders plugin
Patrik Boström commented on JENKINS-20756 Dont work with Folders plugin Fixed https://github.com/Diabol/delivery-pipeline-plugin/commit/2669c2ce5ea22f8262d6022f0c54c950b9561b4a This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-19978) Cannot run maven x.x builds after LTS 1.509.4 upgrade because of InvalidClassException PlexusModuleContributorFactory
Rainer Weinhold commented on JENKINS-19978 Cannot run maven x.x builds after LTS 1.509.4 upgrade because of InvalidClassException PlexusModuleContributorFactory The Exception is now different with your Version (2.0-beta-2-SNAPSHOT (private-10/21/2013 19:02-kutzi)): Total time: 30.412 secs FATAL: hudson.maven.MavenBuild.pickArtifactManager()Ljenkins/model/ArtifactManager; java.lang.NoSuchMethodError: hudson.maven.MavenBuild.pickArtifactManager()Ljenkins/model/ArtifactManager; at hudson.maven.MavenBuild$ProxyImpl.performArchiving(MavenBuild.java:455) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:825) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:565) at hudson.model.Run.execute(Run.java:1592) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-19978) Cannot run maven x.x builds after LTS 1.509.4 upgrade because of InvalidClassException PlexusModuleContributorFactory
Rainer Weinhold reopened JENKINS-19978 Cannot run maven x.x builds after LTS 1.509.4 upgrade because of InvalidClassException PlexusModuleContributorFactory fix does not run on lts. Change By: Rainer Weinhold (25/Nov/13 1:49 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [crowd2] (JENKINS-18153) Crowd2 Plugin Authenticates user, but does not log user in
Kanstantsin Shautsou resolved JENKINS-18153 as Cannot Reproduce Crowd2 Plugin Authenticates user, but does not log user in Change By: Kanstantsin Shautsou (25/Nov/13 1:55 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20757) jenkins startup dies quickly ostensibly due to maven problem in 1.540 and 1.541
warren brown created JENKINS-20757 jenkins startup dies quickly ostensibly due to maven problem in 1.540 and 1.541 Issue Type: Bug Assignee: Unassigned Components: maven Created: 25/Nov/13 2:08 PM Description: Jenkins v1.539 is ok. Failures began in 1.540 and continue in 1.541; ergo, newer Jenkins versions are unusable. INFO: Listed all plugins Nov 25, 2013 8:52:53 AM jenkins.InitReactorRunner$1 onAttained INFO: Prepared all plugins Nov 25, 2013 8:52:53 AM jenkins.InitReactorRunner$1 onAttained INFO: Started all plugins Nov 25, 2013 8:52:53 AM jenkins.InitReactorRunner$1 onAttained INFO: Augmented all extensions Nov 25, 2013 8:52:55 AM hudson.ExtensionFinder$Sezpoz scout WARNING: Failed to scout hudson.maven.MavenModuleSet java.lang.NoClassDefFoundError: hudson/tasks/JavadocArchiver at hudson.maven.MavenModuleSet$DescriptorImpl.(MavenModuleSet.java:1320) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:680) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:310) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:309) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.get(ExtensionList.java:153) at jenkins.plugins.htmlaudio.app.HtmlAudioNotifierPlugin.getComponent(HtmlAudioNotifierPlugin.java:66) at jenkins.plugins.htmlaudio.app.HtmlAudioNotifierPlugin.initializePlugin(HtmlAudioNotifierPlugin.java:46) 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 hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:896) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.ClassNotFoundException: hudson.tasks.JavadocArchiver at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1365) at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1315) at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1068) at java.lang.ClassLoader.loadClass(Unknown Source) ... 27 more Nov 25, 2013 8:52:59 AM hudson.ExtensionFinder$GuiceFinder instantiate WARNING: Failed to load hudson.maven.MavenModuleSet java.lang.InstantiationException: java.lang.NoClassDefFoundError: Could not initialize class hudson.maven.MavenModuleSet$DescriptorImpl at net.java.sezpoz.IndexItem.instance(IndexItem.java:193) at hudson.ExtensionFinder$GuiceFinder.instantiate(ExtensionFinder.java:355) at hudson.ExtensionFinder$GuiceFinder.access$700(ExtensionFinder.java:234) at hudson.ExtensionFinder$GuiceFinder$SezpozModule$1.get(ExtensionFinder.java:531) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:55) at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:66) at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java
[JIRA] [core] (JENKINS-5622) Allow build queue list to be collapsed
SCM/JIRA link daemon commented on JENKINS-5622 Allow build queue list to be collapsed Code changed in jenkins User: Bruno Kühnen Meneguello Path: core/src/main/java/hudson/Functions.java core/src/main/java/hudson/model/PaneStatusProperties.java core/src/main/java/jenkins/model/Jenkins.java core/src/main/resources/lib/hudson/executors.jelly core/src/main/resources/lib/hudson/executors.properties core/src/main/resources/lib/hudson/executors_pt_BR.properties core/src/main/resources/lib/hudson/queue.jelly core/src/main/resources/lib/hudson/queue.properties core/src/main/resources/lib/hudson/queue_ar.properties core/src/main/resources/lib/hudson/queue_be.properties core/src/main/resources/lib/hudson/queue_bg.properties core/src/main/resources/lib/hudson/queue_bn_IN.properties core/src/main/resources/lib/hudson/queue_ca.properties core/src/main/resources/lib/hudson/queue_cs.properties core/src/main/resources/lib/hudson/queue_da.properties core/src/main/resources/lib/hudson/queue_de.properties core/src/main/resources/lib/hudson/queue_el.properties core/src/main/resources/lib/hudson/queue_eo.properties core/src/main/resources/lib/hudson/queue_es.properties core/src/main/resources/lib/hudson/queue_es_AR.properties core/src/main/resources/lib/hudson/queue_et.properties core/src/main/resources/lib/hudson/queue_eu.properties core/src/main/resources/lib/hudson/queue_fi.properties core/src/main/resources/lib/hudson/queue_fr.properties core/src/main/resources/lib/hudson/queue_ga_IE.properties core/src/main/resources/lib/hudson/queue_he.properties core/src/main/resources/lib/hudson/queue_hi_IN.properties core/src/main/resources/lib/hudson/queue_hu.properties core/src/main/resources/lib/hudson/queue_id.properties core/src/main/resources/lib/hudson/queue_is.properties core/src/main/resources/lib/hudson/queue_it.properties core/src/main/resources/lib/hudson/queue_ja.properties core/src/main/resources/lib/hudson/queue_ka.properties core/src/main/resources/lib/hudson/queue_kn.properties core/src/main/resources/lib/hudson/queue_ko.properties core/src/main/resources/lib/hudson/queue_lt.properties core/src/main/resources/lib/hudson/queue_lv.properties core/src/main/resources/lib/hudson/queue_mn.properties core/src/main/resources/lib/hudson/queue_mr.properties core/src/main/resources/lib/hudson/queue_nb_NO.properties core/src/main/resources/lib/hudson/queue_nl.properties core/src/main/resources/lib/hudson/queue_pl.properties core/src/main/resources/lib/hudson/queue_pt_BR.properties core/src/main/resources/lib/hudson/queue_pt_PT.properties core/src/main/resources/lib/hudson/queue_ro.properties core/src/main/resources/lib/hudson/queue_ru.properties core/src/main/resources/lib/hudson/queue_si.properties core/src/main/resources/lib/hudson/queue_sk.properties core/src/main/resources/lib/hudson/queue_sl.properties core/src/main/resources/lib/hudson/queue_sr.properties core/src/main/resources/lib/hudson/queue_sv_SE.properties core/src/main/resources/lib/hudson/queue_ta.properties core/src/main/resources/lib/hudson/queue_te.properties core/src/main/resources/lib/hudson/queue_th.properties core/src/main/resources/lib/hudson/queue_tr.properties core/src/main/resources/lib/hudson/queue_uk.properties core/src/main/resources/lib/hudson/queue_zh_CN.properties core/src/main/resources/lib/hudson/queue_zh_TW.properties core/src/main/resources/lib/layout/pane.jelly war/src/main/webapp/css/style.css war/src/main/webapp/images/16x16/collapse.png war/src/main/webapp/images/16x16/expand.png http://jenkins-ci.org/commit/jenkins/cdf45c6439c9aa5f87dd06e477a732f26fd420ad Log: [FIXED JENKINS-5622] Allow build queue list to be collapsed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-5622) Allow build queue list to be collapsed
SCM/JIRA link daemon commented on JENKINS-5622 Allow build queue list to be collapsed Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/Functions.java core/src/main/java/hudson/model/PaneStatusProperties.java core/src/main/java/jenkins/model/Jenkins.java core/src/main/resources/lib/hudson/executors.jelly core/src/main/resources/lib/hudson/executors.properties core/src/main/resources/lib/hudson/executors_pt_BR.properties core/src/main/resources/lib/hudson/queue.jelly core/src/main/resources/lib/hudson/queue.properties core/src/main/resources/lib/hudson/queue_ar.properties core/src/main/resources/lib/hudson/queue_be.properties core/src/main/resources/lib/hudson/queue_bg.properties core/src/main/resources/lib/hudson/queue_bn_IN.properties core/src/main/resources/lib/hudson/queue_ca.properties core/src/main/resources/lib/hudson/queue_cs.properties core/src/main/resources/lib/hudson/queue_da.properties core/src/main/resources/lib/hudson/queue_de.properties core/src/main/resources/lib/hudson/queue_el.properties core/src/main/resources/lib/hudson/queue_eo.properties core/src/main/resources/lib/hudson/queue_es.properties core/src/main/resources/lib/hudson/queue_es_AR.properties core/src/main/resources/lib/hudson/queue_et.properties core/src/main/resources/lib/hudson/queue_eu.properties core/src/main/resources/lib/hudson/queue_fi.properties core/src/main/resources/lib/hudson/queue_fr.properties core/src/main/resources/lib/hudson/queue_ga_IE.properties core/src/main/resources/lib/hudson/queue_he.properties core/src/main/resources/lib/hudson/queue_hi_IN.properties core/src/main/resources/lib/hudson/queue_hu.properties core/src/main/resources/lib/hudson/queue_id.properties core/src/main/resources/lib/hudson/queue_is.properties core/src/main/resources/lib/hudson/queue_it.properties core/src/main/resources/lib/hudson/queue_ja.properties core/src/main/resources/lib/hudson/queue_ka.properties core/src/main/resources/lib/hudson/queue_kn.properties core/src/main/resources/lib/hudson/queue_ko.properties core/src/main/resources/lib/hudson/queue_lt.properties core/src/main/resources/lib/hudson/queue_lv.properties core/src/main/resources/lib/hudson/queue_mn.properties core/src/main/resources/lib/hudson/queue_mr.properties core/src/main/resources/lib/hudson/queue_nb_NO.properties core/src/main/resources/lib/hudson/queue_nl.properties core/src/main/resources/lib/hudson/queue_pl.properties core/src/main/resources/lib/hudson/queue_pt_BR.properties core/src/main/resources/lib/hudson/queue_pt_PT.properties core/src/main/resources/lib/hudson/queue_ro.properties core/src/main/resources/lib/hudson/queue_ru.properties core/src/main/resources/lib/hudson/queue_si.properties core/src/main/resources/lib/hudson/queue_sk.properties core/src/main/resources/lib/hudson/queue_sl.properties core/src/main/resources/lib/hudson/queue_sr.properties core/src/main/resources/lib/hudson/queue_sv_SE.properties core/src/main/resources/lib/hudson/queue_ta.properties core/src/main/resources/lib/hudson/queue_te.properties core/src/main/resources/lib/hudson/queue_th.properties core/src/main/resources/lib/hudson/queue_tr.properties core/src/main/resources/lib/hudson/queue_uk.properties core/src/main/resources/lib/hudson/queue_zh_CN.properties core/src/main/resources/lib/hudson/queue_zh_TW.properties core/src/main/resources/lib/layout/pane.jelly war/src/main/webapp/css/style.css war/src/main/webapp/images/16x16/collapse.png war/src/main/webapp/images/16x16/expand.png http://jenkins-ci.org/commit/jenkins/6ed2cbf9fa8bf0f84961a2324d59174297273558 Log: Merge pull request #1014 from bkmeneguello/collapsible-panes [DONE] [FIXED JENKINS-5622] Allow build queue list to be collapsed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-5622) Allow build queue list to be collapsed
SCM/JIRA link daemon resolved JENKINS-5622 as Fixed Allow build queue list to be collapsed Change By: SCM/JIRA link daemon (25/Nov/13 2:20 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-20569) Polling with excluded regions don't prevent job triggered
Erik Cokeley commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered I also need the Included Regions. This is failing for me. What version has Included Region (or excluded region) working? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Erik Cokeley edited a comment on JENKINS-20569 Polling with excluded regions don't prevent job triggered I also need the Included Regions. This is failing for me and many builds are being kicked off; I'm not sure if all my builds within the git and branch but at least many. What version has Included Region (or excluded region) working? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Guillaume Jean commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity I have the same problem with version 1.540 on Mac Os X 10.9 Sincerely GJean This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20630) Jenkins fails to start
Shannon Kerr edited a comment on JENKINS-20630 Jenkins fails to start @Gemini just to clarify, by "weekly builds" I was referring to the weekly Jenkins "Latest and Greatest" release in case some people didn't catch that. My only point was that, because my experience using the weekly Jenkins releases have sometimes been more hit than miss, I rely on the user evals before ever taking a weekly and if I wanted something stable, I would take the "Long-Term Support Release" that say they are "Older but stable" Jenkins releases. I don't disagree that if the Jenkins weekly builds are going to have stability issues as significant as 1.540 that a more explicit warning on the download page or changelog is warranted. I don't need it myself as I already understand that instability is very likely and the "Older but stable" remark on the LTS download page made it clear to me that that is where the stability is. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [jobconfighistory] (JENKINS-20220) config history diff does not work for jobs in folders
Walter Kacynski commented on JENKINS-20220 config history diff does not work for jobs in folders I don't know what changed or what happened but this is working correctly for me under Plugin version 2.5 Maybe this is because I moved the jobs into folders and the history backing them, which I store in a different directory, did not move with them. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-5622) Allow build queue list to be collapsed
dogfood commented on JENKINS-5622 Allow build queue list to be collapsed Integrated in jenkins_main_trunk #3077 [FIXED JENKINS-5622] Allow build queue list to be collapsed (Revision cdf45c6439c9aa5f87dd06e477a732f26fd420ad) Result = SUCCESS bruno : cdf45c6439c9aa5f87dd06e477a732f26fd420ad Files : war/src/main/webapp/images/16x16/expand.png core/src/main/resources/lib/hudson/queue_ko.properties core/src/main/java/hudson/model/PaneStatusProperties.java core/src/main/resources/lib/hudson/queue_ja.properties core/src/main/resources/lib/hudson/queue_ca.properties core/src/main/resources/lib/hudson/queue_sk.properties core/src/main/resources/lib/hudson/queue_eu.properties core/src/main/resources/lib/hudson/queue_pt_BR.properties core/src/main/resources/lib/hudson/queue_be.properties core/src/main/resources/lib/hudson/queue_kn.properties core/src/main/resources/lib/hudson/queue_mn.properties core/src/main/resources/lib/hudson/queue_hu.properties core/src/main/resources/lib/hudson/queue_si.properties core/src/main/resources/lib/hudson/queue_pt_PT.properties core/src/main/resources/lib/hudson/queue_sv_SE.properties core/src/main/resources/lib/hudson/queue_th.properties core/src/main/resources/lib/hudson/queue_it.properties core/src/main/resources/lib/hudson/queue_sl.properties core/src/main/resources/lib/hudson/queue_sr.properties core/src/main/resources/lib/hudson/queue_ro.properties core/src/main/resources/lib/hudson/executors_pt_BR.properties core/src/main/resources/lib/hudson/queue_pl.properties core/src/main/resources/lib/hudson/queue_lt.properties core/src/main/resources/lib/hudson/queue_id.properties core/src/main/resources/lib/hudson/queue_de.properties core/src/main/resources/lib/hudson/queue_ru.properties core/src/main/resources/lib/hudson/queue_fr.properties core/src/main/resources/lib/hudson/queue_et.properties core/src/main/java/jenkins/model/Jenkins.java core/src/main/resources/lib/hudson/queue_ka.properties core/src/main/resources/lib/hudson/queue_mr.properties core/src/main/resources/lib/hudson/queue_he.properties core/src/main/resources/lib/hudson/queue_ar.properties core/src/main/resources/lib/hudson/queue_es.properties core/src/main/resources/lib/hudson/queue_bn_IN.properties core/src/main/resources/lib/hudson/queue_uk.properties core/src/main/resources/lib/layout/pane.jelly core/src/main/resources/lib/hudson/queue_ga_IE.properties core/src/main/resources/lib/hudson/queue_lv.properties core/src/main/resources/lib/hudson/queue_te.properties core/src/main/resources/lib/hudson/queue_nb_NO.properties core/src/main/resources/lib/hudson/queue_es_AR.properties core/src/main/resources/lib/hudson/queue_bg.properties core/src/main/resources/lib/hudson/queue_zh_CN.properties core/src/main/resources/lib/hudson/queue_is.properties core/src/main/resources/lib/hudson/queue_tr.properties core/src/main/resources/lib/hudson/queue_nl.properties core/src/main/resources/lib/hudson/queue_da.properties core/src/main/resources/lib/hudson/queue_el.properties core/src/main/resources/lib/hudson/queue_ta.properties war/src/main/webapp/images/16x16/collapse.png core/src/main/resources/lib/hudson/queue_hi_IN.properties core/src/main/resources/lib/hudson/queue_cs.properties core/src/main/resources/lib/hudson/queue.jelly core/src/main/resources/lib/hudson/queue.properties core/src/main/java/hudson/Functions.java core/src/main/resources/lib/hudson/queue_fi.properties core/src/main/resources/lib/hudson/queue_eo.properties core/src/main/resources/lib/hudson/executors.properties war/src/main/webapp/css/style.css core/src/main/resources/lib/hudson/queue_zh_TW.properties core/src/main/resources/lib/hudson/executors.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Hal Deadman commented on JENKINS-20630 Jenkins fails to start I was having the problem with older versions of Java 7 and Java 6. It must be a general issue with Java on windows (and is triggered by something new in Jenkins). I was getting the crash on a Windows 2003 32-bit virtual machine. Specific versions of Java don't appear to be a factor and people have seen the problem on Windows 7, Windows 8, 2008, 2003, and 64bit and 32bit. The common thread appears to be a crash on windows during finalization and it occurs pretty quickly during startup. I have lots of plugins but it sounds like at least some people have gotten the problem by just running the latest war by itself on a fresh install. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20630) Jenkins fails to start
boris ivan commented on JENKINS-20630 Jenkins fails to start Does anyone use Windows and not see this problem? I can't make the problem go away regardless what version of Windows/Java we use. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Matt Kraai commented on JENKINS-20630 Jenkins fails to start Jenkins 1.541 also fails to start in the same way. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xfpanel] (JENKINS-20749) Some jobs are missing in "Available jobs" multichoice window
emanuelez updated JENKINS-20749 Some jobs are missing in "Available jobs" multichoice window Changed component. Change By: emanuelez (25/Nov/13 5:18 PM) Component/s: xfpanel Component/s: extreme-feedback This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
João Vale commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Same problem here, with the same NullPointerException. CentOS 6.4 Jenkins 1.536 Build Pipeline 1.4.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] [core] (JENKINS-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
Jirong Hu commented on JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves I am having the same issue when trying to install Jenkins 1.541 on my Windows XP. It's a brand new installation, found no timestamper plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xvfb] (JENKINS-20758) Xvfb processes remain after slave disconnect
Jonathan Rogers created JENKINS-20758 Xvfb processes remain after slave disconnect Issue Type: Bug Affects Versions: current Assignee: zregvart Components: xvfb Created: 25/Nov/13 5:52 PM Description: When a connection to a slave is unexpectedly broken during a build, an Xvfb process started by the plugin is not killed. After the slave is reconnected, subsequent builds on it fail immediately because the plugin tries to start a new Xvfb process on the same display as the old one. It would be helpful if the plugin could kill left over Xvfb processes before trying to start a new one. There could be a configuration option to kill all Xvfb processes. More robustly, it could probably find just the problematic one by command line. 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-20550) download artifacts is very slow
Petr H commented on JENKINS-20550 download artifacts is very slow I confirm the same. 1.538 here. I had to replace the trilead-ssh2-build217-jenkins-3.jar library with older trilead-ssh2-build214-jenkins-3.jar from 1.536 which significantly improved performance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20550) download artifacts is very slow
Petr H edited a comment on JENKINS-20550 download artifacts is very slow I confirm the same. 1.538 here. I had to replace the trilead-ssh2-build217-jenkins-3.jar library with older trilead-ssh2-build214-jenkins-3.jar from 1.535 which significantly improved performance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [deploy] (JENKINS-18257) Parameters and enviroment variables in the context root field
Darrell Lowrance commented on JENKINS-18257 Parameters and enviroment variables in the context root field Please add support for this feature. It's actually very surprising to learn that this plugin has never supported Jenkins/Hudson variables. Thanks in advance. See duplicate request at https://issues.jenkins-ci.org/browse/JENKINS-5790 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [deploy] (JENKINS-5790) Parameterize Tomcat Context Path and URL Fields
Darrell Lowrance commented on JENKINS-5790 Parameterize Tomcat Context Path and URL Fields Please add support for this feature. It's actually very surprising to learn that this plugin has never supported Jenkins/Hudson variables. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [deploy] (JENKINS-5790) Parameterize Tomcat Context Path and URL Fields
Darrell Lowrance commented on JENKINS-5790 Parameterize Tomcat Context Path and URL Fields See similar/duplicate request at https://issues.jenkins-ci.org/browse/JENKINS-18257 Thanks in advance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18935) Make Subversion plugin support Subversion 1.8
centic updated JENKINS-18935 Make Subversion plugin support Subversion 1.8 Added some status to the description... Change By: centic (25/Nov/13 8:21 PM) Description: Subversion 1.8 is available but the SVN plugin doesn't support it. For example, Configure|Subversion Workspace Version only offers 1.4 thru 1.7.https://issues.jenkins-ci.org/browse/JENKINS-18844 is related. To summarize this instead of having to browse through all the comments:* Talking to a Subversion 1.8 Server should work fine, however the local working copy will still be SVN <=1.7* Checking out in Subversion 1.8 Working Copy format does not work, because the version of svnkit that is used in the Subversion plugin (1.7.10) does not support Subversion 1.8 Working CopyThings that need to be done to make this work:* There is a RC1 of svnkit 1.8.0, which will support Subversion 1.8, see http://svnkit.com/download.php* Updating to this version and adding "1.8" to the checkbox in the Jenkins Server configuration should be most of what is needed to make it work* Unfortunately the Subversion plugin uses a patched version of svnkit, see https://github.com/jenkinsci/svnkit, merging the patches and the newer svnkit requires probably some work, depending on the amount of changes in svnkit upstream* As soon as org.jenkins-ci.svnkit is updated to 1.8.x, the Subversion plugin can upgrade to this and use Subversion 1.8 Working Copy format This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [all-changes] (JENKINS-20759) On windows slaves, occasional crash after successful build: Failed to write winp.x64.dll
boris ivan created JENKINS-20759 On windows slaves, occasional crash after successful build: Failed to write winp.x64.dll Issue Type: Bug Affects Versions: current Assignee: wolfs Components: all-changes Created: 25/Nov/13 9:21 PM Description: Occasionally, remote windows slaves die with the following trace spit to the screen on the remote slave (I am running via command line, not as a service): Nov 20, 2013 4:16:10 PM org.jvnet.winp.Native load WARNING: Failed to write winp.x64.dll java.io.FileNotFoundException: C:\Users\\.jenkins\cache\jars\01\winp.x64.dll (The process can not access the file because it is being used by another process) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:212) at java.io.FileOutputStream.(FileOutputStream.java:165) at org.jvnet.winp.Native.load(Native.java:81) at org.jvnet.winp.Native.(Native.java:52) at org.jvnet.winp.WinProcess.enableDebugPrivilege(WinProcess.java:200) at hudson.util.ProcessTree$Windows.(ProcessTree.java:477) at hudson.util.ProcessTree.get(ProcessTree.java:336) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:899) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:890) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:724) # A fatal error has been detected by the Java Runtime Environment: # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x0c8b3a90, pid=7136, tid=2024 # JRE version: 7.0_25-b17 Java VM: Java HotSpot(TM) 64-Bit Server VM (23.25-b01 mixed mode windows-amd64 compressed oops) Problematic frame: C 0x0c8b3a90 # Core dump written. Default location: C:hs_err_pid7136.mdmp # An error report file with more information is saved as: C:hs_err_pid7136.log When this occurs, here's the trailing end of the build console for this build: ... ... [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 1:33.420s [INFO] Finished at: Wed Nov 20 16:16:09 EST 2013 [INFO] Final Memory: 42M/272M [INFO] [JENKINS] Archiving C:\jenkins\workspace\\pom.xml to SNAPSHOT.pom [JENKINS] Archiving C:\jenkins\workspace\-SNAPSHOT.jar to jar channel stopped FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:714) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:887) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585) at hudson.model.Run.execute(Run.java:1679) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Caused by: hudson.remoting.RequestAbortedException: java.net.SocketEx
[JIRA] [jacoco] (JENKINS-20754) Jacoco coverage reports built from Jenkins are inconsistent.
Ognjen Bubalo commented on JENKINS-20754 Jacoco coverage reports built from Jenkins are inconsistent. Hi, Which JaCoCo Jenkins plugin version do you use? Ogi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [all-changes] (JENKINS-20759) On windows slaves, occasional crash after successful build: Failed to write winp.x64.dll
boris ivan
updated JENKINS-20759
On windows slaves, occasional crash after successful build: Failed to write winp.x64.dll
Change By:
boris ivan
(25/Nov/13 9:29 PM)
Description:
Occasionally, remote windows slaves die with the following trace spit to the screen on the remote slave (I am running via command line, not as a service):
{noformat}
Nov 20, 2013 4:16:10 PM org.jvnet.winp.Native loadWARNING: Failed to write winp.x64.dlljava.io.FileNotFoundException: C:\Users\\.jenkins\cache\jars\01\winp.x64.dll (The process can not access the file because it is being used by another process)at java.io.FileOutputStream.open(Native Method)at java.io.FileOutputStream.(FileOutputStream.java:212)at java.io.FileOutputStream.(FileOutputStream.java:165)at org.jvnet.winp.Native.load(Native.java:81)at org.jvnet.winp.Native.(Native.java:52)at org.jvnet.winp.WinProcess.enableDebugPrivilege(WinProcess.java:200)at hudson.util.ProcessTree$Windows.(ProcessTree.java:477)at hudson.util.ProcessTree.get(ProcessTree.java:336)at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:899)at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:890)at hudson.remoting.UserRequest.perform(UserRequest.java:118)at hudson.remoting.UserRequest.perform(UserRequest.java:48)at hudson.remoting.Request$2.run(Request.java:326)at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)at java.util.concurrent.FutureTask.run(FutureTask.java:166)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at hudson.remoting.Engine$1$1.run(Engine.java:63)at java.lang.Thread.run(Thread.java:724)## A fatal error has been detected by the Java Runtime Environment:## EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x0c8b3a90, pid=7136, tid=2024## JRE version: 7.0_25-b17# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.25-b01 mixed mode windows-amd64 compressed oops)# Problematic frame:# C 0x0c8b3a90## Core dump written. Default location: C:\\hs_err_pid7136.mdmp## An error report file with more information is saved as:# C:\\hs_err_pid7136.log
{noformat}
When this occurs, here's the trailing end of the build console for this build:
{noformat}
..[INFO] BUILD SUCCESS[INFO] [INFO] Total time: 1:33.420s[INFO] Finished at: Wed Nov 20 16:16:09 EST 2013[INFO] Final Memory: 42M/272M[INFO] [JENKINS] Archiving C:\jenkins\workspace\\pom.xml to SNAPSHOT.pom[JENKINS] Archiving C:\jenkins\workspace\-SNAPSHOT.jar to jarchannel stoppedFATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection resethudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:714) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:887) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585) at hudson.model.Run.execute(Run.java:1679) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230)Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:774) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)Caused by: java.net.SocketException: Connection reset at java.net
[JIRA] [all-changes] (JENKINS-20759) On windows slaves, occasional crash after successful build: Failed to write winp.x64.dll
boris ivan updated JENKINS-20759 On windows slaves, occasional crash after successful build: Failed to write winp.x64.dll crashdump log file Change By: boris ivan (25/Nov/13 9:33 PM) Attachment: hs_err_pid7136.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [jacoco] (JENKINS-19915) Support specifying one or more JARs in the classPattern
David Miller
commented on JENKINS-19915
Support specifying one or more JARs in the classPattern
I recently started to try out the Jenkins JaCoCo plug-in, specified a directory ("Path to class directories") that contained only jar files, and it worked OK.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [role-strategy] (JENKINS-8075) Assign role interface does not scale to large number of users and roles
Daniel Beck commented on JENKINS-8075 Assign role interface does not scale to large number of users and roles Published my own userscripts at https://github.com/daniel-beck/jenkins-userscripts Added to wiki page for Role Strategy, rewrote the note a bit to make that work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [jacoco] (JENKINS-19621) Plug-in configuration is inflexible and counter-intuitive
David Miller commented on JENKINS-19621 Plug-in configuration is inflexible and counter-intuitive To add to the counter-intuitive piece: We don't have access to source in our automation, so I left the "Path to source directories" blank. Much to my chagrin, the plug-in interpreted that as the workspace directory, so each build saved off the entire workspace directory, 3GB in our case. I assumed a blank field meant you didn't have sources. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameters] (JENKINS-20760) On the job config scree, allow the the parameters section to be collapsed
Stuart Whelan created JENKINS-20760 On the job config scree, allow the the parameters section to be collapsed Issue Type: Improvement Assignee: Unassigned Components: parameters Created: 25/Nov/13 9:59 PM Description: Our projects have 30ish parameters defined, it can be frustrating scroll down past them all. Please allow the Parameters section to be collapsed. Project: Jenkins Labels: parameter collapsing-section Priority: Minor Reporter: Stuart Whelan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
Henrik Skupin commented on JENKINS-19994 Unable to delete workspace Our own specific instance of the failure I'm also tracking at https://github.com/mozilla/mozmill-ci/issues/358. If I read the stack attached over there correctly, the failure is not inside of the delete workspace plugin, but in core. So the delete workspace plugin and other tasks like rotate log can't get a handle for their operations because the file is locked. We will further investigate it the next days. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameters] (JENKINS-20760) On the job config screen, allow the the parameters section to be collapsed
Stuart Whelan updated JENKINS-20760 On the job config screen, allow the the parameters section to be collapsed Change By: Stuart Whelan (25/Nov/13 11:23 PM) Summary: On the job config scree screen , allow the the parameters section to be collapsed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [multiple-scms] (JENKINS-20647) Uncaught TypeError: Cannot read property 'click' of undefined (when trying to add mercurial repo)
Jeff DeWan
commented on JENKINS-20647
Uncaught TypeError: Cannot read property 'click' of undefined (when trying to add mercurial repo)
I am experiencing the same behavior with a similar TypeError message in Firefox 25.0.1:
TypeError: this._events is undefined
...resetConfig();},subscribe:function(b,c){this._events=this._events||{};if(!(b in ...
element-min.js (line 7)
The Jenkins server is v1.541. I can add other repository types (svn, git, cvs) just fine, only Mercurial seems to be a problem.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-20630) Jenkins fails to start
Arpit Nagar commented on JENKINS-20630 Jenkins fails to start Same issue with us as well. please provide a Fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [role-strategy] (JENKINS-8075) Assign role interface does not scale to large number of users and roles
Oleg Nenashev commented on JENKINS-8075 Assign role interface does not scale to large number of users and roles Thanks a lot, Daniel I hope to implement a built-in support of such layout at some point. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-10709) multiple builds are triggered for one change in Gerrit
Vlad Aginsky commented on JENKINS-10709 multiple builds are triggered for one change in Gerrit Hi Hugo and all, I still observe this on version 1.535, ang gerrit trigger 2.10.1. What release was supposed to contain the solution? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Jason Yang commented on JENKINS-20630 Jenkins fails to start have the same issue: windows sever 2003 R2 vmvare tomcat 7.0 JRE 1.7.0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [mercurial] (JENKINS-5396) Support tags instead of branches
Hermien Pellissier commented on JENKINS-5396 Support tags instead of branches Any news on this implementation yet? We also need this feature. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [testlink] (JENKINS-20752) TestLink is unable to get the devKey
Jeanjean LaGuigne updated JENKINS-20752 TestLink is unable to get the devKey Change By: Jeanjean LaGuigne (26/Nov/13 7:47 AM) Description: Hi,i am making some test automation with Jenkins and testlink, but when I launch a build, Jenkins's build failed because the plugin testlink can't read the developer's key.This is the error output :Preparing TestLink client API.Using TestLink URL: https://testlink-compagnie.com/lib/api/xmlrpc/v1/xmlrpc.phpFATAL: Error verifying developer key: Failed to read server's response: java.security.cert.CertificateException: No subject alternative DNS name matching testlink-compagnie.com found.br.eti.kinoshita.testlinkjavaapi.util.TestLinkAPIException: Error verifying developer key: Failed to read server's response: java.security.cert.CertificateException: No subject alternative DNS name matching testlink-compagnie.com found. --and if I change the url https --> http i got this errorPreparing TestLink client API.Using TestLink URL: http://testlink-compagnie.com/lib/api/xmlrpc/v1/xmlrpc.phpFATAL: Error verifying developer key: HTTP server returned unexpected status: Foundbr.eti.kinoshita.testlinkjavaapi.util.TestLinkAPIException: Error verifying developer key: HTTP server returned unexpected status: FoundI am using Testlink 1.9.8, Jenkins 1.536, testLink Plugin 3.8Plz help me Bruno ^^ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
