[JIRA] [ssh-plugin] (JENKINS-27095) Unable to pass arguments to remote ssh (other than bash)
Title: Message Title Joshua Wherrett commented on JENKINS-27095 Re: Unable to pass arguments to remote ssh (other than bash) A possible solution is to put #!/bin/bash at the start of the script before the VARIABLE=VALUE lines. This would mandate the rest of the script be bash compatible though. Or maybe better solution is to find/replace all the known variables with values before writing the script contents to the tmp file and executing. 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] [ssh-plugin] (JENKINS-27095) Unable to pass arguments to remote ssh (other than bash)
Title: Message Title Joshua Wherrett commented on JENKINS-27095 Re: Unable to pass arguments to remote ssh (other than bash) In the mean time a possible workaround is to source a file that setenv's the variables used in the script at the start of the script. This sourced file will need to be configured in a previous local "Execute Shell" run and stored on a share that is accessible to the remote ssh host you are running on. A bit convoluted, however should get you out of trouble if you are stuck. 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] [ssh-plugin] (JENKINS-15265) Assumes default shell is bourne shell or bash and can not set jenkins environment varaibles if another shell
Title: Message Title Joshua Wherrett commented on JENKINS-15265 Re: Assumes default shell is bourne shell or bash and can not set jenkins environment varaibles if another shell This does not fix the problem when using a tcsh shell. VARIABLE=VALUE format does not work for tcsh. This issue should still be open. 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] [ssh-plugin] (JENKINS-15265) Assumes default shell is bourne shell or bash and can not set jenkins environment varaibles if another shell
Title: Message Title Joshua Wherrett commented on JENKINS-15265 Re: Assumes default shell is bourne shell or bash and can not set jenkins environment varaibles if another shell Or see JENKINS-27095 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] [walldisplay] (JENKINS-24192) Add HTTP Date response header to Jetty
Joshua Wherrett commented on JENKINS-24192 Add HTTP Date response header to Jetty Works great! Thanks for the quick turn-around. 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] [walldisplay] (JENKINS-24192) Add HTTP Date response header to Jetty
Joshua Wherrett created JENKINS-24192 Add HTTP Date response header to Jetty Issue Type: Bug Affects Versions: current Assignee: Christian Pelster Components: walldisplay Created: 11/Aug/14 1:24 AM Description: Embedded jetty doesn't appear to send Date in the HTTP response header. This is used by some plugins (Wall Display) to get Server time (see: https://issues.jenkins-ci.org/browse/JENKINS-21900). Is it possible to turn this on same as they did for Camel? (https://issues.apache.org/jira/i#browse/CAMEL-7360) Environment: Jenkins 1.574 running embedded Jetty webserver on RHEL 6. Fix Versions: current Project: Jenkins Labels: plugin jenkins Priority: Major Reporter: Joshua Wherrett 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-18366) Jetty should be used rather than Winstone for embedded deployments
Joshua Wherrett commented on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments Hi, I am having trouble getting the Jenkins webpage up using a Solaris 10 server (JRE 1.6.0_26-b03). The log shows Jenkins started successfully (Jenkins is fully up and running). However when I try to connect using a web browser (tried IE and Firefox from Jenkins server localhost and remote machines) it hangs indefinitely. Checking netstat shows the connection is ESTABLISHED. All versions of Jenkins prior to 1.535 work perfectly under Solaris 10 and no versions after 1.534 work. So I can only assume it was the introduction of Jetty in 1.535 that has caused this issue. Cheers, Josh 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.
