| Key: |
QB-5
|
| Type: |
New Feature
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Robin Shen
|
| Reporter: |
Robin Shen
|
| Votes: |
4
|
| Watchers: |
3
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 05/Mar/06 10:57 PM
Updated: 25/Jun/10 06:20 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Issue Links:
|
Relate
|
|
|
|
This issue relates:
|
|
QB-6
Get issue keys in commit messages to ...
|
|
|
|
|
|
|
When a build happens, ideally it should be able to collect all checkin comments from version control systems since last build, and form a release notes file which can be packaged into the new build.
This can be done by providing a special step.
|
|
Description
|
When a build happens, ideally it should be able to collect all checkin comments from version control systems since last build, and form a release notes file which can be packaged into the new build.
This can be done by providing a special step. |
Show » |
|
Get all checkin comments since last build to form release notes of a build
An example of such output file:
<changeset>
--<frombuild>2.1 build 1234</frombuild>
--<lastbuild>2.1 build1256</lastbuild>
--<filelist>
----<file name="file1.cs" viewdir="/Project1/sources">
------<comment date="20061230230113" user="Yakushkov Mikhail">
--------<CDATA>Some useful comment about performed changes</CDATA>
--------<labellist>
----------<label>QA_2.1_1235</label>
----------<label>REL_2.1_1241</label>
--------</labellist>
------</comment>
----</file>
--</filelist>
</changeset>
As a variant you can add a new kind of building step that creates a report using user-supplied XSL-file. But this variant is less flexible than the first one.
As addition you can add possibility to choose by user a build-version (label) from which start to collect notes.
Also you can collect information from change requests to those attached revisions of files. It's seems like useful only for StarTeam. It's an option but isn't very required.
Probably most of this work for StarTeam I can perform using a NAnt script using StarTeam API. I'm not sure it's possible for other VCS you better now. Anyway it would be useful to have some reporting functionality common among diffirent VCS through QuickBuild interface/functionality.