Bitbucket Branch Source Plugin & Endpoints

2017-10-04 Thread Richard Bywater
Hi

One of my colleagues is trying to get Jenkins 2 up and running with the
Bitbucket Branch Source plugin using our Bitbucket Server infrastructure.

We've run into an issue with the plugin as it appears it expects the server
URL defined in the Bitbucket endpoint configuration to be the same as the
one to be used for cloning purposes even for SSH.

So for instance if you have defined
https://bitbucketserver.example.com/bitbucket as the server URL, when
cloning via SSH it attempts to use ssh://bitbucketserver.example.com:7999
(where 7999 is correctly read out of the clone link URLs returned by the
Bitbucket API). In our case however, the web URL is different to the SSH
url. For instance, based on the previous example, our SSH address is ssh://
actualservername.example.com:7999/

My question is that, rather than reusing the server URL for cloning
operations, is there a reason why the clone URLs returned by the API for a
repository aren't used instead? This would seem to allow Bitbucket to tell
the plugin exactly where to look in case any other corner cases like this
come up.

Cheers
Richard.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAMui945Sck2UTwhw8n7Ny0hbzc6CC_Aon8tDsXTBGa8cHzRFsw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Nagios & Jenkins

2017-10-04 Thread Robert Hales
Can you set your nagios to not alert so quickly? Make it have a couple more 
failures or an extra minute between checks so it goes into a soft state for 
a minute first. 

Why can't you write a brief downtime to the nagios.cmd file in Jenkins 
first? 

You could disable notifications using a curl command (google it). 



On Wednesday, October 4, 2017 at 5:11:58 PM UTC-6, FirstName LastName wrote:
>
> have a simple Jenkins deploy job (works great)
>
> however, every time a deploy is done, app restarts , we get alert that app 
> is down
>
> is there a way to have Jenkins start a deploy  by disabling nagios, wait x 
> min,
> then do the app restart?  configuring downtime windows, or manually 
> setting on
> before a deploy is not an option.
>
> Hopefully someone's already got an elegant solution for this?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0ae21045-3227-49d7-b179-f2f736ff160b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Nagios & Jenkins

2017-10-04 Thread FirstName LastName
have a simple Jenkins deploy job (works great)

however, every time a deploy is done, app restarts , we get alert that app 
is down

is there a way to have Jenkins start a deploy  by disabling nagios, wait x 
min,
then do the app restart?  configuring downtime windows, or manually setting 
on
before a deploy is not an option.

Hopefully someone's already got an elegant solution for this?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9761f99d-1169-4aa2-b19d-c01c0bb7ee6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins pipeline prematurely kills docker container

2017-10-04 Thread xstourac
Hi all,

I am currently dealing with very weird behaviour of my Jenkins instance. I 
want to use docker containers via pipeline to build my app. But everytime I 
tried even something simple like this:

node() {
  stage('Build') {
docker.image('debian:stretch').inside() {
  sh 'sleep 20'
}
  }
}

Jenkins kills the container after less than 1 second without any 
explanaition anywhere (see attached stretch.log). But what is interesting, 
when I change docker image to debian:jessie (oldstable), everything is 
working correctly (see attached jessie.log). I also tried executing same 
code on jessie and stretch nodes, but it was exactly the same.

Can you please help me or at least give some hints/links? I am really 
stucked and out of ideas. I am using Jenkins 2.73.1 with all plugins 
updated (today) running directly on Debian Jessie host.

Thank you in advance,
Jan Stourac.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1e65b831-72fc-41b8-b38e-0f1afebbc046%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Started by user admin
[Pipeline] node
Running on master in /var/lib/jenkins/workspace/test
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Build)
[Pipeline] sh
[test] Running shell script
+ docker inspect -f . debian:jessie
.
[Pipeline] withDockerContainer
Jenkins does not seem to be running inside a container
$ docker run -t -d -u 108:113 -w /var/lib/jenkins/workspace/test -v 
/var/lib/jenkins/workspace/test:/var/lib/jenkins/workspace/test:rw,z -v 
/var/lib/jenkins/workspace/test@tmp:/var/lib/jenkins/workspace/test@tmp:rw,z -e 
 -e  -e  -e  -e  -e  -e 
 -e  -e  -e  -e  -e  -e 
 -e  -e  -e  -e  -e  -e 
 -e  -e  -e  -e  -e  -e 
 --entrypoint cat debian:jessie
[Pipeline] {
[Pipeline] sh
[test] Running shell script
+ sleep 20
[Pipeline] }
$ docker stop --time=1 
aee0eb563f8a7666f9cce9c23b5607906cef9466323f048dc612a42d4fe7c570
$ docker rm -f aee0eb563f8a7666f9cce9c23b5607906cef9466323f048dc612a42d4fe7c570
[Pipeline] // withDockerContainer
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESSStarted by user admin
[Pipeline] node
Running on master in /var/lib/jenkins/workspace/test
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Build)
[Pipeline] sh
[test] Running shell script
+ docker inspect -f . debian:stretch
.
[Pipeline] withDockerContainer
Jenkins does not seem to be running inside a container
$ docker run -t -d -u 108:113 -w /var/lib/jenkins/workspace/test -v 
/var/lib/jenkins/workspace/test:/var/lib/jenkins/workspace/test:rw,z -v 
/var/lib/jenkins/workspace/test@tmp:/var/lib/jenkins/workspace/test@tmp:rw,z -e 
 -e  -e  -e  -e  -e  -e 
 -e  -e  -e  -e  -e  -e 
 -e  -e  -e  -e  -e  -e 
 -e  -e  -e  -e  -e  -e 
 --entrypoint cat debian:stretch
[Pipeline] {
[Pipeline] sh
[test] Running shell script
+ sleep 20
[Pipeline] }
$ docker stop --time=1 
ece1d7bae016d0848edf035696fa627d7db736a33d3e13c5bb02bc17b709c1fd
$ docker rm -f ece1d7bae016d0848edf035696fa627d7db736a33d3e13c5bb02bc17b709c1fd
[Pipeline] // withDockerContainer
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code -1
Finished: FAILURE

Re: Is there any difference between "shell" and "sh"?

2017-10-04 Thread Victor Martinez
Hey,

   https://jenkins.io/doc/book/pipeline/syntax/#declarative-steps explains 
it.

Cheers

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9e15ddfb-1855-4bbb-a777-816382b74264%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Why does the jenkinsfile use a closure in this way?

2017-10-04 Thread red 888


Its a command pattern to write jenkins pipeline code like this:

