[JIRA] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Philip Cheong commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Michael Neale isn't a "step" still just a step, regardless if it is defined to run in parallel or not? From a basic user-feedback perspective, what I want to see is: 1. Tell me what stages are defined, which one is running now, and what time it has taken or estimated to complete. (I think the existing graphics and animations are all adequate in this area). 2. If there are multiple steps inside the stage, tell me what step we are on, what time it has taken or estimated to complete. (This is what I am missing) Since pipeline stage-progress works from left to right, I'd like to see step-progress displayed from top to bottom for that specific pipeline animation. It doesn't concern me that the pipeline animation would then become be a dynamic height (as it is already dynamic length). Maybe it's a good option to make a check-box in the job configuration that I can click that shows or hides the steps inside the stages. I tend to work with large and complex pipelines (Currently on a project with > 880 git repos) so when I'm introducing CI/CD to different audiences these graphical front ends are really important when it comes to demo time so that the white-board concepts make sense with what I'm creating in the tools. 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] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Philip Cheong commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage I would be happy with something more simple such as this: https://wiki.jenkins-ci.org/download/attachments/69764097/screenshot2.png?version=1=1400172472000 ...where the box indicating the stage simply displays the number of parallel steps that it will run. Bonus points for each step having it's own progress bar! 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] [rake-plugin] (JENKINS-7947) Rake plugin can't always find Rake with rvm installed
Title: Message Title Philip Cheong edited a comment on JENKINS-7947 Re: Rake plugin can't always find Rake with rvm installed I would say this issue should be reopened. I seems to have the this same problem I believe:Environment:RHEL6.7Jenkins 1.609.3Rake plugin 1.8rvm installed globally under /usr/local/rvmRake plugin configuration:Rvm installation path: /usr/local/rvmRuby installation: name: defaultRUBY_HOME: /usr/local/rvm/rubies/defaultname: 2.0.0RUBY_HOME: /usr/local/rvm/rubies/ruby and raised JENKINS - 2 30356 . 0.0-p643 jenkins user has been added to rvm groupConsole error from job when configured to run with rake-plugin:[devtest] $ /usr/local/rvm/rubies/ruby-2.0.0-p643/bin/rake -T/usr/bin/env: ruby: No such file or directoryBuild step 'Invoke Rake' marked build as failureNotifying upstream projects of job completionFinished: FAILURERunning the job via shell with this configuration runs as expected:source /etc/profile.d/rvm.sh &> /dev/nullbundle installrake --versionruby --versionrake -T Is this plugin still actively maintained though ? 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] [rake-plugin] (JENKINS-7947) Rake plugin can't always find Rake with rvm installed
Title: Message Title Philip Cheong edited a comment on JENKINS-7947 Re: Rake plugin can't always find Rake with rvm installed I seems seem to have this same problem and have raised JENKINS-30356 rather than reopen this one .Is this plugin still actively maintained though? 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] [rake-plugin] (JENKINS-30356) Rake plugin can't always find Rake
Title: Message Title Philip Cheong created an issue Jenkins / JENKINS-30356 Rake plugin can't always find Rake Issue Type: Bug Assignee: david_calavera Components: rake-plugin Created: 09/Sep/15 7:25 AM Environment: RHEL6.7 Jenkins 1.609.3 Rake plugin 1.8 Rake plugin configuration: Rvm installation path: /usr/local/rvm Ruby installation: name: default RUBY_HOME: /usr/local/rvm/rubies/default name: 2.0.0 RUBY_HOME: /usr/local/rvm/rubies/ruby-2.0.0-p643 Priority: Major Reporter: Philip Cheong This seems to be the same issue as JENKINS-7947 but I decided to raise a new issue rather than try to reopen the old one. jenkins user has been added to rvm group Console error from job when configured to run with rake-plugin: [devtest] $ /usr/local/rvm/rubies/ruby-2.0.0-p643/bin/rake -T /usr/bin/env: ruby: No such file or directory Build step 'Invoke Rake' marked build as failure Notifying upstream projects of job completion Finished: FAILURE Running the job via shell with this configuration works as expected: source /etc/profile.d/rvm.sh &> /dev/null bundle install rake --version ruby --version rake -T
[JIRA] [rake-plugin] (JENKINS-30356) Rake plugin can't always find Rake
Title: Message Title Philip Cheong updated an issue Jenkins / JENKINS-30356 Rake plugin can't always find Rake Change By: Philip Cheong This seems to be the same issue as JENKINS-7947 but I decided to raise a new issue rather than try to reopen the old one.jenkins user has been added to rvm groupConsole error from job when configured to run with rake-plugin:[devtest] $ /usr/local/rvm/rubies/ruby-2.0.0-p643/bin/rake -T/usr/bin/env: ruby: No such file or directoryBuild step 'Invoke Rake' marked build as failureNotifying upstream projects of job completionFinished: FAILURERunning the job via shell with this configuration works as expected:source /etc/profile.d/rvm.sh &> /dev/nullbundle installrake --versionruby --versionrake -T And produces this output:[devtest] $ /bin/bash -xe /tmp/hudson5194824731866794680.sh+ source /etc/profile.d/rvm.sh+ bundle installUsing rake 10.4.2Using hostlist_expression 0.2.1Using oj 2.12.13Using multi_json 1.11.2Using rspec-support 3.3.0Using rspec-core 3.3.2Using diff-lcs 1.2.5Using rspec-expectations 3.3.1Using rspec-mocks 3.3.2Using rspec 3.3.0Using rspec-its 1.2.0Using net-ssh 2.9.2Using net-scp 1.2.1Using net-telnet 0.1.1Using sfl 2.2Using specinfra 2.43.2Using serverspec 2.23.1Using ansible_spec 0.2.1Using bundler 1.10.6Bundle complete! 12 Gemfile dependencies, 19 gems now installed.Use `bundle show [gemname]` to see where a bundled gem is installed.+ rake --versionrake, version 10.4.2+ ruby --versionruby 2.0.0p643 (2015-02-25 revision 49749) [x86_64-linux]+ rake serverspec:test-playbookRun serverspec for test-playbook to devtest Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [rake-plugin] (JENKINS-7947) Rake plugin can't always find Rake with rvm installed
Title: Message Title Philip Cheong commented on JENKINS-7947 Re: Rake plugin can't always find Rake with rvm installed I would say this issue should be reopened. I have the same problem I believe: Environment: RHEL6.7 Jenkins 1.609.3 Rake plugin 1.8 rvm installed globally under /usr/local/rvm Rake plugin configuration: Rvm installation path: /usr/local/rvm Ruby installation: name: default RUBY_HOME: /usr/local/rvm/rubies/default name: 2.0.0 RUBY_HOME: /usr/local/rvm/rubies/ruby-2.0.0-p643 jenkins user has been added to rvm group Console error from job when configured to run with rake-plugin: [devtest] $ /usr/local/rvm/rubies/ruby-2.0.0-p643/bin/rake -T /usr/bin/env: ruby: No such file or directory Build step 'Invoke Rake' marked build as failure Notifying upstream projects of job completion Finished: FAILURE Running the job via shell with this configuration runs as expected: source /etc/profile.d/rvm.sh &> /dev/null bundle install rake --version ruby --version rake -T Is this plugin still actively maintained? 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-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Philip Cheong commented on JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted I downgraded to the LTS Jenkins ver. 1.580.1 today and just hit 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 -- 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-status-plugin] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Philip Cheong reopened JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted I have this this issue multiple times using in the last few days the swarm plugin on Jenkins ver 1.586. The jenkins master is a brand new server and installation. No jobs have previously run on it. The only thing I'm testing is the connection of news slaves. This is a stochastic issue however. Sometimes it works fine, and sometimes it results in this error (maybe 30% of the time). JNLP agent connected from /172.31.8.131 ===JENKINS REMOTING CAPACITY===Failed to establish the connection with the slave dev-master.phil java.io.IOException: NioChannelHub is not currently running at org.jenkinsci.remoting.nio.NioChannelHub$1.makeTransport(NioChannelHub.java:479) at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:220) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:149) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:159) at org.jenkinsci.remoting.nio.NioChannelBuilder.build(NioChannelBuilder.java:36) at org.jenkinsci.remoting.nio.NioChannelBuilder.build(NioChannelBuilder.java:52) at jenkins.slaves.JnlpSlaveAgentProtocol$Handler.jnlpConnect(JnlpSlaveAgentProtocol.java:120) at jenkins.slaves.DefaultJnlpSlaveReceiver.handle(DefaultJnlpSlaveReceiver.java:63) at jenkins.slaves.JnlpSlaveAgentProtocol2$Handler2.run(JnlpSlaveAgentProtocol2.java:57) at jenkins.slaves.JnlpSlaveAgentProtocol2.handle(JnlpSlaveAgentProtocol2.java:31) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:156) Change By: Philip Cheong (30/Oct/14 2:39 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/d/optout.
[JIRA] [slave-status-plugin] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Philip Cheong edited a comment on JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted I have this this issue multiple times using in the last few days the swarm plugin on Jenkins ver 1.586. The jenkins master is a brand new server running RHEL 6.5. The slave is also RHEL 6.5. No jobs have previously run on it. The only thing I'm testing is the connection of news slaves. This is a stochastic issue however. Sometimes it works fine, and sometimes it results in this error (I guess maybe 30% of the time). JNLP agent connected from /172.31.8.131 ===JENKINS REMOTING CAPACITY===Failed to establish the connection with the slave dev-master.phil java.io.IOException: NioChannelHub is not currently running at org.jenkinsci.remoting.nio.NioChannelHub$1.makeTransport(NioChannelHub.java:479) at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:220) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:149) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:159) at org.jenkinsci.remoting.nio.NioChannelBuilder.build(NioChannelBuilder.java:36) at org.jenkinsci.remoting.nio.NioChannelBuilder.build(NioChannelBuilder.java:52) at jenkins.slaves.JnlpSlaveAgentProtocol$Handler.jnlpConnect(JnlpSlaveAgentProtocol.java:120) at jenkins.slaves.DefaultJnlpSlaveReceiver.handle(DefaultJnlpSlaveReceiver.java:63) at jenkins.slaves.JnlpSlaveAgentProtocol2$Handler2.run(JnlpSlaveAgentProtocol2.java:57) at jenkins.slaves.JnlpSlaveAgentProtocol2.handle(JnlpSlaveAgentProtocol2.java:31) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:156) 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.
