
Key: |
QB-87
|
Type: |
Improvement
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Major
|
Assignee: |
Robin Shen
|
Reporter: |
Robin Shen
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 05/Jun/06 08:14 PM
Updated: 31/Aug/06 07:02 AM
|
|
Component/s: |
None
|
Affects Version/s: |
None
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
From Dave's post:
I have a question pertaining to the contents of the revision log(s). I use Perforce as my SCM. It appears the revision log gets the information based on what's changed since the last build, regardless if it's a successful or failed build. Is that correct?
My suggestion would be to get the changes since the last successful build vs. the last build. You may go through a couple build cycles where it's broken and when you finally get a successful build, you have a disjointed revision content. You'd have to go back to each build since the last successful build to figure out the exact changes in the current successful build.
We like to use the revision log as a 'what's new' in the current build. That's how we view the log's functionality.
|
Description
|
From Dave's post:
I have a question pertaining to the contents of the revision log(s). I use Perforce as my SCM. It appears the revision log gets the information based on what's changed since the last build, regardless if it's a successful or failed build. Is that correct?
My suggestion would be to get the changes since the last successful build vs. the last build. You may go through a couple build cycles where it's broken and when you finally get a successful build, you have a disjointed revision content. You'd have to go back to each build since the last successful build to figure out the exact changes in the current successful build.
We like to use the revision log as a 'what's new' in the current build. That's how we view the log's functionality. |
Show » |
No work has yet been logged on this issue.
|
|