def call(body) {

def config = [:]
body.resolveStrategy = Closure.DELEGATE_FIRST
body.delegate = config
body()

Im not sure how to word this simply, but this closure get implicitly 
imported and can be called by the file name of the .groovy file it lives in.

I call it like: MyClosher{myarg ='sdfsdf}

I not entirely sure what this is doing. Its doing call(body) and then 
assigning body as the delegate. so that means the closure i pass it is the 
delegate, but isn't that just the owner? wah me confused.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/82e5ff55-0ea9-4ca5-88d4-9b9fe7201ee5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Is there any difference between "shell" and "sh"?

2017-10-04 Thread dandeliondodgeball
Sorry, meant "script" and "sh".

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/69c25276-d61e-43af-a790-7c9a9eed102a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Fail to install Jenkins slave agent as a service

2017-10-04 Thread Victoria Wei Lei
Ewelina,  

I did run slave-agent.jnlp from command line,  agent started running,  
however I did not have running slave pop up which give me the option from 
file -> Install as a service (:

Thanks


On Friday, September 29, 2017 at 7:47:07 AM UTC-5, Ewelina Wilkosz wrote:
>
> Did you manage to make it work? 
> because I do it differently, usually:
>
> - download slave-agent.jnlp from agent page - I think it's under this 
> 'launch via web' button, or something, I don't remember what it says :) 
> - open a command window with "Run as Administrator".
> - change directory to the place where you saved the slave-agent.jnlp file.
> - run "slave-agent.jnlp"
> - now with the running slave click the menu item to "Install as Service".
> - run services.msc and you can find and configure your service
>
> So it is a little bit simpler command in cmd, maybe not making any 
> difference... but you have to try everything :)
>
> On Friday, September 22, 2017 at 11:15:31 PM UTC+2, Victoria Wei Lei wrote:
>>
>> yes, you need to attach that secret key in the command
>>
>> On Friday, September 22, 2017 at 3:22:01 PM UTC-5, slide wrote:
>>>
>>> The instructions on my Jenkins install also have a -secret parameter, 
>>> does yours? Are you passing in the secret?
>>>
>>> On Fri, Sep 22, 2017 at 1:14 PM Victoria Wei Lei  
>>> wrote:
>>>
 run command from your slave path:

 $ java -jar slave.jar -jnlpUrl 
 http://yourserver:port/computer/slave-name/slave-agent.jnlp (the full 
 command should be listed on your launch screen)


 make sure slave.jar was copied there. A copy of slave.jar can be 
 downloaded from http://yourserver:port/jnlpJars/slave.jar 



 On Friday, September 22, 2017 at 2:58:10 PM UTC-5, slide wrote:

> How are you running from the command line? 
>
> On Fri, Sep 22, 2017 at 11:00 AM Victoria Wei Lei  
> wrote:
>
 Ewelina, 
>>
>> thanks so much for the reply.  I tried command line before as admin, 
>>  yes, the slave can launch successfully,  but am I supposed to get Slave 
>> agent  pop up and the option to Install as a service?  I did not have 
>> pop 
>> up window as I start by web start.  Therefore, I can't install slave as 
>> a 
>> window service.  If cmd window got killed for some reason,  my slave 
>> agent 
>> died as well.  
>>
>> Victoria 
>>
>>
>> On Friday, September 22, 2017 at 11:20:47 AM UTC-5, Ewelina Wilkosz 
>> wrote:
>>>
>>> Not sure if it will solve your issue, but what I usually do is I 
>>> download the file instead of running it from the browser - the one you 
>>> have 
>>> under web start button - then run 'cmd' as administrator, there I cd to 
>>> directory with downloaded file and run it from there. If you're 
>>> familiar 
>>> with command line it should be easy :) if not I can try to provide more 
>>> details. But in general running it as admin solved a similar (I think, 
>>> I 
>>> don't remember) problem I had
>>
>> -- 
>> You received this message because you are subscribed to the Google 
>> Groups "Jenkins Users" group.
>>
> To unsubscribe from this group and stop receiving emails from it, send 
>> an email to jenkinsci-use...@googlegroups.com.
>
>
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/6790b416-5113-4a86-9ff1-6b4bb1fbe534%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
 You received this message because you are subscribed to the Google 
 Groups "Jenkins Users" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to jenkinsci-use...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-users/17c37bba-9ab8-4125-a4c3-3b6f7c7481e3%40googlegroups.com
  
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e7ac804e-4a62-435d-a73b-3fd6723350a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Is there any difference between "shell" and "sh"?

2017-10-04 Thread dandeliondodgeball
Sorry, as I sort of have an online conversation with myself.

I guess "shell" isn't the same as running something from the command line.

pipeline {
agent any
stages {
stage('ViewArchive') {
steps {
// Works
sh 'unzip -l packages/archive.zip'


/* Doesn't work
script {
unzip -l packages/archive.zip
}

*/

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8f7aaced-f87b-49a4-b155-3b89f2b211a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: LTS support timelines

2017-10-04 Thread lv via Jenkins Users
Thank you for the quick reply!

On Wednesday, October 4, 2017 at 2:31:40 PM UTC-4, R Tyler Croy wrote:
>
> (replies inline) 
>
> On Wed, 04 Oct 2017, lv via Jenkins Users wrote: 
>
> > Hi All, 
> > 
> > I'm one of the people maintaining the public Jenkins installation of the 
> > Apache Impala (Incubating) project, and since it is facing the public 
> > internet we're particularly interested in keeping our installation 
> secure. 
> > We are currently running LTS 2.46.3 and I'm trying to figure out whether 
> > such old LTS releases are still supported, and for how long. 
> > 
> > I looked at the page describing the LTS Release Line and from there it 
> is 
> > not clear to me whether only the latest release line (currently 2.73.X) 
> > will receive security fixes, or whether older lines receive those, too. 
> If 
> > they do, what is the latest LTS line that will receive security update 
> > and/or that is considered when looking at the impact of newly found 
> > security issues? 
>
>
> Older LTS releases are in no way supported by the Jenkins project and do 
> not 
> receive backports of any kind. 
>
> I strongly recommend to always follow the latest LTS versions. 
> ci.jenkins.io 
> (which I maintain) runs 2.73.1 for example, and when we roll new releases, 
> I 
> make sure to upgrade :) 
>
>
>
> - R. Tyler Croy 
>
> -- 
>  Code:  
>   Chatter:  
>  xmpp: rty...@jabber.org  
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F 
> -- 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/547e13fb-193f-4ea5-b048-ff5abc6693df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Is there any difference between "shell" and "sh"?

2017-10-04 Thread dandeliondodgeball
Is one preferred / better?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/82506476-f358-41b6-9562-a00a381aab4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Stages which are not Build, Test, or Deploy

2017-10-04 Thread dandeliondodgeball
Tested again, and wasn't able to recreate the issue.  Seeing stages with 
other names in Jenkins now.  Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/52c4cc10-94da-4148-9f55-ec8a29e7235c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Another CLI question

2017-10-04 Thread Richard Ginga
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
> 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
> , you
> need to ensure that it doesn't buffer request/response bodies when serving
> Jenkins through HTTPS.
>
> Hopefully it helps.
>
> 2017-10-04 19:01 GMT+02:00 Richard Ginga :
>
>> 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, Oct 4, 2017 at 10:08 AM, Richard Ginga 
>> wrote:
>>
>>> 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 https://stt-jenkins.disruptorbeam.com/ -auth 
>>> rginga:xx connect-node perf-test-client3
>>>
>>> *00:04:28.597* Oct 04, 2017 9:52:34 AM hudson.cli.CLI$5 run*00:04:28.597* 
>>> WARNING: null*00:04:28.597* java.io.IOException: Stream is 
>>> closed*00:04:28.597*   at 
>>> sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:3512)*00:04:28.597*
>>>   at 
>>> sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:3486)*00:04:28.597*
>>>at 
>>> java.io.DataOutputStream.writeInt(DataOutputStream.java:197)*00:04:28.597*  
>>>  at 
>>> hudson.cli.PlainCLIProtocol$EitherSide.send(PlainCLIProtocol.java:175)*00:04:28.597*
>>>  at 
>>> hudson.cli.PlainCLIProtocol$ClientSide.sendEndStdin(PlainCLIProtocol.java:347)*00:04:28.597*
>>>  at hudson.cli.CLI$5.run(CLI.java:679)*00:04:28.597*
>>>
>>> --
>>> Dick Ginga
>>> Build Engineer
>>> rgi...@disruptorbeam.com
>>>
>>>
>>
>>
>> --
>> Dick Ginga
>> Build Engineer
>> rgi...@disruptorbeam.com
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-users/CAL3PpaU2vJiaU65icq6vBNwBs%3D7_%3DvG_a4_
>> tOq_vdVxHbLo4Ug%40mail.gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/CAPO77c2yn_VvCtXNbeA9R27E2yNm8xb2_
> PTn1UEK-0ocoTHvXw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Dick Ginga
Build Engineer
rgi...@disruptorbeam.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAL3PpaUB-PoHSb73KvBQuzW_0VGKNZKCb850KCLm2dB9SZ4msA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: In a shared library, what is the "vars/foo.txt" file USED for?

2017-10-04 Thread red 888
Interesting I check there and didn't see them. Does this mean my txt files 
aren't formatted correctly? I just put a sentence in one to test.

On Monday, October 2, 2017 at 11:25:43 PM UTC-4, Robert Hales wrote:
>
> The .txt file shows up on the PipelineSyntax/Global Variables Reference 
> page. 
>
> On Sunday, February 5, 2017 at 6:33:03 PM UTC-7, David Karr wrote:
>>
>> So I now have a handful of pipeline scripts all reusing some global 
>> methods, all of which I pasted into each script, so I've started to set up 
>> a shared library to avoid duplication.
>>
>> I'm using https://jenkins.io/doc/book/pipeline/shared-libraries/ as my 
>> implementation guide.
>>
>> My questions have to do with the following block:
>>
>> The vars directory hosts scripts that define global variables accessible 
>>> from Pipeline. The basename of each *.groovy file should be a Groovy (~ 
>>> Java) identifier, conventionally camelCased. The matching *.txt, if 
>>> present, can contain documentation, processed through the system’s 
>>> configured markup formatter (so may really be HTML, Markdown, etc., though 
>>> the txt extension is required).
>>
>>
>> The first thing I need to define isn't what you might call a "global 
>> variable", but a method.  I know they are the same thing, but I think this 
>> could be clearer to people who are perhaps less than experts if this 
>> described "global variables or methods".  I'll submit that suggestion in a 
>> PR, but that's not quite what I'm asking about here.
>>
>> I'm wondering about this "matching *.txt" file.  It says it "can contain 
>> documentation, ...".  The problem is, this page says nothing about how that 
>> documentation is used or presented. How is this file actually used?
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/cba485b6-1c2d-4758-9346-b3a8581f2d76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: “Copy artifacts from another project” and Jenkinsfiles are exclusive, correct?

2017-10-04 Thread dandeliondodgeball
So this worked (scripted)


node {
step ([$class: 'CopyArtifact', projectName: 
'Create_Infrastructure_archive']);



This doesn't break, but nothing happens (declarative).  

pipeline {
agent any
stages {
stage('Build') {
steps {
script {
[$class: 'CopyArtifact', projectName: 
'Create_Infrastructure_archive']
}

Any ideas? Thanks.


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e1024ae8-43d2-4419-bee3-fd88502148bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: LDAP and systemctl jenkins restart

2017-10-04 Thread Michael Pailloncy
No, clearly it doesn't sound to be the way it should work :-)
Do you see any error/exception inside Jenkins's logs when you save your
LDAP configuration or during Jenkins startup ?

Cheers

2017-10-03 15:55 GMT+02:00 Joaquin Henriquez <
joaquin.henriq...@countercept.com>:

> Hi ppl
>
>
>
> I configure LDAP and everything is fine, but when I restart Jenkins
> “systemctl restart jenkins” the config for LDAP is removed.
>
>
>
> Is this the way it should work or is there something wrong?
>
>
>
> BR
>
>
>
> Jo
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/745136b239784ed9913b334f55321187%40BSKEXCH2013HYPV.
> mwrinfosecurity.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPO77c05gzcnneFjhofvKi7mpRee%3D%3DzfjQw_p3%3DA0LLmpi7row%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Another CLI question

2017-10-04 Thread Michael Pailloncy
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
, you need
to ensure that it doesn't buffer request/response bodies when serving
Jenkins through HTTPS.

Hopefully it helps.

2017-10-04 19:01 GMT+02:00 Richard Ginga :

> 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, Oct 4, 2017 at 10:08 AM, Richard Ginga 
> wrote:
>
>> 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 https://stt-jenkins.disruptorbeam.com/ -auth rginga:xx 
>> connect-node perf-test-client3
>>
>> *00:04:28.597* Oct 04, 2017 9:52:34 AM hudson.cli.CLI$5 run*00:04:28.597* 
>> WARNING: null*00:04:28.597* java.io.IOException: Stream is 
>> closed*00:04:28.597*at 
>> sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:3512)*00:04:28.597*
>>   at 
>> sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:3486)*00:04:28.597*
>>at 
>> java.io.DataOutputStream.writeInt(DataOutputStream.java:197)*00:04:28.597*   
>> at 
>> hudson.cli.PlainCLIProtocol$EitherSide.send(PlainCLIProtocol.java:175)*00:04:28.597*
>>  at 
>> hudson.cli.PlainCLIProtocol$ClientSide.sendEndStdin(PlainCLIProtocol.java:347)*00:04:28.597*
>>  at hudson.cli.CLI$5.run(CLI.java:679)*00:04:28.597*
>>
>> --
>> Dick Ginga
>> Build Engineer
>> rgi...@disruptorbeam.com
>>
>>
>
>
> --
> Dick Ginga
> Build Engineer
> rgi...@disruptorbeam.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/CAL3PpaU2vJiaU65icq6vBNwBs%
> 3D7_%3DvG_a4_tOq_vdVxHbLo4Ug%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPO77c2yn_VvCtXNbeA9R27E2yNm8xb2_PTn1UEK-0ocoTHvXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: LTS support timelines

2017-10-04 Thread R. Tyler Croy
(replies inline)

On Wed, 04 Oct 2017, lv via Jenkins Users wrote:

> Hi All,
> 
> I'm one of the people maintaining the public Jenkins installation of the 
> Apache Impala (Incubating) project, and since it is facing the public 
> internet we're particularly interested in keeping our installation secure. 
> We are currently running LTS 2.46.3 and I'm trying to figure out whether 
> such old LTS releases are still supported, and for how long.
> 
> I looked at the page describing the LTS Release Line and from there it is 
> not clear to me whether only the latest release line (currently 2.73.X) 
> will receive security fixes, or whether older lines receive those, too. If 
> they do, what is the latest LTS line that will receive security update 
> and/or that is considered when looking at the impact of newly found 
> security issues?


Older LTS releases are in no way supported by the Jenkins project and do not
receive backports of any kind.

I strongly recommend to always follow the latest LTS versions. ci.jenkins.io
(which I maintain) runs 2.73.1 for example, and when we roll new releases, I
make sure to upgrade :)



- R. Tyler Croy

--
 Code: 
  Chatter: 
 xmpp: rty...@jabber.org

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20171004183122.dz54bodh3dqvsdqp%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature


Re: “Copy artifacts from another project” and Jenkinsfiles are exclusive, correct?

2017-10-04 Thread Robert Hales
I don't know of any declarative support, but you can still wrap it in a 
script{} block in declarative. 

On Wednesday, October 4, 2017 at 10:27:01 AM UTC-6, dandeliondodgeball 
wrote:
>
> Helpful, thanks.
>
> So there is only a scripted pipeline solution, no support for declarative, 
> correct?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4b92c0da-fd1e-4457-a664-9781ff32d5a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: No such DSL method 'post' found

2017-10-04 Thread Robert Hales
Sounds like you are trying to use Post in the wrong place - most likely in 
a scripted pipeline. If you were using it correctly, but it wasn't 
available, the error message would say something about an "Undefined 
Section". You can't use "post" in a scripted pipeline. Instead, you have to 
use a try/catch/finally. 



On Wednesday, October 4, 2017 at 11:23:31 AM UTC-6, Indra Gunawan wrote:
>
> Hi,
>
> I would like to archive build images files produced after a successful 
> build step/stage in Jenkins pipeline.
> Is "post", the declarative pipeline syntax, the only way to have 
> post-build defined in Jenkins pipeline.
>
> Somehow it is not available on the Jenkins environment I have:
>
> java.lang.NoSuchMethodError: No such DSL method 'post' found among steps ...
>
>
> May I know the plug-in and version of the plug-in that needs to be installed 
> and running?
>
> Can declarative style and old style coexist in the same pipeline script?
>
>
>
> The Jenkins I am running is :  CloudBees Jenkins Enterprise 2.46.3.2-rolling 
> 
>
>
> Thank you
>
> -Indra
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5b70a6fe-ef30-4857-aa03-18fc493eddff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: GitSCM reference repository - how to verify it is working?

2017-10-04 Thread Mark Waite
If you're willing to experiment, a change was recently merged to the
git-client-plugin which prints a message giving the path to the reference
repo.  You can download the unreleased build from
https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fgit-client-plugin/detail/master/148/artifacts
.
The artifact you need is git-client-plugin.hpi  Upload it to your Jenkins
instance and restart Jenkins, and reference repositories will be noted in
the console log.

Mark Waite

On Wed, Oct 4, 2017 at 11:28 AM Luke Lussenden 
wrote:

> I'm not seeing any clear indication that the reference repository I am
> providing is being utilized.  I don't see the "--reference" argument in any
> of the Git commands that are printed to the console and I am not seeing the
> cache boost I would expect.
>
> I want to use a reference repository because occasionally our checkouts
> are getting throttled to kb/sec speeds and timing out.  From what I can
> see, it still looks like everything is copied from the remote repository.
>
> I have the reference directory withing the workspace as an area to be
> preserved between builds
>
> // cache location
> dir("reference"){
> git: url: ssh://remote.location.com/repo.git, credentialsId: xyz
> }
>
> // build location, wiped clean each build
> dir("build_space"){
> deleteDir()
> checkout([$class: 'GitSCM',
>   branches: [[name: 'MyCurrentBranch']],
>   doGenerateSubmoduleConfigurations: false,
>   extensions: [
>   [$class: 'CloneOption',
> reference: "${WORKSPACE}/reference"
>   ]
>   ],
>   submoduleCfg: [],
>   userRemoteConfigs: [[ credentialsId: 'xyz', url: 'ssh://
> remote.location.com/repo.git' ]]
> ])
> }
>
> The only indication at all that what I'm passing in as a reference is
> being used is if I point the reference to an existing directory that does
> not contain a git repo - then I will get a warning in the console output.
>
> Any input - including alternate strategies for caching - would be
> appreciated.
>
> Thanks!
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/c488b9a8-7a9e-4575-b139-4f5f7ba894dd%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFkaL8HQVh1FWecygsHBXSQFYNkdzoMCUL%3DR0G%2BTRdeoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


GitSCM reference repository - how to verify it is working?

2017-10-04 Thread Luke Lussenden
I'm not seeing any clear indication that the reference repository I am 
providing is being utilized.  I don't see the "--reference" argument in any 
of the Git commands that are printed to the console and I am not seeing the 
cache boost I would expect. 

I want to use a reference repository because occasionally our checkouts are 
getting throttled to kb/sec speeds and timing out.  From what I can see, it 
still looks like everything is copied from the remote repository.

I have the reference directory withing the workspace as an area to be 
preserved between builds

// cache location
dir("reference"){
git: url: ssh://remote.location.com/repo.git, credentialsId: xyz
}

// build location, wiped clean each build
dir("build_space"){
deleteDir()
checkout([$class: 'GitSCM',
  branches: [[name: 'MyCurrentBranch']],
  doGenerateSubmoduleConfigurations: false,
  extensions: [
  [$class: 'CloneOption',
reference: "${WORKSPACE}/reference"
  ]
  ],
  submoduleCfg: [],
  userRemoteConfigs: [[ credentialsId: 'xyz', url: 'ssh:
//remote.location.com/repo.git' ]]
])
}

The only indication at all that what I'm passing in as a reference is being 
used is if I point the reference to an existing directory that does not 
contain a git repo - then I will get a warning in the console output.  

Any input - including alternate strategies for caching - would be 
appreciated.

Thanks!


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c488b9a8-7a9e-4575-b139-4f5f7ba894dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


LTS support timelines

2017-10-04 Thread lv via Jenkins Users
Hi All,

I'm one of the people maintaining the public Jenkins installation of the 
Apache Impala (Incubating) project, and since it is facing the public 
internet we're particularly interested in keeping our installation secure. 
We are currently running LTS 2.46.3 and I'm trying to figure out whether 
such old LTS releases are still supported, and for how long.

I looked at the page describing the LTS Release Line and from there it is 
not clear to me whether only the latest release line (currently 2.73.X) 
will receive security fixes, or whether older lines receive those, too. If 
they do, what is the latest LTS line that will receive security update 
and/or that is considered when looking at the impact of newly found 
security issues?

Thanks for the help. Lars

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/aa487ae7-9d74-4f58-84c0-bd544227d678%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


No such DSL method 'post' found

2017-10-04 Thread Indra Gunawan
Hi,

I would like to archive build images files produced after a successful 
build step/stage in Jenkins pipeline.
Is "post", the declarative pipeline syntax, the only way to have post-build 
defined in Jenkins pipeline.

Somehow it is not available on the Jenkins environment I have:

java.lang.NoSuchMethodError: No such DSL method 'post' found among steps ...


May I know the plug-in and version of the plug-in that needs to be installed 
and running?

Can declarative style and old style coexist in the same pipeline script?



The Jenkins I am running is :  CloudBees Jenkins Enterprise 2.46.3.2-rolling 



Thank you

-Indra

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ddab8d54-1613-4842-9885-30914eefb558%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Another CLI question

2017-10-04 Thread Richard Ginga
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, Oct 4, 2017 at 10:08 AM, Richard Ginga 
wrote:

> 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 https://stt-jenkins.disruptorbeam.com/ -auth rginga:xx 
> connect-node perf-test-client3
>
> *00:04:28.597* Oct 04, 2017 9:52:34 AM hudson.cli.CLI$5 run*00:04:28.597* 
> WARNING: null*00:04:28.597* java.io.IOException: Stream is 
> closed*00:04:28.597* at 
> sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:3512)*00:04:28.597*
>   at 
> sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:3486)*00:04:28.597*
>at 
> java.io.DataOutputStream.writeInt(DataOutputStream.java:197)*00:04:28.597*   
> at 
> hudson.cli.PlainCLIProtocol$EitherSide.send(PlainCLIProtocol.java:175)*00:04:28.597*
>  at 
> hudson.cli.PlainCLIProtocol$ClientSide.sendEndStdin(PlainCLIProtocol.java:347)*00:04:28.597*
>  at hudson.cli.CLI$5.run(CLI.java:679)*00:04:28.597*
>
> --
> Dick Ginga
> Build Engineer
> rgi...@disruptorbeam.com
>
>


-- 
Dick Ginga
Build Engineer
rgi...@disruptorbeam.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAL3PpaU2vJiaU65icq6vBNwBs%3D7_%3DvG_a4_tOq_vdVxHbLo4Ug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: “Copy artifacts from another project” and Jenkinsfiles are exclusive, correct?

2017-10-04 Thread dandeliondodgeball
Helpful, thanks.

So there is only a scripted pipeline solution, no support for declarative, 
correct?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a27c203a-403b-444a-b493-314020553ff9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Pre-approval of Groovy script files

2017-10-04 Thread Clément
Hi every one !

I'm preparing the migration of my Jenkins project on the Jenkins2 version 
and it seems like groovy scripts are not managed the same way.

I have numerous jobs which use groovy scripts.
Some of them are very small, and "inlined" in job config.
For those scripts, current approval system is OK.

Some of them are a bit longer, and are managed in a git repository.
For those scripts, current approval system use "white box" method.

That's not very good for me, because these scripts go deep into Jenkins API.

It seems that the newer version of Jenkins is safer, but make things a bit 
difficult.
(i don't want to relaunch the same job XXX times to approve each method 
called)

I would like to find a plugin or a method that would allow me to approve a 
script file or 
manage a list of groovy scripts that could then be used by my jobs without 
further approval.

If you're familiar with what I'm talking about, thanks to let me know.

Regards.

Clément.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/459a807b-360c-4629-8813-3cd2a5a8c655%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins CLI with http protocol does not respond in 2.81

2017-10-04 Thread Riccardo Foschia


Am 04.10.2017 um 15:51 schrieb Devin Nusbaum:

Do you see any errors in the logs on the Jenkins server, and is the 
jenkins-cli.jar you are using from your 2.81 instance? You can download a fresh 
jar from http://YOUR_HOST/jenkins/jnlpJars/jenkins-cli.jar. (If you aren’t 
using the /jenkins context path just http://YOUR_HOST/jnlpJars/jenkins-cli.jar).



The jenkins-cli.jar is the one from the 2.81 server instance. I 
downloaded it from the link you mentioned. The MANIFEST.MF of this jar 
says, it's Jenkins-CLI 2.81.


And I do not see exceptions in /var/lib/jenkins/jenkins.log around the 
times I launch the CLI commands.





On Oct 4, 2017, at 7:50 AM, Riccardo Foschia  
wrote:

Hi all,

after an upgrade of Jenkins 1.638 to 2.81 CLI I need to switch to http protocol 
but it doesn't work (SSH protocol seems to work after the upgrade).

No matter which CLI command I use, after a few seconds the call returns but 
shows no result. E.g.

java -jar jenkins-cli.jar -s http://10.0.3.108 -logger FINE help

called from a Windows command line returns nothing. No errors are reported. On 
console I see only the following output:

Okt 04, 2017 1:11:33 PM hudson.cli.CLI _main
FINE: using connection mode HTTP
Okt 04, 2017 1:11:33 PM hudson.cli.CLI plainHttpConnection
FINE: Trying to connect to http://10.0.3.108:8080/ via plain protocol over HTTP
Okt 04, 2017 1:11:34 PM hudson.cli.FullDuplexHttpStream 
FINE: establishing download side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: established download side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: establishing upload side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: established upload side


On Jenkins server (running on Debian) I enabled HTTP access log and I see the 
following lines there:

10.0.1.66 - - [04/Okt/2017:13:41:50 +0200] "GET / HTTP/1.1" 200 295675 "-" 
"Java/1.8.0_141"
10.0.1.66 - - [04/Okt/2017:13:41:58 +0200] "POST /cli HTTP/1.1" 200 6458 "-" 
"Java/1.8.0_141"
10.0.1.66 - - [04/Okt/2017:13:41:58 +0200] "POST /cli HTTP/1.1" 200 0 "-" 
"Java/1.8.0_141"

I also tried this with other CLI commands like version or who-am-i and 
providing an additional -auth parameter with the right API-Token to the command 
line like

java -jar jenkins-cli.jar -s http://10.0.3.108 -auth foschia:
02a781f2a2fe96e8d38dc548ab07912e -logger FINE version

but the result on the command line and the log outputs on client and server 
side remain the same.

After reading all available Jenkins documentation and googling around I really 
do not know, what to do next.

I would really appreciate any hints.

Thanks in advance,
Riccardo

--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/47734b97-86aa-3555-e7b0-4fac1cbd26c7%40meta-level.de.
For more options, visit https://groups.google.com/d/optout.




--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8589e9fd-ca8d-7bdb-aebf-bc11c8bf08c7%40meta-level.de.
For more options, visit https://groups.google.com/d/optout.


Another CLI question

2017-10-04 Thread Richard Ginga
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 https://stt-jenkins.disruptorbeam.com/ -auth
rginga:xx connect-node perf-test-client3

*00:04:28.597* Oct 04, 2017 9:52:34 AM hudson.cli.CLI$5
run*00:04:28.597* WARNING: null*00:04:28.597* java.io.IOException:
Stream is closed*00:04:28.597*  at
sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:3512)*00:04:28.597*
at 
sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:3486)*00:04:28.597*
at 
java.io.DataOutputStream.writeInt(DataOutputStream.java:197)*00:04:28.597*
at 
hudson.cli.PlainCLIProtocol$EitherSide.send(PlainCLIProtocol.java:175)*00:04:28.597*
at 
hudson.cli.PlainCLIProtocol$ClientSide.sendEndStdin(PlainCLIProtocol.java:347)*00:04:28.597*
at hudson.cli.CLI$5.run(CLI.java:679)*00:04:28.597*

-- 
Dick Ginga
Build Engineer
rgi...@disruptorbeam.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAL3PpaVWfOu_RUHUdPr3N%2Bvj8eQ6b-B-W7F418gR0w9ADupUnw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins CLI with http protocol does not respond in 2.81

2017-10-04 Thread Devin Nusbaum
Do you see any errors in the logs on the Jenkins server, and is the 
jenkins-cli.jar you are using from your 2.81 instance? You can download a fresh 
jar from http://YOUR_HOST/jenkins/jnlpJars/jenkins-cli.jar. (If you aren’t 
using the /jenkins context path just http://YOUR_HOST/jnlpJars/jenkins-cli.jar).

> On Oct 4, 2017, at 7:50 AM, Riccardo Foschia  
> wrote:
> 
> Hi all,
> 
> after an upgrade of Jenkins 1.638 to 2.81 CLI I need to switch to http 
> protocol but it doesn't work (SSH protocol seems to work after the upgrade).
> 
> No matter which CLI command I use, after a few seconds the call returns but 
> shows no result. E.g.
> 
> java -jar jenkins-cli.jar -s http://10.0.3.108 -logger FINE help
> 
> called from a Windows command line returns nothing. No errors are reported. 
> On console I see only the following output:
> 
> Okt 04, 2017 1:11:33 PM hudson.cli.CLI _main
> FINE: using connection mode HTTP
> Okt 04, 2017 1:11:33 PM hudson.cli.CLI plainHttpConnection
> FINE: Trying to connect to http://10.0.3.108:8080/ via plain protocol over 
> HTTP
> Okt 04, 2017 1:11:34 PM hudson.cli.FullDuplexHttpStream 
> FINE: establishing download side
> Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
> FINE: established download side
> Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
> FINE: establishing upload side
> Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
> FINE: established upload side
> 
> 
> On Jenkins server (running on Debian) I enabled HTTP access log and I see the 
> following lines there:
> 
> 10.0.1.66 - - [04/Okt/2017:13:41:50 +0200] "GET / HTTP/1.1" 200 295675 "-" 
> "Java/1.8.0_141"
> 10.0.1.66 - - [04/Okt/2017:13:41:58 +0200] "POST /cli HTTP/1.1" 200 6458 "-" 
> "Java/1.8.0_141"
> 10.0.1.66 - - [04/Okt/2017:13:41:58 +0200] "POST /cli HTTP/1.1" 200 0 "-" 
> "Java/1.8.0_141"
> 
> I also tried this with other CLI commands like version or who-am-i and 
> providing an additional -auth parameter with the right API-Token to the 
> command line like
> 
> java -jar jenkins-cli.jar -s http://10.0.3.108 -auth foschia:
> 02a781f2a2fe96e8d38dc548ab07912e -logger FINE version
> 
> but the result on the command line and the log outputs on client and server 
> side remain the same.
> 
> After reading all available Jenkins documentation and googling around I 
> really do not know, what to do next.
> 
> I would really appreciate any hints.
> 
> Thanks in advance,
> Riccardo
> 
> -- 
> 
> META-LEVEL Software AG
> Lyonerring 1
> 66121 Saarbrücken
> Deutschland
> Tel: +49 - 681 / 99687-0
> Fax: +49 - 681 / 99687-99
> Mail: i...@meta-level.de
> Web: www.meta-level.de
> 
> Rechtsform: Aktiengesellschaft
> Sitz: Saarbrücken
> HR B Nr. 13 380 Amtsgericht Saarbrücken
> USt-IdNr. DE 1 38 17
> Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
> Vorsitzender des Aufsichtsrats:  Reinhard Kuhn
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/47734b97-86aa-3555-e7b0-4fac1cbd26c7%40meta-level.de.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/E3325FB9-7F79-4FD8-B92D-1C302A89F9D4%40cloudbees.com.
For more options, visit https://groups.google.com/d/optout.


RE: Trouble running JNLP slave as a service in Windows 10

2017-10-04 Thread David Aldrich
> Does that not show the "Install as a Service" menu item?

No. The command windows shows the agent is connected but there is no pop-up 
with an "Install as a Service" menu item.

BR

David

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide
Sent: 04 October 2017 14:12
To: jenkinsci-users@googlegroups.com
Subject: Re: Trouble running JNLP slave as a service in Windows 10

That page is for DCOM agents, not JNLP agents.

The easiest method to do this is to open an administrator console and then run 
the command you specified in your original email:

java -jar slave.jar -jnlpUrl 
http:///computer//slave-agent.jnlp
 -secret 

Does that not show the "Install as a Service" menu item?

On Wed, Oct 4, 2017 at 5:02 AM Khomyuk Viktor 
> wrote:

Hi. Install slave as service is not easy :)

Look at the 
https://wiki.jenkins.io/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM​

Start with "Enable Remote Registry Access".

One error will be replaced by another, but after some time you will achieve 
your goal.


От: jenkinsci-users@googlegroups.com 
> от 
имени David Aldrich 
>
Отправлено: 4 октября 2017 г. 17:42
Кому: jenkinsci-users@googlegroups.com
Тема: Trouble running JNLP slave as a service in Windows 10

Hi

I want to install a JNLP slave as a service in Windows 10.

If I use the ‘easy’ method of going to the node page, from the slave machine, 
and clicking on the Launch button, the slave launches. But if I select ‘File > 
Install as a service’ I get an exception:

[cid:image001.png@01D33D05.743EF450]

I wonder if this is because I haven’t done it properly in administrator mode. 
But I did open an admin command prompt and ran my browser (Edge) from there.

Alternatively, I can start the slave from a command line using:

java -jar slave.jar -jnlpUrl 
http:///computer//slave-agent.jnlp
 -secret  described at computer//

but that doesn’t allow me to run the agent as a service.

Please can anyone help me with this?

Best regards

David

--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/37b7943ef2a74239b0e23ad16cb70cde%40EUX13SRV1.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1507115712914.83840%402Gis.ru.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVc0yytZF%2B%2BC68PKMhp1maOiKr-3Tgts2xrp2vumJHZHoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Click 
here
 to report this email as spam.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/16e2b265342d4771bd9565a4ac63f668%40EUX13SRV1.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.


Re: Trouble running JNLP slave as a service in Windows 10

2017-10-04 Thread Slide
That page is for DCOM agents, not JNLP agents.

The easiest method to do this is to open an administrator console and then
run the command you specified in your original email:

java -jar slave.jar -jnlpUrl
http:///computer//slave-agent.jnlp
-secret 

Does that not show the "Install as a Service" menu item?

On Wed, Oct 4, 2017 at 5:02 AM Khomyuk Viktor  wrote:

> Hi. Install slave as service is not easy :)
>
> Look at the
> https://wiki.jenkins.io/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM
> ​
>
> Start with "Enable Remote Registry Access".
>
> One error will be replaced by another, but after some time you will
> achieve your goal.
> --
> *От:* jenkinsci-users@googlegroups.com 
> от имени David Aldrich 
> *Отправлено:* 4 октября 2017 г. 17:42
> *Кому:* jenkinsci-users@googlegroups.com
> *Тема:* Trouble running JNLP slave as a service in Windows 10
>
>
> Hi
>
>
>
> I want to install a JNLP slave as a service in Windows 10.
>
>
>
> If I use the ‘easy’ method of going to the node page, from the slave
> machine, and clicking on the Launch button, the slave launches. But if I
> select ‘File > Install as a service’ I get an exception:
>
>
>
>
>
> I wonder if this is because I haven’t done it properly in administrator
> mode. But I did open an admin command prompt and ran my browser (Edge) from
> there.
>
>
>
> Alternatively, I can start the slave from a command line using:
>
>
>
> java -jar slave.jar -jnlpUrl 
> http:///computer//slave-agent.jnlp
> -secret  described at computer//
>
>
>
> but that doesn’t allow me to run the agent as a service.
>
>
>
> Please can anyone help me with this?
>
>
>
> Best regards
>
>
>
> David
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/37b7943ef2a74239b0e23ad16cb70cde%40EUX13SRV1.EU.NEC.COM
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1507115712914.83840%402Gis.ru
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVc0yytZF%2B%2BC68PKMhp1maOiKr-3Tgts2xrp2vumJHZHoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins CLI with http protocol does not respond in 2.81

2017-10-04 Thread Riccardo Foschia



Am 04.10.2017 um 14:53 schrieb Daniel Beck:



On 4. Oct 2017, at 14:29, Riccardo Foschia  
wrote:

Thanks for your answer, but there is no proxy running.


What security realm are you using?



We are using LDAP and project based matrix authorization (like before 
upgrading).


In the old Jenkins version we used before upgrading to 2.81 we needed to 
authorize user anonymous with common read and connect permissions. These 
user still exists after upgrading to 2.81, see attached screen shot.


--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/eccad6a1-fcd0-10b6-dae3-674dfa03ea46%40meta-level.de.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins CLI with http protocol does not respond in 2.81

2017-10-04 Thread Daniel Beck

> On 4. Oct 2017, at 14:29, Riccardo Foschia  
> wrote:
> 
> Thanks for your answer, but there is no proxy running.

What security realm are you using?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/571B5B4F-3D19-4166-8E1E-CAEF815B18CC%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins CLI with http protocol does not respond in 2.81

2017-10-04 Thread Riccardo Foschia


Am 04.10.2017 um 14:00 schrieb Daniel Beck:



On 4. Oct 2017, at 13:50, Riccardo Foschia  
wrote:

after an upgrade of Jenkins 1.638 to 2.81 CLI I need to switch to http protocol 
but it doesn't work (SSH protocol seems to work after the upgrade).

No matter which CLI command I use, after a few seconds the call returns but 
shows no result. E.g.



If Jenkins is running behind a reverse proxy, make sure the settings are 
correct.

For example for nginx,

proxy_http_version 1.1;
proxy_request_buffering off;



Thanks for your answer, but there is no proxy running.


--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/73022ea1-67f2-4979-852b-ff318b9a29b6%40meta-level.de.
For more options, visit https://groups.google.com/d/optout.


Re: Trouble running JNLP slave as a service in Windows 10

2017-10-04 Thread Khomyuk Viktor
Hi. Install slave as service is not easy :)

Look at the 
https://wiki.jenkins.io/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM?

Start with "Enable Remote Registry Access".

One error will be replaced by another, but after some time you will achieve 
your goal.


От: jenkinsci-users@googlegroups.com  от 
имени David Aldrich 
Отправлено: 4 октября 2017 г. 17:42
Кому: jenkinsci-users@googlegroups.com
Тема: Trouble running JNLP slave as a service in Windows 10

Hi

I want to install a JNLP slave as a service in Windows 10.

If I use the 'easy' method of going to the node page, from the slave machine, 
and clicking on the Launch button, the slave launches. But if I select 'File > 
Install as a service' I get an exception:

[cid:image001.png@01D33D05.743EF450]

I wonder if this is because I haven't done it properly in administrator mode. 
But I did open an admin command prompt and ran my browser (Edge) from there.

Alternatively, I can start the slave from a command line using:

java -jar slave.jar -jnlpUrl 
http:///computer//slave-agent.jnlp -secret  
described at computer//

but that doesn't allow me to run the agent as a service.

Please can anyone help me with this?

Best regards

David


--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/37b7943ef2a74239b0e23ad16cb70cde%40EUX13SRV1.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1507115712914.83840%402Gis.ru.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins CLI with http protocol does not respond in 2.81

2017-10-04 Thread Daniel Beck

> On 4. Oct 2017, at 13:50, Riccardo Foschia  
> wrote:
> 
> after an upgrade of Jenkins 1.638 to 2.81 CLI I need to switch to http 
> protocol but it doesn't work (SSH protocol seems to work after the upgrade).
> 
> No matter which CLI command I use, after a few seconds the call returns but 
> shows no result. E.g.
> 

If Jenkins is running behind a reverse proxy, make sure the settings are 
correct.

For example for nginx,

proxy_http_version 1.1;
proxy_request_buffering off;

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/B66E38CE-AE32-4D37-AB2F-9F765C7D8485%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


Jenkins CLI with http protocol does not respond in 2.81

2017-10-04 Thread Riccardo Foschia

Hi all,

after an upgrade of Jenkins 1.638 to 2.81 CLI I need to switch to http 
protocol but it doesn't work (SSH protocol seems to work after the 
upgrade).


