Re: Kubernetes Plugin 1.2 Agents unable to establish connection to master, but log they can

[brandon]

-- 
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/d5e1e22c-1119-4198-aaa4-21a683dec3b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Kubernetes Plugin 1.2 Agents unable to establish connection to master, but log they can

[brandon]

On Monday, February 19, 2018 at 9:02:22 PM UTC-8, Brandon wrote:
>
> Hello, I am trying to use the community helm chart for Jenkins and the 
> Kubernetes plugin 1.2 so that agents can be dynamically provisioned 
> according to build needs.
>
> Ultimately, builds are failing because the  agents are not able to connect 
> to the master. However, I am seeing that in both the agents and master log 
> that they believe they have established a connection. What is going on? How 
> can I debug this further.
>
> This is using the default agent container and doing service discovery for 
> a Jenkins URL and tunnel according to the services in the jenkins namespace.
>
> k get svc -n jenkins
> NAMETYPECLUSTER-IP  EXTERNAL-IP   
> PORT(S)  AGE
> jenkins-jenkins NodePort10.233.45.129   
> 8080:32080/TCP   7d
> jenkins-jenkins-agent   ClusterIP   10.233.11.112   
> 5/TCP7d
>
>
> #master log
> INFO: Created Pod: default-37fj9 in namespace jenkins
> Feb 12, 2018 11:16:32 PM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
> INFO: Waiting for Pod to be scheduled (0/100): default-37fj9
> Feb 12, 2018 11:16:38 PM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
> INFO: Waiting for agent to connect (0/100): default-37fj9
> Feb 12, 2018 11:16:39 PM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
> INFO: Waiting for agent to connect (1/100): default-37fj9
> Feb 12, 2018 11:16:40 PM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
> INFO: Waiting for agent to connect (2/100): default-37fj9
> Feb 12, 2018 11:16:41 PM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
> INFO: Waiting for agent to connect (3/100): default-37fj9
> Feb 12, 2018 11:16:42 PM hudson.TcpSlaveAgentListener$ConnectionHandler run
> *INFO: Accepted JNLP4-connect connection #3 from /10.233.108.132:38682 
> *
> Feb 12, 2018 11:16:42 PM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
> INFO: Waiting for agent to connect (4/100): default-37fj9
> Feb 12, 2018 11:16:43 PM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
> INFO: Waiting for agent to connect (5/100): default-37fj9
> Feb 12, 2018 11:16:44 PM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
> INFO: Waiting for agent to connect (6/100): default-37fj9
>
>
>
> #agent logs
> INFO: Locating server among [
> http://jenkins-jenkins.jenkins.svc.cluster.local:8080/]
> Feb 12, 2018 11:16:41 PM 
> org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
> INFO: Remoting server accepts the following protocols: [JNLP4-connect, 
> JNLP-connect, Ping, JNLP2-connect]
> Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status
> INFO: Agent discovery successful
>   Agent address: jenkins-jenkins-agent.jenkins.svc.cluster.local
>   Agent port:5
>   Identity:  5d:e6:82:6c:06:4a:ef:96:ae:47:09:b2:cc:58:e8:0a
> Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status
> INFO: Handshaking
> Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status
> INFO: Connecting to jenkins-jenkins-agent.jenkins.svc.cluster.local:5
> Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status
> INFO: Trying protocol: JNLP4-connect
> Feb 12, 2018 11:16:43 PM hudson.remoting.jnlp.Main$CuiListener status
> INFO: Remote identity confirmed: 
> 5d:e6:82:6c:06:4a:ef:96:ae:47:09:b2:cc:58:e8:0a
> Feb 12, 2018 11:16:55 PM hudson.remoting.jnlp.Main$CuiListener status
> * INFO: Connected*
>
> -- 
> Brandon Pinske
> Site Reliability Engineer
> Rabb.it
>
>

-- 
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/e88fad60-b5f2-4f83-82c2-5e0900743839%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Kubernetes Plugin 1.2 Agents unable to establish connection to master, but log they can

[Brandon]

Hello, I am trying to use the community helm chart for Jenkins and the
Kubernetes plugin 1.2 so that agents can be dynamically provisioned
according to build needs.

Ultimately, builds are failing because the  agents are not able to
connect to the master. However, I am seeing that in both the agents and
master log that they believe they have established a connection. What is
going on? How can I debug this further.

This is using the default agent container and doing service discovery
for a Jenkins URL and tunnel according to the services in the jenkins
namespace.

k get svc -n jenkins
NAME    TYPE    CLUSTER-IP  EXTERNAL-IP  
PORT(S)  AGE
jenkins-jenkins NodePort    10.233.45.129      
8080:32080/TCP   7d
jenkins-jenkins-agent   ClusterIP   10.233.11.112      
5/TCP    7d


#master log
INFO: Created Pod: default-37fj9 in namespace jenkins
Feb 12, 2018 11:16:32 PM
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (0/100): default-37fj9
Feb 12, 2018 11:16:38 PM
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (0/100): default-37fj9
Feb 12, 2018 11:16:39 PM
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (1/100): default-37fj9
Feb 12, 2018 11:16:40 PM
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (2/100): default-37fj9
Feb 12, 2018 11:16:41 PM
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (3/100): default-37fj9
Feb 12, 2018 11:16:42 PM hudson.TcpSlaveAgentListener$ConnectionHandler run
*INFO: Accepted JNLP4-connect connection #3 from /10.233.108.132:38682
*
Feb 12, 2018 11:16:42 PM
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (4/100): default-37fj9
Feb 12, 2018 11:16:43 PM
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (5/100): default-37fj9
Feb 12, 2018 11:16:44 PM
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (6/100): default-37fj9



#agent logs
INFO: Locating server among
[http://jenkins-jenkins.jenkins.svc.cluster.local:8080/]
Feb 12, 2018 11:16:41 PM
org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect,
JNLP-connect, Ping, JNLP2-connect]
Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
  Agent address: jenkins-jenkins-agent.jenkins.svc.cluster.local
  Agent port:    5
  Identity:  5d:e6:82:6c:06:4a:ef:96:ae:47:09:b2:cc:58:e8:0a
Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to jenkins-jenkins-agent.jenkins.svc.cluster.local:5
Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Feb 12, 2018 11:16:43 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed:
5d:e6:82:6c:06:4a:ef:96:ae:47:09:b2:cc:58:e8:0a
Feb 12, 2018 11:16:55 PM hudson.remoting.jnlp.Main$CuiListener status
*INFO: Connected*

-- 
Brandon Pinske
Site Reliability Engineer
Rabb.it

-- 
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/aae360a9-e14f-4e9e-94cf-63f75ad5d468%40rabb.it.
For more options, visit https://groups.google.com/d/optout.

Bitbucket payload in multibranch build

[dene14]

Hello there!

I'm trying to implement smart notification for a developer who did push to 
repo based on build success/failure.
However, I cannot see any evidence how to get an access to bitbucket 
payload in multibranch. There is simply no BITBUCKET_PAYLOAD envvar :(

Any advice on that?

-- 
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/ab70bae7-eccb-4cf2-9363-d81235d76fe1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: List of git branches using Jenkinsfile parameters

[niristotle okram]

What kind of pipeline job is that? The one with jenkins groovy dsl or the
declarative one? How r u listing remote git branches in the job parameters
to be selected by a user before starting a build?

I haven’t came accoss that feature. And for the multi branch job, wasnt it
suppose to build any new branch? Why do u want to select specific branch
with it?

On Mon, Feb 19, 2018 at 10:13 AM  wrote:

> Hmm, I was wondering that myself, but the pipeline job can run and
> populate the parameter list at runtime, so I was wondering if/hoping the
> multibranch can do the same
>
>
> On Monday, 19 February 2018 15:14:17 UTC+11, ok999 wrote:
>
>> I dont have much experience with multi branch job types. Nonetheless, The
>> below requirement may not be possible unless there is some plugin to do so.
>>
>> The job / local workspace will not have any idea of remote branches
>> before you trigger it. A workaround may be to start the job, create a stage
>> that checks out the remote branches, and use the input dsl for a users
>> input.
>>
>>
>>
>>
>>
>>
>>
>> On Mon, Feb 19, 2018 at 9:33 AM  wrote:
>>
> Correct. If I choose to "Build with parameters" I want a Branch parameter
>>> to list all the branches of that jobs repository, but defined in a
>>> Jenkinsfile as a multibranch pipeline
>>>
>>>
>>> On Monday, 19 February 2018 14:39:07 UTC+11, ok999 wrote:
>>>
 Not sure, if i am following this requirement. Am I understanding it
 right, if you want to list the remote branches of a repository on jenkins
 job as a parameters?

 On Mon, Feb 19, 2018 at 8:43 AM  wrote:

>>> What I want to be able to do -
>
> Have a Jenkinsfile that will automatically build a git master branch
> if triggered automatically on commit but prompt the user to select from a
> branch if run manually
>
> Selecting the master if triggered automatically is no problem using
> parameter default value, but I cannot for the life of me figure out a way
> to populate the branch parameter
>
> I've looked for a way to use the Git parameters plugin but while there
> is plenty of examples on how to use it though the gui with a pipeline
> script, I cant find any documentation or examples on how to use it with
> multibranch/Jenkinsfile using code
>
> can anyone help with the above, or any other method?
>
> 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-use...@googlegroups.com.


> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1995eb74-988c-4fb2-b972-f849771769c2%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
 --
 Sent from mobile device, excuse typos if any.

>>> --
>>> 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/c987a2f1-9e25-4b20-bfa1-233a47a0ea43%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> Sent from mobile device, excuse typos if any.
>>
> --
> 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/d4462e32-4ff0-489c-adb7-3fce522e22d9%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Sent from mobile device, excuse typos if any.

-- 
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/CAPzcO4jWvAHNnnqJH9LGmvWy5Zqf3FL67cjOnMSLWJbi87gaWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

PTC Integrity with Jenkins Deployment

[Narayana Boominathan]

I've build which is checked-in on the PTC Integrity and I've raised the CR 
or SR ticket(Build & Deploy Request) on the PTC life manager by developer 
for deploy his build on some  server and the version of the build is 
.

As of now as a deployment team we are following the below process

If we get a ticket we assigned it to us.
And then collect all those details which is on the ticket by manually and 
doing deployment also by manually.

Instead of this now we are planning to do this on automation.

How do I get the following details on the Jenkins to do my deployment. I've 
some bat script to do the deployment. To kick off that bat file, it needs 
the following details
1. Version of the build
2. Which server the Build needs to deploy
3. Where the build file is located

I need to collect all those above details from the PTC ticket which I had 
created earlier
Is there any possiblity from Jenkins can I able to get those values from 
the ticket number.

I'm very new to PTC.
I came to know from google there is a plugin available for PTC with Jenkins

Could someone please help on 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/93252141-9e88-4055-9f74-ef2cb1739576%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins, saml and Keycloak SSO

[Ivan Fernandez Calvo]

The Data binding Method SAML Plugin setting should be HTTP-POST, you IdP 
metadata only support HTTP-POST (https://github.com/jenkinsci/saml-plugin/blob/master/doc/CONFIGURE.md
https://github.com/jenkinsci/saml-plugin/blob/master/doc/TROUBLESHOOTING.md

-- 
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/f0f51685-6de1-4209-b362-a96d510a1696%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question about JDK and Maven through Jenkins

[Fábio Cabrita]

Thats the strange part because I have *javac *installed in this system.

Now I have added a new field for jdk in jenkinsfile(as well as in Global 
Tools Installer) and its working:

tools {
jdk 'java_9'
}


Thanks for the help Cyrille Le Clerc!

segunda-feira, 19 de Fevereiro de 2018 às 13:54:39 UTC, Cyrille Le Clerc 
escreveu:
>
> Can you install "java-1.8.0-openjdk-devel" on your server so that 
> javac-1.8 is also installed?
>
> I suspect that Jenkins and Maven get tricked by the fact that your default 
> "java" installation doesn't have a "javac" compiler.
>
> If you cannot install "java-1.8.0-openjdk-devel", I strongly recommend to 
> rely on Jenkins' capability to install a JDK:
>
>- In Jenkins UI, with Jenkins administrator privileges, navigate to 
>"Manage Jenkins / Global Tools Installer"
>- In the "JDK" section, click on "JDK Installations..." then "Add JDK"
>   - Choose the name "1.8"
>   - Select a JDK 8 version (e.g. "Java SE Development Kit 8u162")
>   - Enter oracle.com credentials 
>- Update your pipeline script and add "jdk: '1.8' "to your 
>"withMaven"() step: "withMaven(jdk: 1.8', ...){...}"
>
> Cyrille
>
> On Monday, February 19, 2018 at 11:29:09 AM UTC+1, Fábio Cabrita wrote:
>>
>> Here are both command paths:
>>
>> root@jenkins-server /h/jenkins> which java
>> /bin/java
>> root@jenkins-server /h/jenkins> which javac
>> /bin/javac
>>
>> While checking mvn, I notice that Java home is set to JRE instead of JDK:
>>
>> [jenkins@jenkins-server ~]$ mvn --version
>> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-
>> 18T08:58:13+01:00)
>> Maven home: /usr/local/maven
>> Java version: 1.8.0_161, vendor: Oracle Corporation
>> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/
>> jre
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "linux", version: "3.10.0-693.17.1.el7.x86_64", arch: "amd64", 
>> family: "unix"
>>
>> Checking Java version:
>>
>> [jenkins@jenkins-server ~]$ java -version
>> openjdk version "1.8.0_161"
>> OpenJDK Runtime Environment (build 1.8.0_161-b14)
>> OpenJDK 64-Bit Server VM (build 25.161-b14, mixed mode)
>>
>> In this system I have several Java's versions installed in this system:
>>
>> [root@jenkins-server ~]# sudo update-alternatives --config java
>>
>> There are 2 programs which provide 'java'.
>>
>>   SelectionCommand
>> ---
>> *+ 1   java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk
>> -1.8.0.161-0.b14.el7_4.x86_64/jre/bin/java)
>>2   java-1.7.0-openjdk.x86_64 (/usr/lib/jvm/java-1.7.0-openjdk
>> -1.7.0.161-2.6.12.0.el7_4.x86_64/jre/bin/java)
>>
>> [root@jenkins-server ~]# sudo update-alternatives --config javac
>>
>> There is 1 program that provides 'javac'.
>>
>> Selection Command
>> ---
>> *+ 1 java-1.7.0-openjdk.x86_64 (/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.161
>> -2.6.12.0.el7_4.x86_64/bin/javac)
>>
>> But dont know how to set mavens to use java JDK.
>>
>

-- 
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/0dc56b5f-bc7f-442d-a991-dc77efaa177d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question about JDK and Maven through Jenkins

[Cyrille Le Clerc]

Can you install "java-1.8.0-openjdk-devel" on your server so that javac-1.8 
is also installed?

I suspect that Jenkins and Maven get tricked by the fact that your default 
"java" installation doesn't have a "javac" compiler.

If you cannot install "java-1.8.0-openjdk-devel", I strongly recommend to 
rely on Jenkins' capability to install a JDK:

   - In Jenkins UI, with Jenkins administrator privileges, navigate to 
   "Manage Jenkins / Global Tools Installer"
   - In the "JDK" section, click on "JDK Installations..." then "Add JDK"
  - Choose the name "1.8"
  - Select a JDK 8 version (e.g. "Java SE Development Kit 8u162")
  - Enter oracle.com credentials 
   - Update your pipeline script and add "jdk: '1.8' "to your "withMaven"() 
   step: "withMaven(jdk: 1.8', ...){...}"

Cyrille

On Monday, February 19, 2018 at 11:29:09 AM UTC+1, Fábio Cabrita wrote:
>
> Here are both command paths:
>
> root@jenkins-server /h/jenkins> which java
> /bin/java
> root@jenkins-server /h/jenkins> which javac
> /bin/javac
>
> While checking mvn, I notice that Java home is set to JRE instead of JDK:
>
> [jenkins@jenkins-server ~]$ mvn --version
> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-
> 18T08:58:13+01:00)
> Maven home: /usr/local/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/
> jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-693.17.1.el7.x86_64", arch: "amd64", 
> family: "unix"
>
> Checking Java version:
>
> [jenkins@jenkins-server ~]$ java -version
> openjdk version "1.8.0_161"
> OpenJDK Runtime Environment (build 1.8.0_161-b14)
> OpenJDK 64-Bit Server VM (build 25.161-b14, mixed mode)
>
> In this system I have several Java's versions installed in this system:
>
> [root@jenkins-server ~]# sudo update-alternatives --config java
>
> There are 2 programs which provide 'java'.
>
>   SelectionCommand
> ---
> *+ 1   java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-
> 1.8.0.161-0.b14.el7_4.x86_64/jre/bin/java)
>2   java-1.7.0-openjdk.x86_64 (/usr/lib/jvm/java-1.7.0-openjdk-
> 1.7.0.161-2.6.12.0.el7_4.x86_64/jre/bin/java)
>
> [root@jenkins-server ~]# sudo update-alternatives --config javac
>
> There is 1 program that provides 'javac'.
>
> Selection Command
> ---
> *+ 1 java-1.7.0-openjdk.x86_64 (/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.161-
> 2.6.12.0.el7_4.x86_64/bin/javac)
>
> But dont know how to set mavens to use java JDK.
>

