Re: Kubernetes plugin - multi clusters

2019-01-18 Thread Tristan FAURE
Thank you for your answer ! So If i have a k8s cloud cloud1 and another one cloud2 I can use the label to select one of them ? In this sample (see bellow) I don't see where I have to insert the label ? pipeline { agent { kubernetes { label "bd-${random}" yaml """ spec: containers: - name: node i

Re: Kubernetes plugin - multi clusters

2019-01-18 Thread Carlos Sanchez
In the pipeline you need the "cloud" parameter https://github.com/jenkinsci/kubernetes-plugin/blob/master/README.md#pod-and-container-template-configuration On Fri, Jan 18, 2019, 09:02 Tristan FAURE wrote: > Thank you for your answer ! > > So If i have a k8s cloud cloud1 and another one cloud2

Re: Kubernetes plugin - multi clusters

2019-01-18 Thread Tristan FAURE
Oops đŸ€ Sorry I will test it. Thank you very much Le ven. 18 janv. 2019 Ă  09:21, Carlos Sanchez a Ă©crit : > In the pipeline you need the "cloud" parameter > > > https://github.com/jenkinsci/kubernetes-plugin/blob/master/README.md#pod-and-container-template-configuration > > On Fri, Jan 18, 2019,

Re: How can we achieve the same effect as Jenkins 1's "Deploy artifacts to Maven repository" with Jenkins 2's pipelines?

2019-01-18 Thread Cyrille Le Clerc
Hello Aaron, thanks David As David said, the "Deploy artifacts to Maven repository" feature of the Maven Job type does not exist "as is" in the Pipeline Maven integration. The recommended solution is to use the "-DdeployAtEnd=true" feature of Maven. See https://maven.apache.org/plugins/maven-d

[no subject]

2019-01-18 Thread David Karlsen
I have a global workflow lib, and my scripts work just file, like the "icpDeploy" one listed in [1] - but I cannot get the docs up in https://myjenkins/pipeline-syntax/globals . According to [2] the naming looks correct. At some point in time this was working - but no longer - did something change

Users unable to build projects they're authorized for via role-strategy-plugin

2019-01-18 Thread Benjamin Primrose
I’m not sure if this is FYI or a plea for helpâ˜ș TL:DR, role-strategy-plugin evaluates user permissions by case-sensitively comparing the username as entered in Assign Roles with the way they typed their name when *logging in*. Running: Jenkins 2.150.2 on windows server 2016 Active Dire

Re: Logins (CAS plugin) not working after upgrading to 2.160 (security)

2019-01-18 Thread Daniel Beck
We documented this issue and a workaround at https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+the+SECURITY-901+fix > On 17. Jan 2019, at 16:32, matthew.web...@diamond.ac.uk wrote: > > I just upgraded Jenkins from 2.159 to 2.160, and then found that I could not > log on to the web int

Re: Users unable to build projects they're authorized for via role-strategy-plugin

2019-01-18 Thread Richard Bywater
I've had this issue in the part. In my experience there isn't really much that you can do about it except to try and get people to use a particular case when logging in (e.g. all lower case). If there's an alternative option that can be chosen would love to hear about it though. Richard. On Sat,