No matter which CLI command I use, after a few seconds the call returns 
but shows no result. E.g.


java -jar jenkins-cli.jar -s http://10.0.3.108 -logger FINE help

called from a Windows command line returns nothing. No errors are 
reported. On console I see only the following output:


Okt 04, 2017 1:11:33 PM hudson.cli.CLI _main
FINE: using connection mode HTTP
Okt 04, 2017 1:11:33 PM hudson.cli.CLI plainHttpConnection
FINE: Trying to connect to http://10.0.3.108:8080/ via plain protocol 
over HTTP

Okt 04, 2017 1:11:34 PM hudson.cli.FullDuplexHttpStream 
FINE: establishing download side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: established download side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: establishing upload side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: established upload side


On Jenkins server (running on Debian) I enabled HTTP access log and I 
see the following lines there:


10.0.1.66 - - [04/Okt/2017:13:41:50 +0200] "GET / HTTP/1.1" 200 295675 
"-" "Java/1.8.0_141"
10.0.1.66 - - [04/Okt/2017:13:41:58 +0200] "POST /cli HTTP/1.1" 200 6458 
"-" "Java/1.8.0_141"
10.0.1.66 - - [04/Okt/2017:13:41:58 +0200] "POST /cli HTTP/1.1" 200 0 
"-" "Java/1.8.0_141"


