> On 4. Oct 2017, at 22:37, Richard Ginga wrote:
>
> nothing in my nginx configuration indicates any buffering explicitly one way
> or the other.
Time to re-read the first snippet in
https://wiki.jenkins.io/display/JENKINS/Jenkins+behind+an+NGinX+reverse+proxy
--
Am 04.10.2017 um 22:37 schrieb Richard Ginga:
Hi Michael, thanks for the response, nothing in my nginx configuration
indicates any buffering explicitly one way or the other.
Richard, just in case you are using any kind of anti-virus software on
the machine executing the CLI commands, it's
Hi Michael, thanks for the response, nothing in my nginx configuration
indicates any buffering explicitly one way or the other.
On Wed, Oct 4, 2017 at 3:17 PM, Michael Pailloncy <
michael.paillo...@gmail.com> wrote:
> If you run this very same command directly on the Jenkins server and
>
If you run this very same command directly on the Jenkins server and
without reaching it through your reverse proxy, does it work ?
I'm wondering if it's not related to the configuration of your reverse
proxy. As described in this documentation
is anybody out there?
my script syntax for this is
cmd = 'java -jar ~/Downloads/jenkins-cli.jar -noKeyAuth -s
https://stt-jenkins.disruptorbeam.com/ -auth
rginga:0793b086e3c9272ddeb0daff1093518c connect-node ' + params.NODENAME
st = sh(returnStatus: true, script: cmd)
On Wed,
I see a thread happening on CLI issues. I have a different question/issue
and do not want to hijack that other discussion.
when running any cli in a pipeline script I an getting below but the
command works
*00:04:11.368* + java -jar /Users/jenkins/Downloads/jenkins-cli.jar
-noKeyAuth -s