-
Bug
-
Resolution: Unresolved
-
Minor
-
Jenkins 2.60.1 LTS, pipeline-model-definition 1.1.8, maven-metadata-plugin 1.5.0
We're using List maven artifact version in a parameterized build to pass the application artifact version as a parameter to a declarative pipeline script. Unfortunately this does not work (using ${params.ESB_VERSION} as well as ${env.ESB_VERSION}) and the parameter name is always resolved to 'null'.
Declarative pipeline script:
pipeline { agent { label "docker" } stages { […] stage('Build image') { agent { dockerfile { reuseNode true registryUrl "https://registry.comapny.com" registryCredentialsId "dcr-jenkins" additionalBuildArgs "--pull --build-arg ESB_VERSION=${params.ESB_VERSION}" dir "installation/app" } } steps { script { docker { app = docker.build "company/app" } } } } […] } }
Job execution:
[Job_Name] Running shell script
+ docker build -t 0ed28f6bfba3f17d99c8f8689058b9f5c00e8bf3 --pull --build-arg ESB_VERSION=null -f installation/app/Dockerfile installation/app
Note the ESB_VERSION=null string.
- relates to
-
JENKINS-38619 Maven metadata plugin does not work with jenkins pipeline
-
- Resolved
-
[JENKINS-45566] Build parameters are not passed to declarative pipelines
Assignee | Original: Gesh Markov [ gesh ] | New: Andrew Bayer [ abayer ] |
Component/s | Original: maven-metadata-plugin [ 17226 ] | |
Component/s | Original: pipeline [ 21692 ] |
Component/s | New: maven-metadata-plugin [ 17226 ] | |
Component/s | Original: pipeline-model-definition-plugin [ 21706 ] |
Assignee | Original: Andrew Bayer [ abayer ] | New: Gesh Markov [ gesh ] |
Link |
New:
This issue relates to |