I also tried this with other CLI commands like version or who-am-i and 
providing an additional -auth parameter with the right API-Token to the 
command line like


java -jar jenkins-cli.jar -s http://10.0.3.108 -auth foschia:
02a781f2a2fe96e8d38dc548ab07912e -logger FINE version

but the result on the command line and the log outputs on client and 
server side remain the same.


After reading all available Jenkins documentation and googling around I 
really do not know, what to do next.


I would really appreciate any hints.

Thanks in advance,
Riccardo

--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/47734b97-86aa-3555-e7b0-4fac1cbd26c7%40meta-level.de.
For more options, visit https://groups.google.com/d/optout.


Re: Pipeline Maven: Running on Windows slave

2017-10-04 Thread Sverre Moe
Here follows an update of some observations and configurations I have done 
to get building on Windows to work.

The Windows node is connected in Jenkins with SSH started by sshd in Cygwin.
Using this 
guide: 
https://www.howtogeek.com/howto/41560/how-to-get-ssh-command-line-access-to-windows-7-using-cygwin/

The Windows node's "Remote root directory" is set to 
"C:\cygwin64\home\build", because "/home/build" would not work.
Step withMaven woulld fail with use of the latter:

[myApp_sverre_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ] 
Running shell script
sh: 
/home/build/workspace/myApp_sverre_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ@tmp/durable-e1932da9/pid:
 No such file or directory
