[JIRA] [core] (JENKINS-14264) Breadcrumb: the link to the lastBuild console is missing in the popup for a some jobs
mike bayer commented on JENKINS-14264 Breadcrumb: the link to the lastBuild console is missing in the popup for a some jobs this issue has driven me completely mad for months, and I just identified tonight that it is in fact two different "classes" of console output, based on the size of the log, and then from that "class" you get two entirely different UX treatments - the presence or lack of a "breadcrumb" link to the console output (why is the contextual popup called a "breadcrumb?" not really a breadcrumb...), as well as either "console output ... view as plain text" on the right for small logs or "console output raw" for large logs when you view the build itself. evernat seems to have identified this size as 200K, sounds about right - why isn't this hardcoded number configurable or documented anywhere ?why two entirely different sets of logic kicking in? why can't jenkins pay for all the psychiatric meds this issue has caused me? so many questions thanks for listening. 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-20769) Failed to execute command Pipe.EOF
mike bayer commented on JENKINS-20769 Failed to execute command Pipe.EOF I've recently upgraded from fedora 14 to fedora 20 and am suddenly getting this one quite often. for me it seems to occur after it provisioned a new EC2 node. Mar 04, 2014 8:03:49 AM hudson.slaves.NodeProvisioner update INFO: pg, mysql, etc (ami-d53f32bc) provisioningE successfully completed. We have now 2 computer(s) Mar 04, 2014 8:04:09 AM hudson.remoting.Channel$2 handle SEVERE: Failed to execute command Pipe.EOF(10) (channel pg, mysql, etc (i-e5638cc6)) java.lang.NullPointerException at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) 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-20769) Failed to execute command Pipe.EOF
mike bayer commented on JENKINS-20769 Failed to execute command Pipe.EOF just to update, I'm running "Jenkins ver. 1.558-SNAPSHOT (rc-04/01/2014 04:22 GMT-kohsuke)" which I assume includes this fix, I now see this in my logs: SEVERE: Failed to execute command Pipe.Flush(10) (channel general (i-34cf7b17)) java.lang.ClassCastException: java.io.OutputStreamWriter cannot be cast to java.io.OutputStream at hudson.remoting.ProxyWriter$Flush.execute(ProxyWriter.java:285) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Apr 01, 2014 3:55:54 PM hudson.remoting.Channel$2 handle SEVERE: This command is created here Apr 01, 2014 3:57:13 PM hudson.remoting.Channel$2 handle SEVERE: Failed to execute command Pipe.Flush(10) (channel general (i-6ac87c49)) java.lang.ClassCastException: java.io.OutputStreamWriter cannot be cast to java.io.OutputStream at hudson.remoting.ProxyWriter$Flush.execute(ProxyWriter.java:285) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) not sure if this is related to the fix or 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] (JENKINS-6691) EC2 plugin will launch more instances than cap allows if enough jobs are queued up while no instances are active
mike bayer commented on JENKINS-6691 EC2 plugin will launch more instances than cap allows if enough jobs are queued up while no instances are active this is a major issue that is costing me real cash. over at http://jenkins.sqlalchemy.org/ , a new build will add about ten jobs simultaneously, and despite my instance limit of two, I immediately get five or more instances starting up, which I then have to go and kill manually or pay the price, literally. It seems a lot like the EC2 plugin is spawning based on the number of EC2 instances that amazon reports that are running, without taking into account the number of instances the plugin is already starting to spawn but won't yet be reported by amazon. 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-6691) EC2 plugin will launch more instances than cap allows if enough jobs are queued up while no instances are active
mike bayer commented on JENKINS-6691 EC2 plugin will launch more instances than cap allows if enough jobs are queued up while no instances are active pull request at https://github.com/jenkinsci/ec2-plugin/pull/25, seems to be working for me. 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-15158) Sometimes starts the wrong instance
mike bayer commented on JENKINS-15158 Sometimes starts the wrong instance this is likely a duplicate of JENKINS-12332 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-12332) only start an EC2 instance if a build is actually going to occur, per current label expressions
mike bayer commented on JENKINS-12332 only start an EC2 instance if a build is actually going to occur, per current label expressions note that issue JENKINS-15158 seems to describe the same phenomenon. 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-27006) Broken URL in ContextMenu after adding Actions
Title: Message Title mike bayer commented on JENKINS-27006 Re: Broken URL in ContextMenu after adding Actions ProxyPassMatch is the difference. I've updated the wiki to note this distinction. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-27006) Broken URL in ContextMenu after adding Actions
Title: Message Title
mike bayer commented on JENKINS-27006
Re: Broken URL in ContextMenu after adding Actions
my jenkins returns broken // URLs for about half of the context menus. These can be seen on the UX but also coming back in the JSON from an AJAX call: https://jenkins.sqlalchemy.org/job/sqlalchemy_master/125/contextMenu output: {"items":[ {"displayName":"Changes","icon":"/static/c6533daf/images/24x24/notepad.png","post":false,"requiresConfirmation":false,"subMenu":null,"url":"//job/job/sqlalchemy_master/125/changes"} , {"displayName":"Console Output","icon":"/static/c6533daf/images/24x24/terminal.png","post":false,"requiresConfirmation":false,"subMenu":null,"url":"//job/job/sqlalchemy_master/125/console"} , {"displayName":"Edit Build Information","icon":"/static/c6533daf/images/24x24/notepad.png","post":false,"requiresConfirmation":false,"subMenu":null,"url":"//job/job/sqlalchemy_master/125/configure"} , {"displayName":"Polling Log","icon":"/static/c6533daf/images/24x24/clipboard.png","post":false,"requiresConfirmation":false,"subMenu":null,"url":"//job/job/sqlalchemy_master/125/pollingLog"} , {"displayName":"Git Build Data","icon":"/static/c6533daf/plugin/git/icons/git-32x32.png","post":false,"requiresConfirmation":false,"subMenu":null,"url":"//job/job/sqlalchemy_master/125/git"} , {"displayName":"No Tags","icon":"/static/c6533daf/images/24x24/save.png","post":false,"requiresConfirmation":false,"subMenu":null,"url":"//job/job/sqlalchemy_master/125/tagBuild"} , {"displayName":"Test Result","icon":"/static/c6533daf/images/24x24/clipboard.png","post":false,"requiresConfirmation":false,"subMenu":null,"url":"//job/job/sqlalchemy_master/125/testReport"} ]} note all the "//job/job" links. I am running SSL however I've tried all sorts of varieties of apache and jenkins settings (Setting project URL, unsetting project URL, setting project URL to "http" instead of "https") but nothing changes this.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-27006) Broken URL in ContextMenu after adding Actions
Title: Message Title mike bayer commented on JENKINS-27006 Re: Broken URL in ContextMenu after adding Actions > Access Jenkins directly instead of the reverse proxy. If the problem doesn't occur then, your config is broken and your problem a support-type question for the users mailing list or IRC. OK, so the problem is due to the ProxyPass setting. Doing the exact opposite of the note at https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache resolves, that is, don't put the trailing slash on the proxy URL. So, I need to click around some more and make sure this is not actually causing other problems. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-54415) jep-200 issue w/ matrix reloaded plugin
Title: Message Title mike bayer updated an issue Jenkins / JENKINS-54415 jep-200 issue w/ matrix reloaded plugin Change By: mike bayer Labels: JEP-200 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54415) jep-200 issue w/ matrix reloaded plugin
Title: Message Title mike bayer created an issue Jenkins / JENKINS-54415 jep-200 issue w/ matrix reloaded plugin Issue Type: Bug Assignee: Praqma Support Components: matrix-reloaded-plugin Created: 2018-11-02 04:02 Environment: jenkins 2.138.2 latest version of the matrix plugin (1.30 I think) and latest matrix reloaded plugin Priority: Minor Reporter: mike bayer getting one of those "failed to serialize" exceptions that seem to be reported everywhere re: the jep-200 change, with respect to the matrix reloaded plugin. this plugin is not listed at https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+fix+for+JEP-200, however when I uninstalled it, all the issues was having went away. the stack trace is below, and along with it, a successful matrix build fails to set itself as "successful" in some way, e.g. the junit.xml doesn't get written and it the lastSuccessfulBuild symlink seems to get reset, I don't know how all these things work but that's the handwavy summary. SEVERE: Failed to save build record java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.matrix.MatrixRun at hudson.XmlFile.write(XmlFile.java:200) at hudson.model.Run.save(Run.java:2015) at hudson.model.Run.execute(Run.java:1876) at hudson.matrix.MatrixRun.run(MatrixRun.java:153) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.matrix.MatrixRun at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at
[JIRA] (JENKINS-50547) Add support to Gerrit Trigger for WIP and Private changes (new in Gerrit 2.15)
Title: Message Title mike bayer commented on JENKINS-50547 Re: Add support to Gerrit Trigger for WIP and Private changes (new in Gerrit 2.15) > I have "Exclude Drafts" selected in my trigger configuration, and it appears that also applies to WIP changes in Gerrit 2.15 (i.e., WIP changes are not triggered). i just tried that locally here and WIP changes are triggered even with "exclude drafts" set. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54415) jep-200 issue w/ matrix reloaded plugin
Title: Message Title mike bayer commented on JENKINS-54415 Re: jep-200 issue w/ matrix reloaded plugin im on jenkins 2.138.3 now, have re-installed the matrix reloaded plugin after not having it for a few weeks and not seeing any of those errors, for some reason, and matrix builds are coming out fine including reloaded ones. but i dont know under what circumstances this serialization occurred. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
