[JIRA] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title Lance Johnston commented on JENKINS-31746 Re: Build pipeline elements overflow without proper feedback +1 Seeing this with build pipeline plugin 1.4.9 and Jenkins 1.609.2. Can't believe there are no updates on this issue, which is totally a show stopper. Gonna have to do some rollbacks to try and get back to a usable state. 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] [build-pipeline-plugin] (JENKINS-25430) Clicking on "console" icon doesn't work
Title: Message Title Lance Johnston commented on JENKINS-25430 Re: Clicking on "console" icon doesn't work Indeed, the problem turned out to be related to the jenkins URL in the system configuration. Specifically, my apache reverse proxy was down and I was using the direct jenkins url, bypassing the one in the system configuration, when I encountered this problem. Once the reverse proxy was back up, console output started working again. 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] [build-pipeline-plugin] (JENKINS-25430) Clicking on "console" icon doesn't work
Title: Message Title Lance Johnston commented on JENKINS-25430 Re: Clicking on "console" icon doesn't work Just tried with 1.4.9 and Jenkins 1.609.2 and this does not appear to be fixed. 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] [nested-view-plugin] (JENKINS-17352) Manage columns
Title: Message Title Lance Johnston commented on JENKINS-17352 Re: Manage columns While this ticket is indeed resolved, it is a resolution that works around the problem rather than solving it. While disabling the columns does eliminate the performance issue, ideally we'd have the option of enabling the columns and having the display be performant. Is such a solution possible? I'd be happy to open a separate ticket, but not knowing if it's doable or not, I didn't want to open a ticket just to have it closed. 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] [hipchat-plugin] (JENKINS-28314) Support non-notify messages
Title: Message Title Lance Johnston commented on JENKINS-28314 Re: Support non-notify messages +1 ... Just installed the hipchat plugin and am amazed that popups in rooms is not an option. 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] [hipchat-plugin] (JENKINS-18127) Add an option to enable room notification
Title: Message Title Lance Johnston commented on JENKINS-18127 Re: Add an option to enable room notification +1 ... Just installed the hipchat plugin and am amazed that popups in rooms (for non-failures) is not an option. 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] [hipchat-plugin] (JENKINS-18127) Add an option to enable room notification
Title: Message Title Lance Johnston commented on JENKINS-18127 Re: Add an option to enable room notification Ideally, this would be configurable per notification per job as opposed to some sort of global configuration. 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] [hipchat-plugin] (JENKINS-28314) Support non-notify messages
Title: Message Title Lance Johnston commented on JENKINS-28314 Re: Support non-notify messages aldaris - Ideally, I'd prefer this be configurable per notification per job. We have lots of jobs where I don't want or need to see a popup on start, success, end, etc. We also have jobs where I am interested in those events. 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] [job-node-stalker-plugin] (JENKINS-23125) Node Stalker does not work with job in folders
Lance Johnston commented on JENKINS-23125 Node Stalker does not work with job in folders Hi - Any idea when 1.0.4 might be released to the repository? Thanks, Lance 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] [warnings-plugin] (JENKINS-26311) Warning plugin archives do not exist
Lance Johnston created JENKINS-26311 Warning plugin archives do not exist Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 06/Jan/15 7:21 PM Description: The warnings plugin does not exist in the plugins download site at "https://updates.jenkins-ci.org/download/plugins/". It does exist at "https://updates.jenkins-ci.org/latest/warnings.hpi", but no releases other than latest appear to be available. Project: Jenkins Labels: plugin plugins Priority: Minor Reporter: Lance Johnston 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] [job-node-stalker-plugin] (JENKINS-23125) Node Stalker does not work with job in folders
Lance Johnston commented on JENKINS-23125 Node Stalker does not work with job in folders This was actually fixed with a pull request I submitted that was accepted a while back. It's in the 1.0.4 release, but that release is not available in the plugin center. 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-23094) HTTP error 405 when trying to restart ssh host
Lance Johnston commented on JENKINS-23094 HTTP error 405 when trying to restart ssh host So what LTS will this appear in? Wouldn't this warrant a patch to the current 1.565 LTS version? 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] [nodejs] (JENKINS-21726) Nodejs path not set correctly when running on Windows master, linux slave
Lance Johnston created JENKINS-21726 Nodejs path not set correctly when running on Windows master, linux slave Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: nodejs Created: 07/Feb/14 11:06 PM Description: In the described environment, the nodejs job on the linux slave gets an incorrect path as the nodejs '.../bin' location gets added to the job's path using a Windows path separator ( rather than a linux path separator(. Environment: Jenkins master running on windows. Nodejs job running on linux slave. Project: Jenkins Labels: plugin Priority: Major Reporter: Lance Johnston 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] [build-pipeline] (JENKINS-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Lance Johnston commented on JENKINS-19121 Build pipeline plugin no longer prompts for parameters of parameterised job Can confirm this is an issue with Jenkins 1.532.1 and build-pipeline-plugin 1.4.2. This is something of a showstopper for us when it comes to setting up our build pipelines. We need to be able to have manual jobs in our pipeline that will prompt the user for input. 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] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Lance Johnston commented on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 Some more data points... we have the exact same issue with an rpm install of 1.480.3 on SLES 11 SP2 (rpm from http://pkg.jenkins-ci.org/opensuse-stable/). Uninstalled, installed 1.466.2 same issue. Uninstalled, installed 1.512 and the issue is gone. Really hate going with non-LTS release, so just to be sure, uninstalled 1.512 and reinstalled 1.480.3 again and the problem was back. Uninstalled and reinstalled 1.512 again and all is working. Guess I'll have to stick with 1.512 and hope that we get to a 1.5x LTS soon. 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-17151) Jenkins fails to start after upgrading to 1.505
Lance Johnston commented on JENKINS-17151 Jenkins fails to start after upgrading to 1.505 Same here with 1.512. 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.