sh: 
/home/build/workspace/myApp_sverre_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ@tmp/durable-e1932da9/jenkins-log.txt:
 No such file or directory
sh: 
/home/build/workspace/myApp_sverre_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ@tmp/durable-e1932da9/jenkins-result.txt:
 No such file or directory


I have also added an additional Windows JDK in Jenkins pointing to 
C:\Program Files\Java\jdk1.8.0_144.
Creating a symlink in cygwin at /usr/java/jdk1.8.0_144 to 
/cygdrive/c/Program\ Files/jdk1.8.0_144 allowed me to use the same Jenkins 
JDK tool for both Windows and Linux (though only with the sh step).

For the time being I have been using the pipeline step bat after checking 
!isUnix().
However with the bat step I must use a different JDK that points to the 
real directory in Windows C:\Program Files\Java\jdk1.8.0_144.
Otherwise withMaven fails to find the JDK at /usr/java/jdk1.8.0_144

[myApp_sverre_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ] 
Running batch script

C:\cygwin64\home\build\workspace\myApp_sverre_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ>mvn
 clean install  
- withMaven Wrapper script -
The JAVA_HOME environment variable is not defined correctly 
This environment variable is needed to run this program 
NB: JAVA_HOME should point to a JDK not a JRE 



Using the sh step instead of the bat step in pipeline kinda works. However 
with one Exception.