-- 
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/89ba8611-110c-476b-97d4-feb337ed8464%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: .ssh/config file not read?

[LnT]

Hi-

is this resolved..?
I'm getting the same error.   




On Monday, September 21, 2015 at 3:07:17 PM UTC+5:30, Karsten K wrote:

> Hi all,
>
> sorry in case for a duplicated question, but by scrolling through various 
> forums I couldn't find any concrete info.
>
> I have the feeling that jenkins doesn't really read my ssh-config file. 
>
> On my master:
> created a certificate called 'jenkins'. 
> I copied this identityfile on each slave.
>
> Since the username on each slave is called 'slave' I created a ssh config 
> file pointing the user 'slave' to identityfile 'jenkins'. 
> However I constantly run into 'ERROR: Server rejected the 1 private key(s) 
> for jenkins' ...
> So I had to create a new profile called 'slave' given the correct key and 
> it seemed to work.
>
> So the question here is why username 'jenkins' fails when ssh into any 
> slave-machine just works fine based on the config file.
>
>
> any ideas?
>

-- 
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/7e6175c5-57f8-4ddc-819c-e9bfea480d81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins, saml and Keycloak SSO

[Vikas Kumar]

Hello Ivan,

Thanks for your response. To be honest, I am a novice in SAML at the moment 
but have managed to hook Keycloak to AWS using some tutorials :).

