Re: SAML plugin - differentiate between encryption and signing certificate

2020-07-28 Thread Ivan Fernandez Calvo
Hi,

The configuration only allows one certificate, this is used for singing and 
encryption, so it is not possible to use two different certificates.

El lunes, 27 de julio de 2020, 21:54:03 (UTC+2), Chris DW escribió:
>
> Hi , 
>
> When setting up the Jenkins SAML plugin, is it possible to configure two 
> different certificates (generated from the same private key) for signing 
> and encryption? 
> The plugin seems to allow to configure just one key alias from one 
> keystore. (
> https://github.com/jenkinsci/saml-plugin/blob/master/doc/CONFIGURE.md)
> I'ml looking to configure 
> alias 1 = private key A + signing certificate chain C1
> alias 2 = private key A+ encryption certificate chain C2
>
> When enabling option 'Auth Request Signature' to  enable the signature of 
> the Redirect Binding Auth Request, I can see two key descriptors being 
> written to the saml-sp-metadata.xml file: 
>
> 
> http://www.w3.org/2000/09/xmldsig#;>
> 
> ...
>
> and 
>
>  
> http://www.w3.org/2000/09/xmldsig#;>
> 
> ...
>
> This leads me to believe that a setup with different sign and encryption 
> certs is a possibility.
> I've tried to configure the correct values for my setup directly in the 
> saml-sp-metadata.xml file, but the file gets overwritten on each login 
> attempt. 
>
> Does the current implementation of the saml plugin dictate the encryption 
> and signing cert to be the same and if not, how do I configure these? 
>
> Kind regards, 
> Chris
>

-- 
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/b189b9e7-5429-4fa1-9f6d-a72564f8a352o%40googlegroups.com.


!! Need urgent help with Active Choices Reference Parameter !!

2020-07-28 Thread Nishant Jha
Hi Team,

I am using opensource *Jenkins 2.235.3* version on *Centos 7.7* machine 
with *Active Choices Plug-in Version 2.4*

The problem I am running into is very strange

I am using a groovy script to dynamically populate parameters and I am 
using Active Choices Reactive Parameter. In that plugin I have written a 
following groovy script

Groovy Code:

this.class.classLoader.addURL(new 
URL("file:///var/lib/jenkins/.groovy/grapes/org.yaml/snakeyaml/jars/snakeyaml-1.17.jar"))
def url = 'g...@xxx.xxx.com:csd/deployment.git'
def envlist = ['/bin/bash', '-c', ' ssh-add 
 /var/lib/jenkins/.ssh/id_rsa_git; cd /var/lib/jenkins/services/; git 
archive --remote='+ url +' master inventory | tar xvf -' ].execute().
envlist.waitFor()
def yaml = Class.forName("org.yaml.snakeyaml.Yaml").newInstance()
def config = yaml.load(new 
FileReader("/var/lib/jenkins/services/inventory/${SERVICES}.yml"))
return config.all.children."${SERVICES}".children.keySet()

NOTE: SERVICES is another defined parameter

Whereas when I use Active choice reactive reference parameter with same 
code:

Same groovy code works and prints out the following result
"[functional, staging_stable, pilot_stable, prod_stable]"


When I use script console in manage jenkins, it runs fine and prints me the 
same result
Result: [functional, staging_stable, pilot_stable, prod_stable]


When I check web console logs, I get 

"Calling Java server code to update HTML elements... unochoice.js:154:17 

Values returned from server: [[],[]] unochoice.js:157:21 



How can I proceed with debugging, I want to only use Active Choices 
Reactive Parameter?
I have attached the screenshot to show how one is populated and one is not. 
Not enough to go through and debug this problem over the internet.
Can somebody please help?

Thankyou
Nishant

-- 
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/2d7253f5-79c5-4d15-b502-0f7dcdec5ce8o%40googlegroups.com.


Increased usage of 0-executor master (flyweight visibility?)

2020-07-28 Thread 'Gavin Davies' via Jenkins Users
Hello,

We have a Jenkins running Jenkins LTS 2.222.4 on Kuberentes via the Jenkins 
helm chart. We use Kubernetes agents on an EC2 autoscaling group. We have 
2216 projects, each of which uses Jenkinsfile.Master is set to 0 executors 
and no builds should execute there (except for branch indexing and the 
flyweight executors dealing with Groovy etc). 

Since Friday 24th July, we have started to see FAR more activity on master 
and Jenkins CPU usage increased.

When a job is executing, we now see it listed on the agent that it is 
running on AND often under master as well. Clicking on the job’s log shows 
‘running on’ referencing the agent, NOT master. Before Friday, we were not 
seeing any jobs listed under master except for during branch indexing or 
the initial pre-checkout phase.

We would like to know if anything has changed on Jenkins, whereby flyweight 
executors are shown under master? We don’t think we changed anything at our 
end before this happened.

Should the flyweight executors be showing up under master in this way? Or, 
have we totally misread the situation? 

Thanks,
- Gavin

-- 
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/35517303-3804-4e8e-abc9-422cca622dcfn%40googlegroups.com.


Re: Distributed Tasks

2020-07-28 Thread JonathanRRogers
You can use Jenkins to run tests written in a large variety of languages 
with a large variety of test runners, so there's no way to answer your 
question without more details about your tests and how you run them. I run 
tests written in Python using a custom system that runs pytest concurrently 
on several nodes. There may be an easier way for you, depending on your 
needs. I'm not very familiar with elastic-axis, but it doesn't seem very 
well maintained, since its last release was six years ago.

On Monday, July 27, 2020 at 1:03:50 PM UTC-4, Sindhuja Banyala wrote:
>
> I have set of test cases to be run. I will give these to a job which is 
> configured to run on group of nodes(grouped using same label name). 
> I want this particular job to split my test cases and assign to all the 
> free nodes available in this group.
> I tried elastic-axis plugin to achieve this distributed task mechanism, 
> apparently it did not split the test cases instead it concurrently executed 
> the same task on all the nodes present in that group. It would good if 
> anybody can suggest any mandatory/missing configuration for Elastic-axis or 
> any new plug-in that can serve my requirement. 
>

-- 
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/d6e28e16-e405-4300-8408-329e3ff58768o%40googlegroups.com.


Jenkins hang on startup after "Listed all plugins"

2020-07-28 Thread Randall Becker
This has been going on since 2.233. We are getting pretty consistent 
failures of Jenkins right after the "Listed all plugins" message is logged. 
This just on the controller (there are no agents), running JRE 1.8.0_45. I 
have wiped the configuration three times already. As soon as I add pipeline 
jobs and actually do a build, I cannot stop and restart Jenkins. There are 
no weird exceptions showing in the log. This has been reported as a defect 
to Core, with a thread dump, but I have not had any feedback at all. It's 
getting seriously frustrating. Has anyone else seen this or have advice on 
tracking down what's going on?

-- 
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/0870ff38-86af-4744-a212-c87734f07c2fo%40googlegroups.com.