Change sets created for build definition updates
We are using Jazz source control (GA) and have a number of components containing source in our project. I have updated one of our build definitions, and this has resulted in an incoming change for every component in the Pending Changes view. The change contains no updated files, and is titled like:
300: Alpine Test Build Definition_<date><time>
We don't get these change sets created when other build definitions are updated.
Is this expected, and what purpose does it serve?
300: Alpine Test Build Definition_<date><time>
We don't get these change sets created when other build definitions are updated.
Is this expected, and what purpose does it serve?
4 answers
Updating a build definition should not cause any changes in source control. What changes did you make?
Are the incoming changes change sets or baselines? Is it possible that you ran a build that created baselines in each component? If so, those baselines would show up as incoming when you look at Pending Changes in your workspace.
Martha
Jazz Developer
Are the incoming changes change sets or baselines? Is it possible that you ran a build that created baselines in each component? If so, those baselines would show up as incoming when you look at Pending Changes in your workspace.
Martha
Jazz Developer
The changes were to the load directory and the build target. I did run a build, but I don't know what causes baselines to be created. Another quirk we noticed after my original post was that a real code change set (associated with a specific WI) was shown in the Pending Changes view as one of these 'build definition' change sets.
If you have set your pending changes view to flow with the build workspace
(this would be unusual) or if your build definition is pointing directly at
your main development stream, you may be seeing incoming baselines because
when a build is performed, a baseline is created for each component in the
build workspace.
You might benefit from the discussion here:
https://jazz.net/forums/viewtopic.php?t=2634
---
Ryan Manwiller
Jazz Team
(this would be unusual) or if your build definition is pointing directly at
your main development stream, you may be seeing incoming baselines because
when a build is performed, a baseline is created for each component in the
build workspace.
You might benefit from the discussion here:
https://jazz.net/forums/viewtopic.php?t=2634
---
Ryan Manwiller
Jazz Team