Option to Not Modify the Build in Jenkins Team Concert Plugin
![]() Thank you for making the Jenkins Team Concert plugin. Would it be feasible to give it an option to not modify the build result when subsequent SCM retrievals occur?
If your build retrieves source code more than once, you really only want a snapshot to be associated with the build the first time. With the current functionality, multiple snapshots (and external links to Jenkins) are created if you access the source code more than once in your job.
Here is a use case that would benefit from this functionality:
We've worked around the issue in step #2 by using the
team_scm_snapshotUUID
environment variable instead of the build definition/
buildResultUUID
. This works OK, but it adds a logic branch to our source retrieval: if it is a personal build, there isn't a snapshot, so we instead need to use the repository workspace UUID.
|
Accepted answer
![]() Yes, without the workaround, the plugin would create multiple build results and snapshots. This issue has been captured in this work item.
Kirk Vogen selected this answer as the correct answer
|