[JIRA] [core] (JENKINS-16327) Pages with CodeMirror editors are impossibly wide
Title: Message Title Donato Tagliabue commented on JENKINS-16327 Re: Pages with CodeMirror editors are impossibly wide Hello, I have the same problem with Jenkins 2.1. On Chrome and Firefox (not tested elsewhere), in job config page, the command in the "execute shell" textarea is always displayed on a single row (without any word wrap) and the page gets wider and wider if you have very long commands. This does not happen in the "job description" textarea, so I think is due to CodeMirror (css or code). Moreover, the suggested workaround (trying to disable CodeMirror) does not work: the checkbox "disable syntax highlighting" do nothing. I checked it and also restarted Jenkins, and nothing changed. Thanks, Donato Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-25561) Wrong column number in executor status table
Donato Tagliabue created JENKINS-25561 Wrong column number in executor status table Issue Type: Bug Assignee: Unassigned Attachments: wrong_executor_table.png Components: core Created: 12/Nov/14 11:08 AM Description: The table for the status of executors (see picture) has a wrong format. This is due I think to an extra column (I've customized the css to have a cell border, but the problem exists in any case). If you look at the HTML source (this is from "Jenkins on Jenkins"): tr th class="pane" colspan="3"a class="model-link inside" href=""img style="width: 16px; height: 16px; " class="icon-computer icon-sm" src="" / celery/a/th /tr tr td class="pane" align="right" style="vertical-align: top"1/td td class="pane"Inattivo/td td class="pane"/td td class="pane"/td /tr the colspan 3 seems incorrect or, viceversa, there is an extra column (td class="pane"/td), which was not present in older versions. Environment: Found in v1.580 and higher. not present in v1.570 Project: Jenkins Priority: Minor Reporter: Donato Tagliabue 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-23026) Parameterized build can not save the Parameter Description in the first time
Donato Tagliabue commented on JENKINS-23026 Parameterized build can not save the Parameter Description in the first time Hi, I've the same problem. The behaviour is the same as in Jenkins-23151 bug. The workaround also in this case is to "apply" the modifications (the new build parameter description) before saving 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-23191) NPE in downstream jobs
Donato Tagliabue commented on JENKINS-23191 NPE in downstream jobs Hi Daniel, the workaround works, but you have to do that every time you modify the job (let me say, if you change the description, you will also have to set the radio button for the downstream project trigger). From my personal experience, it's very easy to forget 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] [core] (JENKINS-23191) NPE in downstream jobs
Donato Tagliabue commented on JENKINS-23191 NPE in downstream jobs Hi, I can confirm that the problem happens in Jenkins 1.563 with three new jobs created from scratch. When in project B you choose "Build after other projects are built" you have "Trigger only if build is stable" selected by default. When you add as a post-build action "Build other projects", none of the previous radio buttons are selected (it seems almost a _javascript_ problem). If you save the configuration like that for the job B, and you run the job A, you'll get the error "java.lang.NullPointerException at hudson.model.Result.isBetterOrEqualTo(Result.java:125)" and job B will not be triggered. 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] [downstream-ext] (JENKINS-23191) NPE in downstream jobs
Donato Tagliabue created JENKINS-23191 NPE in downstream jobs Issue Type: Bug Assignee: kutzi Attachments: bug_jenkins_downstreams_jobs.png, bug_jenkins_downstreams_jobs_2.png Components: downstream-ext Created: 26/May/14 12:43 PM Description: Created three jobs: job A, job B, job C. Set job B config to be triggered after job A and to trigger job C. In this case, radio button in the section "build after other projects are built" cannot be saved (even if you save and reopen the configuration page). When job A is built, a NullPointerException is thrown and job B is not started (see attachments). If you chain only job B to job A, it works. Environment: Jenkins 1.563 RHEL6 Project: Jenkins Labels: nullpointer downstream upstream Priority: Major Reporter: Donato Tagliabue 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] [build-pipeline] (JENKINS-23151) Execute shell window not saved properly
Donato Tagliabue commented on JENKINS-23151 Execute shell window not saved properly I have the same problem (with Jenkins 1.563, on RHEL6, browser Chrome), not present in older releases (e.g. 1.540). If you click on "apply" in the configuration page, then on "save" it seems to work always, instead, by using directly the "save" button, textarea contents sometimes is lost. 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.
