[JIRA] [extensible-choice-parameter] (JENKINS-22282) Extensible choice parameter greyed out in Internet Explorer
David Odren commented on JENKINS-22282 Extensible choice parameter greyed out in Internet Explorer Ah, your last post has been most helpful! Now I have to figure out why my default setting in IE seems to be '7'. Perhaps I need to talk with our IT department. As soon as I change it to a higher value per your instructions the problem goes away. 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] [extensible-choice-parameter] (JENKINS-22282) Extensible choice parameter greyed out in Internet Explorer
David Odren commented on JENKINS-22282 Extensible choice parameter greyed out in Internet Explorer I also tried this on a Windows Server 2012 R2 Datacenter machine also running IE 11. The Extensible Choice parameter is also grayed out when "Editable" is checked. 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] [extensible-choice-parameter] (JENKINS-22282) Extensible choice parameter greyed out in Internet Explorer
David Odren commented on JENKINS-22282 Extensible choice parameter greyed out in Internet Explorer Hello, I wanted to let you know that I have updated my 64-bit Windows 7 Professional SP1 machine with Internet Explorer 11 and applied the latest IE 11 security updates. After doing this I saw no difference whether I added my domain to the Compatibility View or not. The choice field continues to be grayed out and not editable when the "Editable" box is checked. 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] [extensible-choice-parameter] (JENKINS-22282) Extensible choice parameter greyed out in Internet Explorer
David Odren commented on JENKINS-22282 Extensible choice parameter greyed out in Internet Explorer It works just fine with both Chrome and Firefox, which is why I only wrote the bug against Internet Explorer. I have all of the latest updates applied to Jenkins and all plugins. 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] [extensible-choice-parameter] (JENKINS-22282) Extensible choice parameter greyed out in Internet Explorer
David Odren commented on JENKINS-22282 Extensible choice parameter greyed out in Internet Explorer I have the same problem when following your steps. However, the problem disappears as soon as "Editable" is left unchecked, and returns as soon as it is checked again. 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] [extensible-choice-parameter] (JENKINS-22282) Extensible choice parameter greyed out in Internet Explorer
David Odren updated JENKINS-22282 Extensible choice parameter greyed out in Internet Explorer Screen Capture of grayed out box, screen capture of "About IE" and config.xml of job. Change By: David Odren (25/Mar/14 3:20 PM) Attachment: JenkinsBug22282.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 -- 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] [extensible-choice-parameter] (JENKINS-22282) Extensible choice parameter greyed out in Internet Explorer
David Odren commented on JENKINS-22282 Extensible choice parameter greyed out in Internet Explorer I selected the job to build from the all menu, then clicked on "Build with Parameters" on the left. The extensible choice paramter window is grey and too small to read the entire string. When I click on the grey area, it does not expand to the list of choices that I can click on as it does in Chrome. The version of IE I am using is 10.0.9200.16844 Please find screen captures and config.xml file in attachment. I am seeing the problem as the build administrator as well as users seeing the 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/d/optout.
[JIRA] [extensible-choice-parameter] (JENKINS-22282) Extensible choice parameter greyed out in Internet Explorer
David Odren created JENKINS-22282 Extensible choice parameter greyed out in Internet Explorer Issue Type: Task Assignee: Unassigned Components: extensible-choice-parameter Created: 20/Mar/14 8:05 PM Description: I have defined an Extensible Choice parameter with a Global Choice Parameter with "Top Most Choice", checked "add Edited Value" and made it Editable. When I build the job with parameters, the choice is greyed out and the drop-down menu is not available. Environment: Jenkins installed on Windows Server 2012, Client running IE on Windows 7 Project: Jenkins Labels: plugin Priority: Major Reporter: David Odren 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-16560) Failure to rewrite files during rekeying on Windows Server 2003 R2
David Odren commented on JENKINS-16560 Failure to rewrite files during rekeying on Windows Server 2003 R2 Thank you shinsato! I was able to work around the issue by re-keying the the background as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16970) Jenkins NUnit Plugin 0.14 incorrectly converts Unit XML results to JUnit
David Odren created JENKINS-16970 Jenkins NUnit Plugin 0.14 incorrectly converts Unit XML results to JUnit Issue Type: Bug Affects Versions: current Assignee: redsolo Attachments: ASI.SOP.AmazonBTI.Tests.xml, junitResult.xml, TestResultLevel1.jpg, TestResultLevel2.jpg, TestResultLevel3.jpg Components: junit, nunit Created: 26/Feb/13 7:56 PM Description: In the conversion of the NUnit XML results to JUnit, some tests are named incorrectly. When an NUnit output file contains a test-suite of type "TestFixture" containing a results element containing both test-suites of type "ParameterizedTest" and test-cases (not parameterized), the test-cases are reported with incorrect namespace and class names. It is as if some code were determining the namespace/class names to report by walking a certain number of tokens back in a fully qualified class name, and too many steps back are being taken for simple tests when parameterized tests are present. In TestResultLevel1.jpg all tests should appear under pacakge ASI.SOP.AmazonBTI.Tests. TestResultLevel3.jpg shows the badly parsed name AmazonUpcParseStrategyTests.ShouldRequireProductProgramFinder. Environment: Windows Server 2003, Jenkins 1.497, Jenkins NUnit plugin 0.14, NUnit 2.6.2 Project: Jenkins Priority: Minor Reporter: David Odren 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-16560) Failure to rewrite files during rekeying on Windows Server 2003 R2
David Odren edited a comment on JENKINS-16560 Failure to rewrite files during rekeying on Windows Server 2003 R2 I was at 1.497 and told Jenkins to upgrade automatically to 1.500, then restart Jenkins. After Jenkins restarted, the version reported at the bottom of the page was 1.500. (I even repeated the test again this morning to make sure it wasn't reporting 1.498, which is where the original problem occurred for me weeks ago.) 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-16560) Failure to rewrite files during rekeying on Windows Server 2003 R2
David Odren commented on JENKINS-16560 Failure to rewrite files during rekeying on Windows Server 2003 R2 I was at 1.497 and told Jenkins to upgrade automatically to 1.500, then restart Jenkins. After Jenkins restarted, the version reported at the bottom of the page was 1.500. (I even repeated the test again this morning to make sure it wasn't reporting 1.498, which is where the original problem occurred or me weeks ago.) 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-16560) Failure to rewrite files during rekeying on Windows Server 2003 R2
David Odren created JENKINS-16560 Failure to rewrite files during rekeying on Windows Server 2003 R2 Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Jan/13 9:49 PM Description: In an upgrade from Jenkins 1.487 to 1.500 the rekey operation fails due to being unable to rewrite the necessary files. This seems to be the same or similar to the issue resolved in JENKINS-16319, which was included in the Jenkins 1.500 release. I seem to be unable to upgrade beyond Jenkins 1.497, as this problem first occurred in an attempted upgrade from Jenkins 1.497 to 1.498. The re-key log is as follows: Started re-keying Wed Jan 09 10:13:00 CST 2013 Scanning E:\Jenkins\config.xml ERROR: Failed to rewrite E:\Jenkins\config.xml java.io.IOException: Unable to delete E:\Jenkins\config.xml at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:112) at hudson.util.SecretRewriter.rewrite(SecretRewriter.java:121) at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:170) at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:143) at jenkins.security.RekeySecretAdminMonitor$RekeyThread.run(RekeySecretAdminMonitor.java:182) Scanning E:\Jenkins\jobs\BuildAllFromTrunk\builds\2012-12-11_06-16-44\changelog.xml Scanning E:\Jenkins\jobs\MakeCustomerService\builds\2012-12-15_06-40-38\changelog.xml Scanning E:\Jenkins\jobs\MakeCustomerService\builds\2013-01-08_06-40-28\changelog.xml Scanning E:\Jenkins\jobs\MakeFlash\builds\2012-12-29_07-07-22\build.xml Scanning E:\Jenkins\jobs\MakeImageOne\builds\2012-12-18_10-16-06\changelog.xml Scanning E:\Jenkins\jobs\MakeMsgProc\builds\2012-12-11_07-07-21\build.xml Scanning E:\Jenkins\jobs\MakeMsgProc\builds\2013-01-03_05-35-18\build.xml Scanning E:\Jenkins\jobs\MakePortal\builds\2012-12-20_07-21-50\changelog.xml Scanning E:\Jenkins\jobs\MakePrintAndPopcorn\builds\2012-12-13_10-33-18\build.xml Scanning E:\Jenkins\jobs\MakePrintAndPopcorn\builds\2013-01-05_07-07-37\build.xml Scanning E:\Jenkins\jobs\MakeTools\builds\2012-12-19_06-41-33\changelog.xml Scanning E:\Jenkins\jobs\MakeWeb\builds\2012-12-13_05-35-40\build.xml Scanning E:\Jenkins\jobs\MakeWeb\builds\2013-01-05_05-34-53\build.xml Scanning E:\Jenkins\jobs\RefreshBranchSourceCode\builds\2012-12-13_07-01-20\changelog.xml Scanning E:\Jenkins\jobs\RefreshBranchSourceCode\builds\2012-12-15_07-01-41\changelog.xml Scanning E:\Jenkins\jobs\RefreshBranchSourceCode\builds\2012-12-20_06-16-43\changelog.xml Scanning E:\Jenkins\jobs\RefreshBranchSourceCode\builds\2012-12-27_07-01-46\changelog.xml Scanning E:\Jenkins\jobs\RefreshBranchSourceCode\builds\2013-01-03_05-31-58\changelog.xml Scanning E:\Jenkins\jobs\RefreshBranchSourceCode\builds\2013-01-08_05-31-46\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-11_06-16-45\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-13_06-01-10\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-14_06-48-53\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-15_07-01-37\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-18_07-00-54\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-20_06-16-38\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-24_09-27-10\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-28_05-31-39\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-30_06-16-41\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2013-01-03_05-59-52\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2013-01-05_06-48-03\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2013-01-08_06-16-39\changelog.xml ERROR: Failed to rewrite E:\Jenkins\proxy.xml java.io.IOException: Unable to delete E:\Jenkins\proxy.xml at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:112) at hudson.util.SecretRewriter.rewrite(SecretRewriter.java:121) at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:170) at hudson.util.SecretRewriter.r
[JIRA] (JENKINS-16319) Failure to delete old config files during rekeying on Windows
David Odren edited a comment on JENKINS-16319 Failure to delete old config files during rekeying on Windows An upgrade from Jenkins 1.497 to 1.500 produced the same errors about failure to rewrite the config.xml files. I am running Jenkins as a service on Windows Server 2003 R2 Standard Edition SP2. 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-16319) Failure to delete old config files during rekeying on Windows
David Odren reopened JENKINS-16319 Failure to delete old config files during rekeying on Windows An upgrade from Jenkins 1.497 to 1.500 produced the same errors about failure to rewrite the config.xml files. I am running Jenkins as a service on Windows 7. Change By: David Odren (30/Jan/13 3:45 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.
