Re: CLI command to start jenkins job with default and overridenparameters

Thank you Daniel! Do you know if there is a way to pass a file parameter this way? On Thursday, January 10, 2019 at 1:51:03 AM UTC-8, Daniel Butler wrote: > > Hi Vicki, > > According to https://wiki.jenkins.io/display/JENKINS/Parameterized+Build, > for buildWithParameters you should use URL que

RE: CLI command to start jenkins job with default and overridenparameters

Hi Vicki, According to https://wiki.jenkins.io/display/JENKINS/Parameterized+Build, for buildWithParameters you should use URL query params to pass the values. To use your example: curl -v https://jenkins/job/JobName/buildWithParameters?targ_env=dev --user userName:userToken Regards, Daniel

Re: CLI/scripted way to stop scheduling any new builds on a given node?

Looks like you will have to look at writing a groovy script, maybe. You could offline it in a groovy script, then there must be some way to get the status of the node. Can probably put that in a 'while' loop until the node is idle. Then do your other work. You can send a groovy script to the sc

Re: CLI/scripted way to stop scheduling any new builds on a given node?

Unfortunately it doesn't work this way. If there is a long running job, "wait-node-offline" will not wait for it to finish. # time java -jar jenkins-cli.jar -s https://jenkins.my-domain -auth user:pass offline-node jenkins-node real0m1.249s user0m0.834s sys 0m0.049s At this point,

Re: CLI/scripted way to stop scheduling any new builds on a given node?

I think wait-offline-node is supposed to just wait until the node is actually offline. So you are supposed to run offline-node, then in your script you can wait-offline-node before you do whatever what you wanted to do after the node was offline. I would assume the node is not configured offlin

Re: CLI/scripted way to stop scheduling any new builds on a given node?

Actually, I still didn't find a solution to my problem. 1) I don't understand the purpose of "wait-node-offline" java -jar jenkins-cli.jar -s https://jenkins.my-domain -auth user:pass wait-node-offline some-node This will never exit, unless I use "offline-node" first. But "offline-node" exits

Re: CLI/scripted way to stop scheduling any new builds on a given node?

