What is the best way to baseline and build selective changesets?
![]()
Andy Jewell (242●2●57●71)
| asked Dec 03 '13, 8:53 p.m.
retagged Dec 06 '13, 9:16 a.m. by David Lafreniere (4.8k●7)
Sorry for the long post! Here is the executive summary for my most pressing issue(from problem #2, below):
What's the best way to build a selected set of changesets in a build workspace? The build workspace is on the target stream.
PROD
^
|
|
UAT
^ ^
/ \
/ \
rel1 rel2
This gives me two challenges:
1) To handle selective builds, we deliver the changesets we want deployed to PROD and the build process will then compare the build workspace to the PROD stream to determine what is being deployed. If everything goes perfectly, this works. If there's a hiccup and the build breaks, then the workspace henceforth matches the PROD stream so there is no longer any deviations between the build workspace and the PROD stream.
I don't like the fact that the build process is dependent on the state of the workspace. I think I'm missing a key paradigm, like possibly creating a baseline of the incoming changesets or alternatively, creating before and after snapshots and then using snapshot comparisons. I also considered creating baselines in the source streams and changing the workspace stream configuration on the fly (rather than using accept at all).
2) The second challenge is inter-related with #1 in the sense that when the build breaks, I'm left with an extremely difficult manual manipulation task. For example, for the PROD deployment, I need to be able to generate a report of all the code being delivered, yet, neither Changeset Explorer nor Changeset Summary seem to give the needed functionality. As far as I can tell, Changeset Explorer just shows you the files in the changeset. CS Summary at least provides a way to load the file but it will not load the entire path nor can you load multiple changesets at once. Locate changeset seemed promising since the changeset results appear in under a stream name that suggests you could load the changeset results into their own workspace, but actually, selecting that option just takes you to the normal repository workspace creation wizard. Is there someway to do something with a set of changesets? For example:
a. Create a workspace on a stream loaded only with selected changesets
b. Generate a report of selected changesets
c. Export selected changesets either to file (load) or as a report
d. Baseline or snapshot the changesets
I'm looking for some way to capture the essential "oneness" of a group of changesets.
Thanks for any suggestions!
- Andy
|
3 answers
![]()
Hi Andy,
Yes, you have to suspend the change set before you create a baseline if you don't want to include the change-set into the Baseline. This should be done from the Repository Workspace ( I mean suspend option). If your having large number of task than its huge task to do. Grouping of Changset can be done using the Baseline. Please let me know if you need any further information. Regards, Arun. |