I have tried turning off signing and encryption in Keycloak and configured 
below parameters after google-ing.



This is my IDP metadata configured in Jenkins


http://13.211.108.58/auth/realms/amp;
   xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
   xmlns:dsig="http://www.w3.org/2000/09/xmldsig#;
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
   
  http://13.211.108.58/auth/realms/amp/protocol/saml; />
   urn:oasis:names:tc:SAML:2.0:nameid-format:persistent

   urn:oasis:names:tc:SAML:2.0:nameid-format:transient

   urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified

   urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress



  http://13.211.108.58/auth/realms/amp/protocol/saml; />
  

  -3exGGnBkt9XwDMBUwkkkXg2JYGXg-_YAcr5gwYTSN0

  

MIIClTCCAX0CBgFhnj1EXDANBgkqhkiG9w0BAQsFADAOMQwwCgYDVQQDDANhbXAwHhcNMTgwMjE2MTA0OTMwWhcNMjgwMjE2MTA1MTEwWjAOMQwwCgYDVQQDDANhbXAwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCXWPRbbOOjiDlBR3retdd1hIrdbPbsQw88AoYj3+4kIJGmAl+g7z/DIEdjTMsn5Jbx6NF2UUS4b2c/rIkCqEMAMz4CKfOFKppbEGTgAJmyAM0uNvo56K01lhsiGVgj9JRqrX5ANoH5PQWkHeF/miyCm1n6EFdyefheNP2lGksofpphrgW9ChTXPHyLhdv1KCJCTI2c7b+HwAhslI0Zw/XT9ZlKQ3/dkc4mYVRsTKjVKPWXSZwvp7eSNDPn1cbEtuUCOikaxcKVKZBghW4ZwspY7DJZIulhnS4rZB8JO2+GWWAJAqIUZffoh99yHANM/wVHwtEdl6Eckw0IiVTW3RSFAgMBAAEwDQYJKoZIhvcNAQELBQADggEBAHEkunR6dy+/b3cPl+GJNKpmkMbjMjNQ3P/7YMHQYldl6pr0njYGIl7wh6uA5JF176bz5oP+XddNiySue7lPm+AbsEvefOcfpWt0eBAOHWmZrZLWvp5toE7ipNYd+coicRsddDTAm9ZIdP9X2jNDHrouCkfNHgNIIeLYWdlYUb9VvYW0JbdiwqJs5iCLBIo9M3buffltGyI1ghK0S0/xQf6SgxDLLH4kjU0POj3XMMNDGB4YlPcWeA9DzEQzvWI2gK8Ul/MV3TbYdTXxIRJqef3Qv5ZkCKFBMPORdfLKZyOvP7vex3MSZZzfX342ZjZmzvrlQtOekvldP2OupFeLV8M=

  

  
   


