RE: Subversion Plugin - version in workspace?

Hi Rick, Yes, this is configurable, e.g. via JCasC: subversionSCM: workspaceFormat: 31 Or in manual work-of-art in global settings: configure system > Subversion > Subversion Workspace Format HTH Reinhold From: jenkinsci-users@googlegroups.com On Behalf Of Richard Frank Sent: Sonntag,

RE: LTS 2.303.1 and JCasC / RBAC - startup failure

Just for the sake of slightly more details: * Without RBAC, but exact these versions of LDAP and JCasC (and actually many many more plugins) this works fine with 2.303.1 Cheers, Reinhold From: jenkinsci-users@googlegroups.com On Behalf Of Alan Sparks Sent: Mittwoch, 25. August 2021 22:11

RE: Console logs of parallel stages

Please have a look at it in BlueOcean UI HTH Reinhold From: jenkinsci-users@googlegroups.com On Behalf Of Jenkinsuser Sent: Montag, 5. Juli 2021 16:29 To: Jenkins Users Subject: Console logs of parallel stages Hello, I Hope you are doing well. I am facing some difficulties related to

RE: Using withEnv with withCredentials

Sorry, Björn, but I think I didn’t get it: * Is your suggestion to use? * withEnv([“http_proxy=https://${PROXY_CREDENTIALS}@proxy-endpoint.com:3128”]) { * But isn’t that what kelvSYC also tried and “gets flagged as unsafe by Jenkins” *

RE: [JCasC] job parameters lost when re-starting docker container / reloading existing configuration

Hi Danny et al, I think, I just stumbled over the same problem: * parameterized pipeline + Jenkins Docker container restart + JCasC + JobDSL (that is re-generating the parameterized scripted pipeline – pipeline from SCM -- during Jenkins startup via

RE: jiraComment pipeline step throwing groovy.lang.MissingMethodException

all(Checker.java:165) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) at WorkflowScript.notifyIssueTrackerIfApplicable(WorkflowScript:239) at WorkflowScript.run(WorkflowScript:62) at ___cps.transform___(Native Method) [...] On Tue, Jan 12, 2021 at 4:14

RE: how to avoid cps error using XmlSlurper() method in jenkins pipeline

Hi jfernandez, Naïve guess(es): * Are you maybe missing this: import com.cloudbees.groovy.cps.NonCPS * though not sure if the annotation would/should not then lead to an error instead already? * Or is this a declarative pipeline and you are missing the script { … } step based

RE: jiraComment pipeline step throwing groovy.lang.MissingMethodException

Hello Stefan, I think the documentation of the plugin is slightly outdated (or maybe only “COMPATIBILITY.md”): * https://www.jenkins.io/doc/pipeline/steps/jira/#jiracomment-jira-add-a-comment-to-issues *

RE: Where are jekins logs?

Sorry, I could not resist: https://lmgtfy.app/?q=where+are+docker+logs+stored From: jenkinsci-users@googlegroups.com On Behalf Of zil...@gmail.com Sent: Donnerstag, 12. November 2020 16:45 To: Jenkins Users Subject: Re: Where are jekins logs? Thanks Reinhold, I get that. But WHERE are they?

RE: Where are jekins logs?

Hi Chris, $ docker logs https://www.jenkins.io/doc/book/installing/docker/#accessing-the-jenkins-console-log-through-docker-logs HTH Reinhold From: jenkinsci-users@googlegroups.com On Behalf Of zil...@gmail.com Sent: Mittwoch, 11. November 2020 22:26 To: Jenkins Users Subject: Where are

RE: one downstream with multiple upstreams(all upstreams should be success)

Hi Keshav, sorry for interfering, but I think Gianluca’s pseudo code and hint should actually help you: * Job A will wait for both job B and job C to be finished * and only if both were successful, then and only then continue with triggering job D in the next stage HTH Reinhold

RE: The pipeline emailextrecipients step takes too long time

Ad LDAP: we are also using another configuration element, but again, this may not be kriegs-entscheidend userSearchBase: "CN=Users" If you know that it is the emailextrecipients step and it is really that slow, then you could maybe find the problem when remote debugging into Jenkins? But I

RE: The pipeline emailextrecipients step takes too long time

Sorry for the following potentially too naïve hint: In addition try to also play around with the LDAP caching, if not yet activated – because that may also reduce load on LDAP server (in case that is a problem); of course, other LDAP clients in your company should do the same! (I remember that

RE: BackgroundGlobalBuildDiscarder error on jenkins home NFS

Hi Alan, I think there is an additional LogRotater exception stack trace below and it is the same issue as: https://issues.jenkins-ci.org/browse/JENKINS-61687 For possible workarounds (and related bugs ) please see comments from https://issues.jenkins-ci.org/browse/JENKINS-61256 HTH Reinhold

RE: shared library - hashmap error

Hi „judaondo“, 1. Ad “but it doesn’t do anything”: in @NonCPS annotated methods you must not call pipeline steps like “checkout” => seemingly this is skipped (?) rather silently 2. However, in addition the warning log “expected to call WorkflowScript.gitCheckoutMultipleRepositories but

RE: Shared library function cannot call other shared library function in separate file if called function uses "writeFile"

Weird. And sorry for misunderstanding you. There might be a stacktrace in the Jenkins log file (hopefully). Or you could try catch all exceptions in your scripted pipeline to get some more details… I just tried to reproduce your problem (or the one I now think you are describing), but

AW: Shared library function cannot call other shared library function in separate file if called function uses "writeFile"

Hi David, I think that could be related to https://issues.jenkins-ci.org/browse/JENKINS-50736, because there is a pipeline basic step called 'writeFile' (see https://jenkins.io/doc/pipeline/steps/workflow-basic-steps/#writefile-write-file-to-workspace), but maybe Jesse Glick or Andrew Bayer

RE: Issue with cps-method-mismatches

Hi Stefan, Just a naïve guess: This might be a little bug in Jenkins pipeline, but you should be able to work around it… “action” in pipeline file is named argument map element for custom “someStep” step Therefore in custom “someStep” step: additionalActions.action … might still work but

RE: pipelines: how to store script output into a variable?

Hi, the „funny“ answer is: „java -version” prints the version information to stderr… HTH Reinhold From: jenkinsci-users@googlegroups.com On Behalf Of Pa Y Sent: Mittwoch, 23. Oktober 2019 13:40 To: Jenkins Users Subject: pipelines: how to store script output into a variable? Hi, I looked

RE: Whats is the format for custom pipeline library help files?

Hi Martin, This (markup rendering) works fine for me (with HTML markup used in “vars/foo.txt”); of course only once the build succeeds; but I guess you have a different problem (than non-successful builds), because otherwise it does not change at all or is rendered at all. Maybe it also

RE: declarative pipeline and gitlab

Hi Pablo, which Links? I am seeing Links to GitLab “Commits” in “Changes” section (scripted pipeline; only “Push Events” is enabled for GitLab Triggers; Git checkout has configured “gitlab” as repository browser; this requires Git plugin in beta version IIRC; in addition the pipeline finally

RE: Marking of skipped stages in blue ocean

Hi Marek, First of all please also note https://issues.jenkins-ci.org/browse/JENKINS-47286?focusedCommentId=360479=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-360479 -- in the meantime https://issues.jenkins-ci.org/browse/JENKINS-47286 has been therefore (?)

RE: Jenkins Overwriting JobDSL Configured Job

, Chris On Wed, 7 Aug 2019 at 23:54, Reinhold Füreder mailto:r.fuere...@xortex.com>> wrote: Hi Chris, just a very naive guess: * there are certain pipeline options or also called pipeline job properties (e.g. build discarder policy or pipeline triggers or pipeline parameters) that

RE: Jenkins Overwriting JobDSL Configured Job

Hi Chris, just a very naive guess: * there are certain pipeline options or also called pipeline job properties (e.g. build discarder policy or pipeline triggers or pipeline parameters) that lead to updates of the pipeline job config once the corresponding “properties” step (of scripted)

RE: emailext using groovy-html.template with environment variables issue

Hi Amit, (a) in your code/screenshot example the problem: to: '${GERRIT_CHANGE_OWNER_EMAIL}', […] in the to: section i want to use the env variable "GERRIT_CHANGE_OWNER_EMAIL" but it not passing the value ( i tried also with env.GERRIT_CHANGE_OWNER_EMAIL and also

RE: Pipeline: Expected call wound up catching different method

an @NonCPS method I think it’s a lot easier to just avoid using Pipeline steps inside of @NonCPS entirely. Thanks, Devin On Jul 30, 2019, at 03:15, Reinhold Füreder mailto:r.fuere...@xortex.com>> wrote: Sorry to bring this up again, but I am just curious: Sverre wrote (a) „Both the

RE: Pipeline: Expected call wound up catching different method

Sorry to bring this up again, but I am just curious: Sverre wrote (a) „Both these methods [(checkUpstream and checkDownstream)] make[s] a call to releaseUtility.getReleaseBranch.” and (b) that both are annotated with “@NonCPS” and (c) that the latter (releaseUtility.getReleaseBranch) is

RE: Is pipeline timeout suppose to work?

Hi Kevin, I have used “timeout” step in the past and as far as I can remember it worked as expected. Note, however, that I may not have put the “node(…)” step inside the “timeout” step; not sure if that is of any relevance though… HTH Reinhold From: jenkinsci-users@googlegroups.com On

RE: A pipeline throws random java.io.NotSerializableException

Hi Ivan, Yep! I guess you are somewhere in your shared Jenkins pipeline library using sun.net.www.protocol.https.HttpsURLConnectionImpl – most likely because you are doing an URL request for e.g. a REST API call => extract that encapsulated logic into a dedicated method that returns something

RE: Jenkins Pipeline: Variable expansion issues

Hi Mike, it looks like the variables are actually strings with a line break at the end, and not integers? HTH Reinhold From: jenkinsci-users@googlegroups.com On Behalf Of Mike Craig Sent: Montag, 11. März 2019 23:33 To: Jenkins Users Subject: Jenkins Pipeline: Variable expansion issues

RE: MissingMethodException while using shared libraries

Hi, a naive quick guess is that you are using too much groovy, but Jenkins pipeline code is -- well -- not fully groovy… => Maybe try to replace the fields like: @Field final BitbucketBuildOperationsHandler bitbucketUtilities = new BitbucketBuildOperationsHandler(this,env) … in

RE: How to call jenkins custom plugin from Pipeline

Hi Prasad, look at the stacktrace: at WorkflowScript.run(WorkflowScript:2) then you see why: * On line #2 checkout filesystem(clearWorkspace: false, copyHidden: false, path: 'C:\\java-junit-sample-master\\java-junit-sample-master') * … is maybe completely wrong, or in wrong scope, but

RE: Pipeline: Stage View has wrong build status

I also remember to have seen this symptom very few times in the last months; IIRC a jenkins (master) restart actually “fixed” the bad visualization, but of course that is by no means a fix… Reinhold -- You received this message because you are subscribed to the Google Groups "Jenkins Users"

RE: Console full log is truncated

Hello, just a naive guess: it might be due to https://issues.jenkins-ci.org/browse/JENKINS-54752 or Ansi-Color plugin v0.6.0? HTH Reinhold -- You received this message because you are subscribed to the

RE: Blank HTML report in Jenkin's left hand side bar for Performance Center Reports

Hi Mukesh, I guess according to e.g. https://jenkins.io/doc/pipeline/steps/htmlpublisher/ * “reportDir” should not be an empty string and be relative to workspace * “reportFiles” should not be an absolute path, but relative to “reportDir” So maybe try this: publishHTML([…, reportDir:

RE: Pipeline - missing arg causes error: java.io.NotSerializableException: org.codehaus.groovy.util.FastArray

Hello Connor, maybe this gives you some more background on the problem: * https://github.com/jenkinsci/workflow-cps-plugin/blob/master/README.md * https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md Hints: @NonCPS annotation vs. using other (by groovy CPS) supported

RE: 'Project name' field missing

Hi Ewelina, I think quite recently an explicit “Rename” link (below “Configure” link on the left) was introduced instead. HTH Reinhold -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails

RE: How to trigger nightly build via blue ocean?

Hi Zack, I think “cron” trigger according to https://jenkins.io/doc/book/pipeline/syntax/#triggers might be what you are looking for? Please note that the jenkins pipeline documentation is really helpful => just try to use it… HTH Reinhold -- You received this message because you are

RE: How to use Folder-level Shared Libraries in Declarative Jenkinsfile

Hi Michael, I think “folder-level shared libraries” mean that you can configure shared pipeline libraries specific to folders, so a Jenkins folder has in its configuration a section called “Pipeline Libraries” with the hint “Sharable libraries available to any Pipeline jobs inside this folder.

RE: RemoteInvocationHandler statistics and an exception

Hi David, I think the exception is due to https://issues.jenkins-ci.org/browse/JENKINS-50748 and is allegedly fixed in Jenkins 2.117 (https://jenkins.io/changelog/). HTH Reinhold -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To

RE: "Replay" button availability

Hi (and replying to myself), I am very, very, very sure (but admittedly still not certain) now that this is a new behavior – and I dare to call it a bug: any other opinions? Can it be that it can only “replay” builds anymore (?) that were triggered after the last Jenkins (master) restart?

RE: BlueOcean observations from user

Perfect timing: Blue Ocean 1.5.0 is shown as available in plugin manager since a few hours or minutes… -- 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: [DISCUSS] Change Jenkins default logging format

Hi Baptiste, Definitely +1! That is I wish to see the default logging format changed to a one-liner. This is more or less what in our Ansible based provisioning of Jenkins setup is already done: # See

"Replay" button availability

Hi, Since (felt) very recently the "Replay" button is not shown anymore for slightly older (pipeline) builds. What does it depend on? It does not seem to be available based on (a) work day, or (jenkins log inspired suspicions) (b) jobAnalytics or (c) Workspace clean-up. Maybe it always

RE: Extension points for declarative pipeline in shared library

@Francois: Thanks for sharing your approach (that did not come to my mind to be honest). Just for the sake of completeness and kind of praising Jenkins development listening to the needs of us users, please have a look at some of the new features for declarative pipelines just

RE: Extension points for declarative pipeline in shared library

Hello Francois, I think this -- still rather small amount of additional flexibility -- already asks for scripted pipelines instead of declarative ones (cf. https://issues.jenkins-ci.org/browse/JENKINS-46547). At least for now, but I guess/assume not just for now… (Although I just stumbled

RE: Pipeline: Resource Locking Plugin hangs

Very naïve thought(s): While “Do not know why nodeName1 acquired the lock before nodeName released.“ might be just a matter of output flushing/buffering, “The entire build hangs and goes no further.” sounds really frightening to me. Maybe it is the usage of lock inside parallel step and/or

RE: How to keep a running docker container after a build fails?

Hi aps, Just in case the problem is still there and to avoid a misunderstanding: Based on (a) Victor’s hint “tr[y] with the docker.inside syntax […] It might give you the chance to debug it somehow.” and (b) your own comment “I'm really surprised you can't pause the build”:

RE: Resuming of pipelines vs. docker.image(...).inside(...)?

I now dared to file https://issues.jenkins-ci.org/browse/JENKINS-49365 -- 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: Release notes for Blue Ocean 1.4??

I am with David and dare to stress that problem too… (sorry for being cheeky) From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Aldrich Sent: Donnerstag, 25. Jänner 2018 14:03 To: jenkinsci-users@googlegroups.com Subject: RE: Release notes for

Resuming of pipelines vs. docker.image(...).inside(...)?

17 ..., and thus this output at the top of the build log: Running in Durability level: MAX_SURVIVABILITY Is this supposed to work? If so, what am I missing? Or can it work at all? Thanks, Reinhold [balken_print] Reinhold Füreder - XORTEX eBusiness GmbH Testautomat

RE: "ERROR: missing workspace" and chaining builds

Hi Vincent, does it work most of the times? If so, could it be related to https://issues.jenkins-ci.org/browse/JENKINS-27329 “WorkspaceCleanupThread may delete workspaces of running jobs”? HTH Reinhold From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf

RE: Jenkins init.groovy compilation

Hi Jason, yes, I remember stumbling over this as well. Partially I have actually uses a workaround for that compilation failure: However, I am not sure it is worth it – because it is based on using reflection, e.g.: def instance = Jenkins.getInstance() … // LDAPSecurityRealm class depends