Issue with cps-method-mismatches

2019-07-30 Thread Stefan.Rademacher
Hi everyone, my Jenkins Pipeline prints the following message: expected to call java.util.LinkedHashMap.action but wound up catching org.jenkinsci.plugins.workflow.cps.CpsClosure2.call The Jenkinsfile is pipeline { agent { label "Linux-Agent" } stages { stage("Stage") { steps {

WG: Issue with cps-method-mismatches

2019-10-23 Thread Stefan.Rademacher
Hi everyone, it's been a while, since I asked the question below. I still couldn't figure out, what 'm doing wrong. Is there anyone, who has a hint? Thanks! Stefan _ Von: Rademacher, Stefan Gesendet: Dienstag, 30. Juli 2019 14:04 An: jenkinsci-users@g

AW: Issue with cps-method-mismatches

2019-10-23 Thread Stefan.Rademacher
Hi Reinhold, in can't believe, it was that easy… Thanks, your guess worked!!! Regards Stefan Von: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] Im Auftrag von Reinhold Füreder Gesendet: Mittwoch, 23. Oktober 2019 15:36 An: jenkinsci-users@googlegroups.com Betreff:

Use environment variable from upstream build

2020-02-24 Thread Stefan.Rademacher
Hi everyone, I used to set an environment variable via env.x = "..." in my Jenkinsfile. Another pipeline has an upstream trigger configured and runs right after the first pipeline build finishes. It reads the environment from the upstream build. It used to work, that the downstream build could

AW: Use environment variable from upstream build

2020-02-25 Thread Stefan.Rademacher
Hi, as a simple test case, I created these two pipelines. First, the "upstream pipeline": pipeline { agent { label 'Linux-Test' } environment { name = 'foo' } stages { stage('Set environment') { environment { name = 'bar'

AW: Use environment variable from upstream build

2020-02-26 Thread Stefan.Rademacher
Hi, thanks for the suggestions. Sidenote: This solution, using environment variables used to work and afaik, we didn't make any pipeline changes, related to this. Unfortunately I can't narrow down, since when exactly it broke. I can confirm, that allowing undefined parameters (JENKINS-56875) do

Pipeline SCM trigger breaks

2020-05-14 Thread Stefan.Rademacher
Hi, I have configured a multibranch pipeline (declarative), which checks out several git repositories and has pollSCM('') configured: I deleted and recreated the build for branch 'int'. The first two builds were triggered by branch indexing and manually by me. The 'Git Polling Log' from yesterd

AW: Pipeline SCM trigger breaks

2020-05-25 Thread Stefan.Rademacher
Hi everyone, does anyone know, how I can get more information about the internal state of the Jenkins Git Plugin, especially the mapping from repositories/branches to pipelines, that need to be triggered on SCM changes? Are there classes, that I can add to a log recorder, files in Jenkins Home,