How to identify from which starting build a particular bug-fix/change-set is available if snapshot/baseline is unknown?
Problem Statement:
- Bug-fix/change-set was resolved by a developer while ago.
- Multiple snapshots/baselines where created after the deliver.
- At later stage, Developer needs to identify from which software build his changes are available.
In Clearcase:
- Developer identifies Bug-fix/change-set are available in a particular version of a file using version tree.
- Developer uses clearcase version tree -> Properties of Version, identifies the first build the changes are available.
Current RTC Environment we adopted:
- Project reuse Work item
- After successful build is completed it does not store build number in incident management.
- After successful build compares snapshot between 2 baselines and store in read-me and release notes.
In RTC:
- Everything is change-set based. We can identify file history and change-set and identify the date it was delivered.
- Based on date of delivery identify build date close to deliver date and search in read-me which is not straight forward.
Question:
- If we do not know the snapshot/baseline, do we have any better options to find which is the first build a particular version of file or change-set is checked-in.
Nice to have:
- In RTC History, if we have column which displays "Baseline/snapshot" if available for each change-set would be helpful.
One answer
First of all, any public build creates a snapshot. The build result refers to the snapshot and the snapshots can be found on the workspace/stream.
You can use locate change set to search the snapshots if they contain the change set(s) you are interested in.
I would assume from the snapshot creation time and the build results you should be able to also identify the build result you are interested in.
From a build result, you can create a release, which is the final product you deliver to customers. This holds all the rest together.
You can use locate change set to search the snapshots if they contain the change set(s) you are interested in.
I would assume from the snapshot creation time and the build results you should be able to also identify the build result you are interested in.
From a build result, you can create a release, which is the final product you deliver to customers. This holds all the rest together.