I have configured this as below








Request you to please have a quick look and let me know where I am going 
wrong. The above configuration in Jenkins has this stack trace

org.pac4j.saml.exceptions.SAMLException: Identity provider has no single 
sign on service available for the selected profileorg.opensaml.saml.saml2.
metadata.impl.IDPSSODescriptorImpl@3ce818f6
 at org.pac4j.saml.context.SAML2MessageContext.getIDPSingleSignOnService(
SAML2MessageContext.java:93)
 at org.pac4j.saml.sso.impl.SAML2AuthnRequestBuilder.build(
SAML2AuthnRequestBuilder.java:70)
 at org.pac4j.saml.sso.impl.SAML2AuthnRequestBuilder.build(
SAML2AuthnRequestBuilder.java:34)


Thanks in advance.


Regards



On Monday, 19 February 2018 05:50:36 UTC+11, Ivan Fernandez Calvo wrote:
>
> >How can I add the IDP public key to my keystore and how to configure 
> jenkins to decode saml message with the key in the keystore ?
>
> The IdP key should be in the IdP Metadata as described in 
> https://www.oasis-open.org/committees/download.php/51890/SAML%20MD%20simplified%20overview.pdf
>  If You are generating the IdP metadata in a manual way, you can use this 
> tool https://www.samltool.com/idp_metadata.php
>