Great, thanks for confirming! I’ll update the docs. Thanks, Devin > On Oct 26, 2017, at 6:06 PM, 'Tomasz Chmielewski' via Jenkins Users > wrote: > > That was it! Adding proxy_buffering off helped. > > For reference, here is my SSL vhost definition: > > server { > > listen 443 ssl; >

Re: CLI/scripted way to stop scheduling any new builds on a given node?

That was it! Adding proxy_buffering off helped. For reference, here is my SSL vhost definition: server { listen 443 ssl; server_name jenkins.my-domain; ssl_certificate ssl/my-domain.crt; ssl_certificate_key ssl/my-domain.key; ssl_dhparam ssl/dhparam-2048

Re: CLI/scripted way to stop scheduling any new builds on a given node?

Some comments on https://issues.jenkins-ci.org/browse/JENKINS-43666 suggest that proxy_buffering off; is needed for SSL connections. (I was also testing nginx reverse proxies in the past and have that setting in my SSL config; might have forg

Re: CLI/scripted way to stop scheduling any new builds on a given node?

nginx vhost is almost the exact copy of the vhost on https://wiki.jenkins.io/display/JENKINS/Jenkins+behind+an+NGinX+reverse+proxy: upstream jenkins { server 127.0.0.1:8080 fail_timeout=0; } server { listen 80; server_name jenkins.my-domain; add_header X-Frame-Options SAMEORIGI

Re: CLI/scripted way to stop scheduling any new builds on a given node?

Make sure to follow https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Nginx if Nginx is configured as a a reverse proxy. Notably proxy_http_version 1.1; and proxy_request_buffering off; are required for your v

Re: CLI/scripted way to stop scheduling any new builds on a given node?

Except... it doesn't seem to work. $ java -jar jenkins-cli.jar -s https://jenkins-url -auth user:pass help offline-node $ echo $? 255 In nginx log: 10.11.0.8 - user [26/Oct/2017:21:11:51 +] "GET / HTTP/1.1" 200 150393 "-" "Java/1.8.0_131" 10.11.0.8 - user [26/Oct/2017:21:11:52 +] "GET

Re: CLI/scripted way to stop scheduling any new builds on a given node?

Got it, thanks: https://wiki.jenkins.io/display/JENKINS/Jenkins+CLI On Friday, October 27, 2017 at 5:57:18 AM UTC+9, Robert Hales wrote: > > You have to use the Jenkins CLI. I guess that can be a bit confusing. It > isn't a script available to run at the command line. Jenkins has their own > CL

Re: CLI/scripted way to stop scheduling any new builds on a given node?

You have to use the Jenkins CLI. I guess that can be a bit confusing. It isn't a script available to run at the command line. Jenkins has their own CLI. If you google for it, you will find the details pretty easily. On Thursday, October 26, 2017 at 2:55:07 PM UTC-6, Tomasz Chmielewski wrote: >

Re: CLI/scripted way to stop scheduling any new builds on a given node?

Hmm, where do I find "offline-node" command? root@jenkins:~# dpkg -L jenkins /. /usr /usr/share /usr/share/doc /usr/share/doc/jenkins /usr/share/doc/jenkins/changelog.gz /usr/share/doc/jenkins/copyright /usr/share/jenkins /usr/share/jenkins/jenkins.war /etc /etc/logrotate.d /etc/logrotate.d/jenkin

Re: CLI/scripted way to stop scheduling any new builds on a given node?

In the CLI, use the 'offline-node' command. Another useful command in what it looks like you want to do might be "wait-offline-node". You could also create a groovy script to do it and run that from the REST API. On Thursday, October 26, 2017 at 3:35:29 AM UTC-6, Tomasz Chmielewski wrote: > >

Re: CLI Created Jobs Do Not Run

On 8 October 2015 at 15:09, Hilco Wijbenga wrote: > I am experiencing a strange issue. I am successfully creating new jobs using > Jenkins CLI "create-job" + "enable-job" but these jobs are not triggered > (they use "Build Periodically"). If I go in and change something through the > UI (e.g., I c

Re: CLI Commander Plugin seemingly does nothing

On Thu, 02 Jul 2015 11:17:08 +0200, Itai Sanders wrote: got it. thanks! do I understand that the plugin does not show the results of a command (I tried using the who-am-i command to see if the plugin gets the authentication correctly. the page refreshed but nothing showed). or am I still doi

Re: CLI Commander Plugin seemingly does nothing

On Wed, 01 Jul 2015 10:40:34 +0200, Itai Sanders wrote: Problem is - as much as I looked throughout the Jenkins web UI, I couldn't find anywhere to run the CLI commands. I tried looking into the global settings and into job configurations, but nothing new pops up after installing the plugin.

Re: CLI regression or new error?

This was the tweet I sent last night - no response so not sure if @jenkinsci is considered a valid way to pass things on. @jenkinsci so, just to confirm: the regression in hudson.remoting.SynchronousCommandTransport$ReaderThread occurs in 1.576. 1.575 is good. C

Re: CLI list-jobs words, but get-job on ANY of the listed jobs says "No such job"

That is weird and told nowhere! :-( How to get the "real" job name from the listed "display" job names? Am Mittwoch, 12. März 2014 22:32:55 UTC+1 schrieb Daniel Beck: > > Likely because list-jobs prints the display name, while get-job requires > the actual job name to be specified. > > Another

Re: CLI list-jobs words, but get-job on ANY of the listed jobs says "No such job"

Likely because list-jobs prints the display name, while get-job requires the actual job name to be specified. Another possibility is that folders are involved (but that'd require you to query a specific view's items in get-jobs). On 12.03.2014, at 09:46, k...@quipsy.de wrote: > When I do list-

RE: CLI

>> looks like CLI is completely broken. >> I cannot auth via u/p and not even via ssh keys. What release are you using? Has this ever worked for you, or are you trying it for the first time? Post the exact command you are using, and the response. -- This e-mail and any attachments may contain

RE: CLI command failing since Friday 10/18/13

I think I might have found the issue. I "think" I was trying to force run a job that was waiting for an executor on the master. The master had 2 hung jobs. From: Ginga, Dick Sent: Monday, October 21, 2013 9:34 AM To: jenkinsci-users@googlegroups.com Subject: CLI command failing since Friday 10/18

Re: CLI Authentication using Unix Users

Thanks Sami, I will try that. In fact I will also try the key based authentication. Somehow I missed that part earlier. Will be trying out sometime next week as out on vacation

Re: CLI Authentication using Unix Users

I have often found the ssh access to be useful when other kind of authentication has been problematic. Have you seen https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+SSH ? -- Sami 2012/5/2 Anshul : > Hi, > One of my Jenkins job actually creates a new job using the cli > interface. The creator

Re: CLI Causes Server to Crash?

I think I figured it out... I had a system.exit() as the last line in my script! Left over from something else :-( On Mon, Mar 19, 2012 at 8:54 PM, Jay Flowers wrote: > Yep :-( Same version... > > > On Mon, Mar 19, 2012 at 2:02 PM, Sami Tikka wrote: > >> Sorry, no idea. Grasping at straws here

Re: CLI Causes Server to Crash?

Yep :-( Same version... On Mon, Mar 19, 2012 at 2:02 PM, Sami Tikka wrote: > Sorry, no idea. Grasping at straws here: Do your CLI and Jenkins have > the same version? > > -- Sami > > 2012/3/19 Jay Flowers : > > When I execute a simple groovy script over the CLI the server crashes > with > > this

Re: CLI Causes Server to Crash?

Sorry, no idea. Grasping at straws here: Do your CLI and Jenkins have the same version? -- Sami 2012/3/19 Jay Flowers : > When I execute a simple groovy script over the CLI the server crashes with > this error: > > Exception in thread "jI_GarbageCollector" java.lang.NoClassDefFoundError: > org/ji