[JIRA] (JENKINS-56992) When a pod dies in kubernetes, we should be able to dump out the pod logs somewhere
Title: Message Title Levon Saldamli commented on JENKINS-56992 Re: When a pod dies in kubernetes, we should be able to dump out the pod logs somewhere I have a similar problem (running jenkins builds with openshift) when pods occasionally fail to start and disappear without any trace of logs kept anywhere. It would be great of logs or events from pod and container startup failures could show up in the build log on jenkins. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198689.1555081636000.6141.1583999280170%40Atlassian.JIRA.
[JIRA] [xvnc-plugin] (JENKINS-25424) Exception when editing nodes
Levon Saldamli commented on JENKINS-25424 Exception when editing nodes Yes, please list the steps to reproduce it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-25424) Exception when editing nodes
Levon Saldamli commented on JENKINS-25424 Exception when editing nodes I've committed a fix but I can't get the mvn release plugin to make a release. Does anyone know how to make it work or what steps it does so I can do it manually? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-25424) Exception when editing nodes
Levon Saldamli commented on JENKINS-25424 Exception when editing nodes Thanks, that seemed to work, but the upload was done to http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/xvnc/1.20/ and this version doesn't show up among the updates or at http://updates.jenkins-ci.org/download/plugins/xvnc/ which still has 1.18 (the old version). Am I missing something? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-25424) Exception when editing nodes
Levon Saldamli commented on JENKINS-25424 Exception when editing nodes Got help on jenkins-dev: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Help%5C%21Mypluginisnotshowingupintheupdatecenter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-25424) Exception when editing nodes
Levon Saldamli resolved JENKINS-25424 as Fixed Exception when editing nodes Fixed in version 1.20 Change By: Levon Saldamli (13/Nov/14 7:16 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25424) Exception when editing nodes
Levon Saldamli started work on JENKINS-25424 Exception when editing nodes Change By: Levon Saldamli (10/Nov/14 5:09 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc] (JENKINS-19139) Xvnc plugin fails if the job has a space in the name
Levon Saldamli reopened JENKINS-19139 Xvnc plugin fails if the job has a space in the name Adding "" in the path value in XAUTHORITY value didn't work (causes wrong file name issues). The problem is in the "vncserver" script which contains the line: open (XAUTH, "|xauth -f $xauthorityFile source -"); which needs "" around $xauthorityFile . I'll be reverting my fix in 1.17. Change By: Levon Saldamli (16/Mar/14 8:10 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/d/optout.
[JIRA] [xvnc] (JENKINS-19139) Xvnc plugin fails if the job has a space in the name
Levon Saldamli resolved JENKINS-19139 as Not A Defect Xvnc plugin fails if the job has a space in the name The problem is in the vncserver start script, which doesn't put quotes around the xauthority filename. Fix/report that bug in vncserver or don't use spaces in job names (or disable per build xauthority checkbox). Change By: Levon Saldamli (16/Mar/14 9:02 AM) Status: Reopened Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc] (JENKINS-22105) [xvnc] Client is not authorized to connect to Server
Levon Saldamli commented on JENKINS-22105 [xvnc] Client is not authorized to connect to Server Fixed in 1.17. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc] (JENKINS-22105) [xvnc] Client is not authorized to connect to Server
Levon Saldamli resolved JENKINS-22105 as Fixed [xvnc] Client is not authorized to connect to Server Change By: Levon Saldamli (16/Mar/14 9:53 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc] (JENKINS-18108) Unrecognized option: UI in v1.14
Levon Saldamli reopened JENKINS-18108 Unrecognized option: UI in v1.14 Change By: Levon Saldamli (16/Mar/14 10:02 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/d/optout.
[JIRA] [xvnc] (JENKINS-18108) Unrecognized option: UI in v1.14
Levon Saldamli resolved JENKINS-18108 as Wont Fix Unrecognized option: UI in v1.14 Fix is needed in vncserver script, where quotes should be added around the filename to xauthority file when xauth is called. Or spaces in job names should be avoided. Change By: Levon Saldamli (16/Mar/14 10:03 AM) Status: Reopened Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc] (JENKINS-22105) [xvnc] Client is not authorized to connect to Server
Levon Saldamli commented on JENKINS-22105 [xvnc] Client is not authorized to connect to Server @Stephane, are you also running TightVNC? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc] (JENKINS-22101) Setting per-job xauthority fails
Levon Saldamli resolved JENKINS-22101 as Not A Defect Setting per-job xauthority fails Use environment variable $XAUTHORITY. Change By: Levon Saldamli (10/Mar/14 3:00 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc] (JENKINS-22101) Setting per-job xauthority fails
Levon Saldamli commented on JENKINS-22101 Setting per-job xauthority fails I'm not sure if that is backwards compatible. I don't think the vncserver command understands the -auth flag. So your workaround should be fine to use instead. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc] (JENKINS-18108) Unrecognized option: UI in v1.14
Levon Saldamli resolved JENKINS-18108 as Fixed Unrecognized option: UI in v1.14 Fixed in 1.16 Change By: Levon Saldamli (05/Mar/14 3:08 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] [xvnc] (JENKINS-19139) Xvnc plugin fails if the job has a space in the name
Levon Saldamli resolved JENKINS-19139 as Fixed Xvnc plugin fails if the job has a space in the name Fixed in 1.16 Change By: Levon Saldamli (05/Mar/14 3:07 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] [xvnc] (JENKINS-20177) XVnc plugin fails to set the DISPLAY variable properly if jenkins already
Levon Saldamli commented on JENKINS-20177 XVnc plugin fails to set the DISPLAY variable properly if jenkins already I cannot reproduce this. I can see the original variable in the environment, but it is reset by the plugin to the correct xvnc display value, as I can see by running "echo $DISPLAY" in a build step shell command. Is this still an issue? Can you provide logs or do a similar test as I did? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-16775) Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpl's signer information does not match signer information of other clas
Levon Saldamli edited a comment on JENKINS-16775 Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpls signer information does not match signer information of other classes in the same package Is there a difference in the classpath? I found this explanation: http://stackoverflow.com/questions/2877262/java-securityexception-signer-information-does-not-match It could help to resolve the issue to dump the classpath used, and search whether there are multiple classes named org.kohsuke.args4j.XmlParser$ArgumentImpl. Btw, we are using this plugin with 1.501 without seing this 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-16775) Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpl's signer information does not match signer information of other clas
Levon Saldamli edited a comment on JENKINS-16775 Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpls signer information does not match signer information of other classes in the same package Is there a difference in the classpath? I found this explanation: http://stackoverflow.com/questions/2877262/java-securityexception-signer-information-does-not-match It could help to resolve the issue to dump the classpath used, and search whether there are multiple classes named org.kohsuke.args4j.XmlParser$ArgumentImpl. Btw, we are using this plugin with Jenkins 1.501 without seing this 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-16775) Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpl's signer information does not match signer information of other clas
Levon Saldamli commented on JENKINS-16775 Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpls signer information does not match signer information of other classes in the same package Is there a difference in the classpath? I found this explanation: http://stackoverflow.com/questions/2877262/java-securityexception-signer-information-does-not-match It could help to resolve the issue to dump the classpath used, and search whether there are multiple classes named org.kohsuke.args4j.XmlParser$ArgumentImpl. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xvnc] (JENKINS-18108) Unrecognized option: UI in v1.14
Levon Saldamli edited a comment on JENKINS-18108 Unrecognized option: UI in v1.14 I wonder if "UI" comes from "DART UI Fest", is that a directory name? I'll try to reproduce that. Meanwhile, you could try to change the dir name to something without spaces, and see if that helps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xvnc] (JENKINS-18108) Unrecognized option: UI in v1.14
Levon Saldamli commented on JENKINS-18108 Unrecognized option: UI in v1.14 I'm suspecting there is an issue with spaces in filenames. I'll look into that. Meanwhile, you could try with a project name that doesn't contain spaces, and see if that works 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] [xvnc] (JENKINS-18108) Unrecognized option: UI in v1.14
Levon Saldamli commented on JENKINS-18108 Unrecognized option: UI in v1.14 Great, thanks for the debugging! Levon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xvnc] (JENKINS-17550) Xvnc plugin tries to use already allocated displays
Levon Saldamli resolved JENKINS-17550 as Fixed Xvnc plugin tries to use already allocated displays Fixed in xvnc-1.14 Change By: Levon Saldamli (10/Apr/13 7:03 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xvnc] (JENKINS-17280) Display number out of bounds, no way to reset
Levon Saldamli resolved JENKINS-17280 as Fixed Display number out of bounds, no way to reset Fixed in xvnc-1.14 Change By: Levon Saldamli (10/Apr/13 7:03 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xvnc] (JENKINS-17550) Xvnc plugin tries to use already allocated displays
Levon Saldamli created JENKINS-17550 Xvnc plugin tries to use already allocated displays Issue Type: Bug Affects Versions: current Assignee: Levon Saldamli Components: xvnc Created: 09/Apr/13 11:21 PM Description: Xvnc plugin creates a new allocator for each build, and forgets previously allocated ports and tries to allocate them again. Project: Jenkins Labels: plugin Priority: Major Reporter: Levon Saldamli This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xvnc] (JENKINS-1943) add ability for xvnc plugin to take a screenshot
Levon Saldamli commented on JENKINS-1943 add ability for xvnc plugin to take a screenshot What is the status of this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xvnc] (JENKINS-17280) Display number out of bounds, no way to reset
Levon Saldamli commented on JENKINS-17280 Display number out of bounds, no way to reset No, this is not implemented yet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xvnc] (JENKINS-17280) Display number out of bounds, no way to reset
Levon Saldamli commented on JENKINS-17280 Display number out of bounds, no way to reset Very bad. It would need a restart. I'll implement the above suggestion to clear the blacklist when it's full in the next release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xvnc] (JENKINS-16879) More robust display detection needed - builds fail when many builds require Xvnc
Levon Saldamli resolved JENKINS-16879 as Fixed More robust display detection needed - builds fail when many builds require Xvnc Resolved in xvnc-1.12 Change By: Levon Saldamli (04/Apr/13 3:55 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] [xvnc] (JENKINS-17280) Display number out of bounds, no way to reset
Levon Saldamli commented on JENKINS-17280 Display number out of bounds, no way to reset 1) is implemented now in xvnc-1.12, but not 2) Is this sufficient to resolve this bug? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
