[JIRA] (JENKINS-16327) Pages with CodeMirror editors are impossibly wide
Dave Abrahams created JENKINS-16327 Pages with CodeMirror editors are impossibly wide Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: job-config.tiff, system-config.tiff Components: gui Created: 13/Jan/13 3:36 AM Description: The Job Configuration and System Configuration windows are just intolerable. If I go in and manually set the max-width of the div.CodeMirror-lines>div>div to, say, 40em, the window behaves better. See attached screenshots. Even if you can't fix this quickly, a workaround using the "simple theme" plugin would be most appreciated! Environment: ubuntu linux 12.04 Project: Jenkins Labels: gui Priority: Major Reporter: Dave Abrahams 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-16233) EnvInject plugin using a cached value for ${WORKSPACE}
Gregory Boissinot
commented on JENKINS-16233
EnvInject plugin using a cached value for ${WORKSPACE}
Hi,
could you check your job configuration?
Thanks
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-14104) Use same node which has been specified in the "Restrict where this project can be run" field
Gregory Boissinot resolved JENKINS-14104 as Fixed Use same node which has been specified in the "Restrict where this project can be run" field Ok thanks for your last comment. I set to Fixed for now. And reopen it you reproduce it. Change By: Gregory Boissinot (12/Jan/13 8:10 PM) Status: Reopened 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
[JIRA] (JENKINS-14051) A PollingLog would be helpful in setting up dosTrigger
Gregory Boissinot commented on JENKINS-14051 A PollingLog would be helpful in setting up dosTrigger Any update? 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-14053) Being able to read environment variables in dos-trigger would be helpful
Gregory Boissinot commented on JENKINS-14053 Being able to read environment variables in dos-trigger would be helpful Any update? 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-15156) Builds Disappear from Build History after Completion
Peter Loron commented on JENKINS-15156 Builds Disappear from Build History after Completion Also seeing this on 1.498. Linux master. Win2K8 slave. 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-16183) Jabber Plugin does not work with Openfire 3.7.1
kutzi resolved JENKINS-16183 as Incomplete Jabber Plugin does not work with Openfire 3.7.1 No response from reporter => closing Change By: kutzi (12/Jan/13 4:50 PM) Status: Open Resolved Resolution: Incomplete 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-16311) Feature to display contributory upstream job changes in downstream builds
kutzi updated JENKINS-16311 Feature to display contributory upstream job changes in downstream builds Change By: kutzi (12/Jan/13 4:43 PM) Assignee: kutzi Component/s: core Component/s: downstream-ext 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-11799) GCC - better categories - Parser "GNU compiler (gcc)"
Ulli Hafner commented on JENKINS-11799 GCC - better categories - Parser "GNU compiler (gcc)" Thanks for adding! Can you please create a pull request? Then it would be easier to merge... 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-11799) GCC - better categories - Parser "GNU compiler (gcc)"
Yoichi Nakayama reopened JENKINS-11799 GCC - better categories - Parser "GNU compiler (gcc)" I've implemented classification of warnings produced by gcc 4.6 or later. https://github.com/yoichi/warnings-plugin/commit/04da9970e546183c1c1d3e204c7b8254525de241 Change By: Yoichi Nakayama (12/Jan/13 2:39 PM) Resolution: Won't Fix 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
[JIRA] (JENKINS-16191) Matrix job fails on git repos if node labels have special characters
Samuel Moritz commented on JENKINS-16191 Matrix job fails on git repos if node labels have special characters I guess the invalid characters could be converted/escaped by the Git plugin in some fashion. As a reference, here is a description of valid tag names: http://linux.die.net/man/1/git-check-ref-format 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-15069) Git plugin should fail when branch specifier does not match to any branch
Samuel Moritz commented on JENKINS-15069 Git plugin should fail when branch specifier does not match to any branch I cannot reproduce this in version 1.1.26. If I enter a branch name that does not exist I get the following output, and the build fails. "No candidate revisions ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job." 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-15067) NullPointerException using project-stats-plugin
Michael Pailloncy closed JENKINS-15067 as Fixed NullPointerException using project-stats-plugin Change By: Michael Pailloncy (12/Jan/13 9:18 AM) Status: Resolved Closed 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-15067) NullPointerException using project-stats-plugin
Michael Pailloncy resolved JENKINS-15067 as Fixed NullPointerException using project-stats-plugin https://github.com/jenkinsci/project-stats-plugin/commit/63c3393e9c4d3763432358ceee865a52651efb7b seems to have corrected the problem. Change By: Michael Pailloncy (12/Jan/13 9:18 AM) 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
[JIRA] (JENKINS-15293) Can't configure Maven Installations on Jenkins ver. 1.483, 1.484
Michael Pailloncy closed JENKINS-15293 as Fixed Can't configure Maven Installations on Jenkins ver. 1.483, 1.484 Bug due to a correction made for https://issues.jenkins-ci.org/browse/JENKINS-14510 -> resolved since 1.485 Change By: Michael Pailloncy (12/Jan/13 9:16 AM) Status: Resolved Closed 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-14510) NPE at hudson.maven.MavenModuleSet.getMaven(MavenModuleSet.java:982)
Michael Pailloncy closed JENKINS-14510 as Fixed NPE at hudson.maven.MavenModuleSet.getMaven(MavenModuleSet.java:982) Change By: Michael Pailloncy (12/Jan/13 9:15 AM) Status: Resolved Closed 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-14510) NPE at hudson.maven.MavenModuleSet.getMaven(MavenModuleSet.java:982)
Michael Pailloncy resolved JENKINS-14510 as Fixed NPE at hudson.maven.MavenModuleSet.getMaven(MavenModuleSet.java:982) see https://issues.jenkins-ci.org/browse/JENKINS-15293 Change By: Michael Pailloncy (12/Jan/13 9:14 AM) Status: Reopened 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
[JIRA] (JENKINS-15491) OOM in Jenkins after 1 day
Michael Pailloncy closed JENKINS-15491 as Fixed OOM in Jenkins after 1 day Switch to RedHat on the master (with Oracle JDK) seems to have resolved the issue. Change By: Michael Pailloncy (12/Jan/13 9:06 AM) Status: Resolved Closed 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-15491) OOM in Jenkins after 1 day
Michael Pailloncy resolved JENKINS-15491 as Fixed OOM in Jenkins after 1 day see https://issues.jenkins-ci.org/browse/JENKINS-15837 Change By: Michael Pailloncy (12/Jan/13 9:05 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
[JIRA] (JENKINS-15837) Jenkins takes a lot of time to respond after 2 days
Michael Pailloncy edited a comment on JENKINS-15837 Jenkins takes a lot of time to respond after 2 days Not reproduced on a RedHat OS with Oracle JDK. 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-15837) Jenkins takes a lot of time to respond after 2 days
Michael Pailloncy closed JENKINS-15837 as Fixed Jenkins takes a lot of time to respond after 2 days Change By: Michael Pailloncy (12/Jan/13 9:03 AM) Status: Resolved Closed 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-15837) Jenkins takes a lot of time to respond after 2 days
Michael Pailloncy resolved JENKINS-15837 as Fixed Jenkins takes a lot of time to respond after 2 days We've switch to a new architecture of Jenkins based on a RedHat OS (with Oracle JDK) on the master and this problem does not appear anymore. Change By: Michael Pailloncy (12/Jan/13 9:02 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
[JIRA] (JENKINS-15837) Jenkins takes a lot of time to respond after 2 days
Michael Pailloncy commented on JENKINS-15837 Jenkins takes a lot of time to respond after 2 days We've switch to a new architecture of Jenkins based on a RedHat OS on the master and this problem does not appear anymore. The OOME could be caused by a memory leak due to AIX or IBM JDK. I'll close the ticket because nobody seems to have had the same 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
