credentials-binding-plugin and private key files

Anyone else noticed this? I just updated my Jenkins to 2.289.1 and some of my build that use a private key file for SSH access fail like this (complete stacktrace at bottom): FATAL: Cannot use the same key in both secretValues and publicValues Turns out that I got rid of the message if I edited

Re: How to write a yaml configuration for certificate with JCasC plugin?

Upgraded to 1.20 and I got the same error. Sigh, wish they could actually get the syntax set once and for all. -- 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

Re: How to write a yaml configuration for certificate with JCasC plugin?

Hi, this matches my config which looks like this: - certificate: id: "our-keystore" description: "certificate-alias" keyStoreSource: fileOnMaster: keyStoreFile: "/var/jenkins_conf/secrets/ComodoCodeSigning2018.p1

Re: How to write a yaml configuration for certificate with JCasC plugin?

This matches my configuration except that I had to add the alias of the certificate as "description". Not sure if that was the error I got though. Eveything else matches my config. /Andreas -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To u

Re: Run pipeline flyweight executors off of master

In some instance this checkout can be helped/removed by doing a lightweight checkout, but it don't work on our builds since we have ${TAGNAME} parameters on the checkouts. And parameters in the SCM URL are not compatible with lightweight checkout. -- You received this message because you are s

Re: Pipeline: How to modify Build History status monitor

Not quite sure what you want to do, but we modify currentBuild.displayName and currentBuild.description from within our pipeline. They are documented under Pipeline Syntax | Global Variable Reference /Andreas -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: Not able to access and create files in path location(\\\\192.168.0.1/f$/D:\\p.txt)

Your UNC path looks very strange. As I interpret it you have the following parts: 192.168.0.1 - localhost probably f$ - automatic share created by windows on drive F: D:\\p.txt - file on another drive Question is, what are you trying to access? You could try: 192.168.0.1\D$\p.txt On Sunday,

Re: Blue ocean plugin supported version

2.121 is a later version than 2.7 Not quite sure what you need more than that? Regards, Andreas -- 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-user

Re: Error while running dynamically created parallel stages

I have a similar solution, but without the inner stage, just as Wouter suggest. And that works great. So try it without stage("Build parallel $target") { -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop

Re: Configuration of environment variables in Pipeline

Hi, is there a specific reason you don't use this structure? withEnv(['MY_VAR=VAL']) { // some block } Regards, Andreas On Tuesday, April 24, 2018 at 5:31:47 PM UTC+2, Daniel Belenky wrote: > > Hi, > > I'm trying to configure an environment variable during the Pipeline that > later on shoul

Re: Pipeline PATH problems (seems related to JENKINS-41339)

hint towards that as well? Seems that the rule have changed (for the better), but trying to understand why old (more or less misconfigured) systems suddenly fail isn't always that easy. Cheers, Andreas On Monday, June 19, 2017 at 6:44:19 AM UTC+2, Andreas Magnusson wrote: > > After

Pipeline PATH problems (seems related to JENKINS-41339)

After an upgrade of my Jenkins installation (2.65 and all plugins updated) I cannot for my life get the 'sh' command to work. This is my mini example: node('linux') { sh 'echo $PATH' } and this is the output: Started by user anonymous [Pipeline] nodeRunnin

Double changes in Declarative Pipeline job

We happily using Declarative Pipeline here, however I've noticed from the very beginning that we get double build "recordings" in the Changes log. It seems that we get one log from the checkout/update of the workspace for the Jenkinsfile, and then one from the automatic checkout/update from the

[pipeline-model-definition] No such DSL method 'credentials'

Hi, I'm trying to convert our pipeline build to work with pipeline-model-definition, but have a problem. According to the docs (https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/SYNTAX.md) I should be able to create a small example like this: pipeline { agent any