[JIRA] [delivery-pipeline-plugin] (JENKINS-28848) Erratic PIPELINE_VERSION behavior with other Parameters

[nnord...@ideafidelity.com (JIRA)]

Title: Message Title

Noah Nordrum created an issue   Jenkins / JENKINS-28848 Erratic PIPELINE_VERSION behavior with other Parameters Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 10/Jun/15 6:17 PM Environment: delivery 1.4.7 jenkins 1.616 Environment Injector Plugin 1.91.3 Priority: Major Reporter: Noah Nordrum I get different behavior depending on if a non-pipeline parameter is defined on a Job. Here's the smallest job I could configure. Parameter type doesn't seem to matter. <?xml version='1.0' encoding='UTF-8'?> <project> <actions/> <description></description> <keepDependencies>false</keepDependencies> <properties> <hudson.model.ParametersDefinitionProperty> <parameterDefinitions> <hudson.model.BooleanParameterDefinition> <name>A_PARAMETER</name> <description></description> <defaultValue>true</defaultValue> </hudson.model.BooleanParameterDefinition> </parameterDefinitions> </hudson.model.ParametersDefinitionProperty> </properties> <scm class="hudson.scm.NullSCM"/> <assignedNode>docker-one-slave</assignedNode> <canRoam>false</canRoam> <disabled>false</disabled> <blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding> <blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding> <triggers/> <concurrentBuild>false</concurrentBuild> <builders> <hudson.tasks.Shell> <command>echo &quot;PIPELINE_VERSION: ${PIPELINE_VERSION}&quot;</command> </hudson.tasks.Shell> <hudson.plugins.groovy.SystemGroovy plugin="groovy@1.25"> <scriptSource class="hudson.plugins.groovy.StringScriptSource"> <command>println &quot;build.getEnvironment(listener)[&apos;PIPELINE_VERSION&apos;]: ${build.getEnvironment(listener)[&apos;PIPELINE_VERSION&apos;]}&quot; println &quot;build.buildVariableResolver.resolve(&apos;PIPELINE_VERSION&apos;): ${build.buildVariableResolver.resolve(&apos;PIPELINE_VERSION&apos;)}&quot; </command> </scriptSource> <bindings></bindings> <classpath></classpath> </hudson.plugins.groovy.SystemGroovy> </builders> <publishers/> <buildWrappers> <se.diabol.jenkins.pipeline.PipelineVersionContributor plugin="delivery-pipeline-plugin@0.9.3"> <versionTemplate>1.0.0.${BUILD_NUMBER}</versionTemplate> <updateDisplayName>true</updateDisplayName> </se.diabol.jenkins.pipeline.PipelineVersionContributor> </buildWrappers> </project> If I execute the Job with no additional Parameters, I see the PIPELINE_VERSION in the Parameters page for the Job, but it's not there if there is an additional Parameter defined. It is in the $ {JOB_URL} /api/xml in both situations, and it does seem to be getting passed to downstream jobs. PIPELINE_VERSION also doesn't seem to be available through the buildVariableResolver when an additional Parameter is defined, but is when the parameter is not defined: No additional Parameters defined: Creating version: 1.0.0.36 [A] $ /bin/sh -xe /tmp/hudson51864413681590712.sh + echo 'PIPELINE_VERSION: 1.0.0.36' PIPELINE_VERSION: 1.0.0.36 build.getEnvironment(listener)['PIPELINE_VERSION']: 1.0.0.36 build.buildVariableResolver.resolve('PIPELINE_VERSION'): 1.0.0.36 Additional Parameter defined: Creating version: 1.0.0.35 [A] $ /bin/sh -xe /tmp/hudson5436099757112549933.sh + echo 'PIPELINE_VERSION: 1.0.0.35' PIPELINE_VERSION: 1.0.0.35 build.getEnvironment(listener)['PIPELINE_VERSION']: 1.0.0.35 build.buildVariableResolver.resolve('PIPELINE_VERSION'): null Let me know if there's anything else I can provide/debug/diagnose/etc. Thanks! Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.