Hi -

I'm using the Team Concert plugin (v 1.2.0.1) with Jenkins v 2.19.1 and Pipeline 2.4. Our RTC server is 5.0.2 and so are the build tools.

Normally the build will be triggered on an SCM change, however, I notice that every time I trigger it by requesting from RTC a new parameter is added to the Jenkins configuration. I'm not sure if this is a bug or something wrong with my usage.

Here is my pipeline script:

node {
        checkout scm : [ $class : "RTCScm", overrideGlobal: false, timeout:4800, buildType :[value:"buildDefinition", buildDefinition:"TestStreamForBuildToolsStreamBuild", buildWorkspace:null]]
        pipelineWorkspace = "${env.WORKSPACE}"
        sh 'env'
}

For example, here is a snippet from the config.xml file after several runs.

   <hudson.model.StringParameterDefinition>
          <name>buildResultUUID</name>
          <description>The UUID of the build result in RTC. It is supplied by builds initiated through RTC. For builds initiated through Hudson/Jenkins, no value should be supplied.</description>
          <defaultValue/>
        </hudson.model.StringParameterDefinition>
        <hudson.model.StringParameterDefinition>
          <name>buildResultUUID</name>
          <description>The UUID of the build result in RTC. It is supplied by builds initiated through RTC. For builds initiated through Hudson/Jenkins, no value should be supplied.</description>
          <defaultValue/>
        </hudson.model.StringParameterDefinition>
        <hudson.model.StringParameterDefinition>
          <name>buildResultUUID</name>


Zoe