[JIRA] [core] (JENKINS-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Simon Strauch commented on JENKINS-26312 Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden Works for me in 1.598, tank you. (I hope this comment is appreciated.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Simon Strauch edited a comment on JENKINS-26312 Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden Works for me in 1.598, thank you. (I hope this comment is appreciated.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Simon Strauch
commented on JENKINS-26312
Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
I would like to suggest an alternative workaround. It puts the "save" Button at the bottom of the page. To click the buttons, you have to scroll down to the bottom of the page. It looks a little bit nicer, I think.
Change to rule for .bottom-sticker, #bottom-sticker this way:
style.css
.bottom-sticker, #bottom-sticker {
position: inherit !important;
width: 100%; /* it needs to occupy the entire width or else the underlying content will see through */
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Simon Strauch edited a comment on JENKINS-26312 Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden (_Sorry, Daniel Beck. Sorry, Tom FENNELLY_) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Simon Strauch
edited a comment on JENKINS-26312
Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
I would like to suggest an alternative workaround. It puts the "save" Button at the bottom of the page. To click the buttons, you have to scroll down to the bottom of the page. It looks a little bit nicer, I think.
Change to rule for .bottom-sticker, #bottom-sticker this way:
style.css
.bottom-sticker, #bottom-sticker {
position: inherit !important;
width: 100%; /* it needs to occupy the entire width or else the underlying content will see through */
}
EDIT: I don't want to give the solution. It is my workaround for working with the version with this bug. May be it help some others, or may be not.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-setup] (JENKINS-21570) Slave JNLP not signed by a CA causes issues with Java 7.51
Simon Strauch commented on JENKINS-21570 Slave JNLP not signed by a CA causes issues with Java 7.51 The Website http://www.java.com/en/download/help/java_blocked.xml describes 3 of 2 topics that went wrong in the JNLP-Slave. 1st: self-signed certificat. I used this description to extract the public key and add it to Java as Signer CA: stackoverflow: Extract raw X.509 Certificate from a signed APK or JAR Now Java Webstart begin to except the JAR file. But the 2nd Problem is: Missing required Permissions manifest attribute in main jar The MANIFEST.MF file does not contain the Permissions attribute. The workaround is to add the download server URL. 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] (JENKINS-14497) Can't start emulator with new Android SDK Tools rev. 20.0.1
Simon Strauch
commented on JENKINS-14497
Cant start emulator with new Android SDK Tools rev. 20.0.1
I tried applying the Integer.parseInt() and the fall-back with the RegEx to the String "16" of this change. It works, both return the number 16.
java.util.regex.Pattern REVISION = java.util.regex.Pattern.compile("(\\d+)(?:\\.\\d+){0,2}");
java.util.regex.Matcher m = REVISION.matcher("16");
m.matches(); // return true
String num = m.group(1); // num is "16"
return Integer.parseInt(num); // returns 16
This message is automatically generated by JIRA.
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-12573) CVS plugin version 2.0 checkout failed: Can't parse date/time
[ https://issues.jenkins-ci.org/browse/JENKINS-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160815#comment-160815 ] Simon Strauch commented on JENKINS-12573: - The update seems to work for me. CVS checkout with numeric timezone (+0200) does work on my system. CVS plugin version 2.0 checkout failed: Can't parse date/time - Key: JENKINS-12573 URL: https://issues.jenkins-ci.org/browse/JENKINS-12573 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Environment: Jenkins ver. 1.424.2 Jenkins CVS Plug-in 2.0 Reporter: Eric Co Assignee: Michael Clarke Priority: Blocker Fix For: current Attachments: screenshot-1.jpg After I upgraded the CVS plugin 2.0, got the following error: cvs checkout -P -D 2012-01-30 16:37:44HKT -d abc abc cvs [checkout aborted]: Can't parse date/time: 2012-01-30 16:37:44HKT -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12573) CVS plugin version 2.0 checkout failed: Can't parse date/time
[ https://issues.jenkins-ci.org/browse/JENKINS-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160759#comment-160759 ] Simon Strauch edited comment on JENKINS-12573 at 3/26/12 9:04 AM: -- I have the same problem. Reason is, The CVS server don't understand CEST, Central European Summer Time. I guess, this is caused by the CVS front end. But a solution would be to use +0200 instead of CEST. The string dd MMM HH:mm:ss z (lower case 'Z') in 'hudson.scm.CVSSCM'#'DATE_FORMATTER' should solve the problem, too. was (Author: 12delta): I have the same problem. Reason is, The CVS server don't understand CEST, Central European Summer Time. I guess, this is caused by the CVS front end. But a solution would be to use +0200 instead of CEST. The string dd MMM HH:mm:ss z (lower case 'Z') in 'hudson.scm.CVSSCM'#'DATE_FORMATTER' should solve the problem. CVS plugin version 2.0 checkout failed: Can't parse date/time - Key: JENKINS-12573 URL: https://issues.jenkins-ci.org/browse/JENKINS-12573 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Environment: Jenkins ver. 1.424.2 Jenkins CVS Plug-in 2.0 Reporter: Eric Co Assignee: Michael Clarke After I upgraded the CVS plugin 2.0, got the following error: cvs checkout -P -D 2012-01-30 16:37:44HKT -d abc abc cvs [checkout aborted]: Can't parse date/time: 2012-01-30 16:37:44HKT -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12573) CVS plugin version 2.0 checkout failed: Can't parse date/time
[ https://issues.jenkins-ci.org/browse/JENKINS-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160761#comment-160761 ] Simon Strauch edited comment on JENKINS-12573 at 3/26/12 9:25 AM: -- Our local CVS client understand +0200, but it don't understand '-D 2012-03-26 11:10 CEST'. Well, that is the cvs command-line-tool, I not sure how the Jenkins CVS client works. Would it be a solution to eliminate the timezone problem with an UTC/GMT timestamp? E.g. '-D 2012-03-26 09:10 GMT' instead of '-D 2012-03-26 11:10 CEST'. was (Author: 12delta): Our local CVS client understand +0200, but it don't understand '-D 2012-03-26 11:10 CEST'. Well, that is the cvs command-line-tool. Would it be a solution to eliminate the timezone problem with an UTC/GMT timestamp? E.g. '-D 2012-03-26 09:10 GMT' instead of '-D 2012-03-26 11:10 CEST'. CVS plugin version 2.0 checkout failed: Can't parse date/time - Key: JENKINS-12573 URL: https://issues.jenkins-ci.org/browse/JENKINS-12573 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Environment: Jenkins ver. 1.424.2 Jenkins CVS Plug-in 2.0 Reporter: Eric Co Assignee: Michael Clarke After I upgraded the CVS plugin 2.0, got the following error: cvs checkout -P -D 2012-01-30 16:37:44HKT -d abc abc cvs [checkout aborted]: Can't parse date/time: 2012-01-30 16:37:44HKT -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12573) CVS plugin version 2.0 checkout failed: Can't parse date/time
[ https://issues.jenkins-ci.org/browse/JENKINS-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160759#comment-160759 ] Simon Strauch edited comment on JENKINS-12573 at 3/26/12 12:07 PM: --- I have the same problem. Reason is, The CVS server don't understand CEST, Central European Summer Time. I guess, this is caused by the CVS front end. But a solution would be to use +0200 instead of CEST. The string (EDIT) dd MMM HH:mm:ss Z (uppercase 'Z') (EDIT) in 'hudson.scm.CVSSCM'#'DATE_FORMATTER' should solve the problem, too. EDIT: Yes, the patch above should work for me, I think. Right. was (Author: 12delta): I have the same problem. Reason is, The CVS server don't understand CEST, Central European Summer Time. I guess, this is caused by the CVS front end. But a solution would be to use +0200 instead of CEST. The string dd MMM HH:mm:ss z (lower case 'Z') in 'hudson.scm.CVSSCM'#'DATE_FORMATTER' should solve the problem, too. CVS plugin version 2.0 checkout failed: Can't parse date/time - Key: JENKINS-12573 URL: https://issues.jenkins-ci.org/browse/JENKINS-12573 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Environment: Jenkins ver. 1.424.2 Jenkins CVS Plug-in 2.0 Reporter: Eric Co Assignee: Michael Clarke Priority: Blocker Attachments: screenshot-1.jpg After I upgraded the CVS plugin 2.0, got the following error: cvs checkout -P -D 2012-01-30 16:37:44HKT -d abc abc cvs [checkout aborted]: Can't parse date/time: 2012-01-30 16:37:44HKT -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
