[JIRA] [core] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Joël Royer edited a comment on JENKINS-14546 Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated Issue is still present in 1.549!!! I have a nested view, with one sub-view (type list view). Admin users can see nested view and its sub-view, and all jobs associated with it. Regulars users (with only Global Read permission), can't see the nested view. But they can see jobs in the tab "All". The only way I found is to assign View Read Permission to regulars users. But they can see all views, even those without jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Joël Royer commented on JENKINS-14546 Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated Issue is still present in 1.549!!! I have a nested view, with one sub-view (type list view). Admin users can see nested view and its sub-view, and all jobs associated with it. Ragulars users (with only Global Read permission), can't see the nested view. But they can see jobs in the tab "All". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-16543) [Delete old builds] Each setting appear 2 times
Joël Royer created JENKINS-16543 [Delete old builds] Each setting appear 2 times Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: ScreenShot_jroyer_2013-01-30_121412.png, ScreenShot_jroyer_2013-01-30_121532.png Components: core Created: 30/Jan/13 11:16 AM Description: The settings for "Delete old builds" appear 2 times. First time in french: Second time in english, after display advanced tab: The settings in french are ignored! Environment: Windows Server 2003 GlassFish 3.1.2.2 Oracle JDK 1.7.0_11 Jenkins 1.500 Project: Jenkins Priority: Major Reporter: Joël Royer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-15700) SVNException: svn: E210003: Malformed reply from SOCKS server at ....
Joël Royer updated JENKINS-15700 SVNException: svn: E210003: Malformed reply from SOCKS server at Change By: Joël Royer (02/Nov/12 10:17 AM) Environment: Jenkinsserver:WindowsServer2003R2/Glassfish3.1.2.2/ OracleJavaSE1.6/ Jenkins1.487Subversionserver:LinuxDebian5x64/Subversion1.4.6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15700) SVNException: svn: E210003: Malformed reply from SOCKS server at ....
Joël Royer created JENKINS-15700 SVNException: svn: E210003: Malformed reply from SOCKS server at Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: subversion Created: 02/Nov/12 10:16 AM Description: We've got the next error from time to time when jobs tried to update their workspace. The only solution we've found for the moment is to reboot jenkins server. Building in workspace C:\PIC\work\jenkins-work\jobs\MyJob\workspace Updating svn://svnserver/myproject/trunk to revision '2012-10-29T10:43:48.770 +0100' ERROR: Failed to update svn://svnserver/myproject/trunk org.tmatesoft.svn.core.SVNException: svn: E210003: Malformed reply from SOCKS server at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:85) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:69) at org.tmatesoft.svn.core.internal.io.svn.SVNPlainConnector.open(SVNPlainConnector.java:65) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:77) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1252) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.testConnection(SVNRepositoryImpl.java:95) at org.tmatesoft.svn.core.io.SVNRepository.getRepositoryUUID(SVNRepository.java:280) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.createRepository(SVNBasicDelegate.java:339) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.createRepository(SVNBasicDelegate.java:328) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:532) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:414) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:324) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1221) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:315) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:295) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:391) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:144) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:799) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:780) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:763) at hudson.FilePath.act(FilePath.java:851) at hudson.FilePath.act(FilePath.java:824) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:746) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:688) at hudson.model.AbstractProject.checkout(AbstractProject.java:1308) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:679) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:584) at hudson.model.Run.execute(Run.java:1516) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.net.SocketException: Malformed reply from SOCKS server at java.net.SocksSocketImpl.readSocksReply(SocksSocketImpl.java:128) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:459) at java.net.Socket.connect(Socket.java:579) at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.connect(SVNSocketFactory.java:112) at
[JIRA] (JENKINS-13032) Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command
Joël Royer updated JENKINS-13032 Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command Change By: Joël Royer (23/Oct/12 1:11 PM) Attachment: threadDumps.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13032) Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command
Joël Royer edited a comment on JENKINS-13032 Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command The bug re-occurs today. Here is a zip file which contains thread dumps: 1 before restart and 1 after restart (See joined file threadDumps.zip) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13032) Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command
Joël Royer commented on JENKINS-13032 Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command The bug re-occurs today. I joined a zip file which contains thread dumps before and after server reboot. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13032) Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command
Joël Royer updated JENKINS-13032 Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command The bug re-occurs today. Here is a zip file which contains thread dumps: 1 before restart and 1 after restart Change By: Joël Royer (22/Oct/12 3:22 PM) Attachment: threadDumps.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13032) Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command
Joël Royer edited a comment on JENKINS-13032 Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command The bug re-occurs today. Here is a zip file which contains thread dumps: 1 before restart and 1 after restart This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13032) Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command
Joël Royer edited a comment on JENKINS-13032 Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command The bug re-occurs today. Here is a zip file which contains thread dumps: 1 before restart and 1 after restart Seems to have a problem joining the zip file. How can I send you this file? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13032) Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command
Joël Royer
commented on JENKINS-13032
Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command
Yes, we have a proxy. I setted up Jenkins to use this proxy in the plugin management, but I added the CVS server hostname in exception list ("No proxy host"). Is the plugin using those settings?
Moreover, we have a strange behavior. When we got this error, if we restart the application server, CVS server is reachable.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13032) Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command
Joël Royer commented on JENKINS-13032 Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command I'm using GlassFish App Server v3.1.2.2. The issue re-occurs from time to time but when it reoccurs, the only solution we've found for the moment is to stop et start GlassFish. There is no automatic recover. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13032) Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command
Joël Royer reopened JENKINS-13032 Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command I've got the same problem since version 2.0 of the plugin. I've got timeouts randomly. However, the CVS server is available, I can ping it from the jenkins server. Change By: Joël Royer (18/Oct/12 9:37 AM) Resolution: NotADefect Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13032) Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command
Joël Royer edited a comment on JENKINS-13032 Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command I've got the same problem since version 2.0 of the plugin. I've got timeouts randomly. However, the CVS server is available, I can ping it from the jenkins server. Windows Server 2003 / Glassfish 3.1.2.2 / Oracle SDK 1.7.0_07 / Jenkins 1.486 / CVS Plugin 2.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
[JIRA] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Joël Royer commented on JENKINS-14546 Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated I have the same problen on my own Jenkins server (v1.480). I'm admin and I see all nested views. But my regular users can't see it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Joël Royer edited a comment on JENKINS-14546 Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated I have the same problen on my own Jenkins server (Jenkins v1.480, nested View Plugin v1.9). I'm admin and I see all nested views. But my regular users can't see it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14313) login page redirects to login page
Joël Royer commented on JENKINS-14313 login page redirects to login page I have the same problem (not all time) on my Jenkins server (Jenkins v1.480). Actually, the login is succesfull (I see all links in the menu at the left of the screen) but I see the login form instead of the dashboard. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