-- 
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/64276bab-fbda-4731-89ea-5699e6d93391%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question about JDK and Maven through Jenkins

[Fábio Cabrita]

Here are both command paths:

root@jenkins-server /h/jenkins> which java
/bin/java
root@jenkins-server /h/jenkins> which javac
/bin/javac

While checking mvn, I notice that Java home is set to JRE instead of JDK:

[jenkins@jenkins-server ~]$ mvn --version
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T08:
58:13+01:00)
Maven home: /usr/local/maven
Java version: 1.8.0_161, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-693.17.1.el7.x86_64", arch: "amd64", 
family: "unix"

Checking Java version:

[jenkins@jenkins-server ~]$ java -version
openjdk version "1.8.0_161"
OpenJDK Runtime Environment (build 1.8.0_161-b14)
OpenJDK 64-Bit Server VM (build 25.161-b14, mixed mode)

In this system I have several Java's versions installed in this system:

[root@jenkins-server ~]# sudo update-alternatives --config java

There are 2 programs which provide 'java'.

  SelectionCommand
---
*+ 1   java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-
1.8.0.161-0.b14.el7_4.x86_64/jre/bin/java)
   2   java-1.7.0-openjdk.x86_64 (/usr/lib/jvm/java-1.7.0-openjdk-
1.7.0.161-2.6.12.0.el7_4.x86_64/jre/bin/java)

[root@jenkins-server ~]# sudo update-alternatives --config javac

There is 1 program that provides 'javac'.

Selection Command
---
*+ 1 java-1.7.0-openjdk.x86_64 (/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.161-
2.6.12.0.el7_4.x86_64/bin/javac)

But dont know how to set mavens to use java JDK.

-- 
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/4b27f009-70bd-4f94-89e4-63178e24195a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.