[withMaven] use Maven installation provided by the build agent with executable 
C:\Program Files\apache-maven-3.5.0\bin\mvn.cmd
[Pipeline] {

[Pipeline] sh
[C:\cygwin64\home\build\workspace\myApp_sverre_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ]
 Running shell script
Cannot contact master-windows7-x86_64: java.io.IOException: Remote call on 
master-windows7-x86_64 failed

+ mvn clean install

The build continues never the less with success, so I am not sure what 
failed here and what it tried to do on the remote node that caused the 
IOException.


tirsdag 12. september 2017 10.51.46 UTC+2 skrev Cyrille Le Clerc følgende:
>
> Hello Svere,
>
> It seems that we have some work to make withMaven(){} more friendly to 
> Windows+Cygwin users.
>
> We have already tracked:
>
>- JENKINS-44089 Request that withMaven pipeline step produce both mvn 
>and mvn.cmd wrappers on Windows 
>
>- JENKINS-44276 Maven fails in pipeline + cygwin 
>
>
> Some refactoring of the code will be needed to generate both standard 
> Windows and Cygwin friendly scripts on Windows agents.
>
> Please feel free to give us hints on what a smooth integration with 
> Windows and Cygwin should look like.
>
> Cyrille
>
> On Monday, September 11, 2017 at 9:08:53 AM UTC+2, Baptiste Mathus wrote:
>>
>> Hello,
>> I know the developers of that plugin would like to make it as good as 
>> possible. To that, if so, could you please try and summarize what you think 
>> could be made easier/better? And even if possibly a config error, if you 
>> think the error could help more quickly understand what is wrong?
>>
>> Thanks!
>>
>> Le 11 sept. 2017 09:03, "Sverre Moe"  a écrit :
>>
>>> The fix was to set the Windows slave Remote Root Directory to Windows URI
>>> C:\cygwin64\home\username
>>>
>>> mandag 11. september 2017 08.35.29 UTC+2 skrev Sverre Moe følgende:

 Well, adding a new JDK in Jenkins Tools pointing to the Windows path of 
 Java worked
 Then withMaven(jdk: "jdk1.8-win")

 I have though hit another snag. Lots of ERROR after build success.
 ERROR: [withMaven] WARNING: Exception archiving and fingerprinting 
 MavenArtifact{no.spacetec:myApp:jar:1.0.0-SNAPSHOT 
 C:\home\username\workspace\myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ\target\myApp-1.0.0-SNAPSHOT.jar},
  
 skip archiving of the artifacts

 ERROR: [withMaven] WARNING: Exception archiving and fingerprinting 
 MavenArtifact{no.spacetec:myApp:rpm:1.0.0-SNAPSHOT 
 

Trouble running JNLP slave as a service in Windows 10

2017-10-04 Thread David Aldrich
Hi

I want to install a JNLP slave as a service in Windows 10.

If I use the 'easy' method of going to the node page, from the slave machine, 
and clicking on the Launch button, the slave launches. But if I select 'File > 
Install as a service' I get an exception:

[cid:image001.png@01D33D05.743EF450]

I wonder if this is because I haven't done it properly in administrator mode. 
But I did open an admin command prompt and ran my browser (Edge) from there.

Alternatively, I can start the slave from a command line using:

java -jar slave.jar -jnlpUrl 
http:///computer//slave-agent.jnlp -secret  
described at computer//

but that doesn't allow me to run the agent as a service.

Please can anyone help me with this?

Best regards

David

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/37b7943ef2a74239b0e23ad16cb70cde%40EUX13SRV1.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.


Re: Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked.

2017-10-04 Thread YAN-HONG WANG
Hi Carlos,

Thanks for your valuable hint.
That's worked on Ubuntu 16.04 environment since I added RBAC roles setup.

Something interesting is that before I always run in Minikube environment 
without RBAC role, that still can run.

Thanks anyway.

Hong

Am Dienstag, 3. Oktober 2017 12:15:11 UTC+2 schrieb Carlos Sanchez:
>
> That means you don't have the right RBAC roles setup for the default SA in 
> kubernetes. By default you get no permissions
>
> On Mon, Oct 2, 2017 at 3:38 PM, WANG, YAN-HONG  > wrote:
>
>> Hi
>>
>> I meet a error message while I tried "*Test Connection*"
>>
>> *Error connecting to https://kubernetes.default.svc.cluster.local 
>> : Failure executing: GET at: 
>> https://kubernetes.default.svc.cluster.local/api/v1/namespaces/build-env/pods
>>  
>> .
>>  
>> Message: Forbidden!Configured service account doesn't have access. Service 
>> account may have been revoked. User 
>> "system:serviceaccount:build-env:default" cannot list pods in the namespace 
>> "build-env"...*
>>
>> My environment:
>> Platform: Ubuntu 16.04
>> Jenkins: 2.73.1
>> Jenkins plugin (kubernetes:1.0).
>> Kuberntes Server: v1.7.7
>>
>> There are some similar issue could also be found here. 
>> https://issues.jenkins-ci.org/browse/JENKINS-41388
>> https://groups.google.com/forum/#!topic/fabric8/H-UGSFJLC6g
>>
>> Is there anyone know about this issue?
>>
>> Thanks very much.
>>
>> Hong
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/CADLWyO0a2uWcc%3DRZ-u4LfTv5CZ3uG7jam7oQJdb%2BR46MJsUfLQ%40mail.gmail.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2532476a-45ce-466a-8949-a93e7d20e4e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Mixing declarative and scripted pipeline syntax in one Jenkinsfile ...

2017-10-04 Thread Daniel Beck

> On 4. Oct 2017, at 09:00, Eric Tan  wrote:
> 
> Is it possible to mix declarative and scripted pipeline syntax in one 
> Jenkinsfile ?
> 

https://jenkins.io/doc/book/pipeline/syntax/#script

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/776FBCCA-8727-44BA-BB66-5AC758A7EA1C%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


Mixing declarative and scripted pipeline syntax in one Jenkinsfile ...

2017-10-04 Thread Eric Tan
Hi,

Is it possible to mix declarative and scripted pipeline syntax in one 
Jenkinsfile ?

For example, there is no withRun() equivalent in the declarative syntax.

https://issues.jenkins-ci.org/browse/JENKINS-41581

Thanks,
Eric

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2a9d164f-f697-4e00-b43a-6e1214b17b46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.