| 
|  
 
            
            
                | Key: | QB-2204 |  
                | Type: |  New Feature |  
                | Status: |  Resolved |  
                | Resolution: | Fixed |  
                | Priority: |  Major |  
                | Assignee: | Robin Shen |  
                | Reporter: | Riku Eronen |  
                | Votes: | 0 |  
                | Watchers: | 0 |  
        
          
                    | If you were logged in you would be able to see more operations. |  |  | 
                
| 
    | 
        | QuickBuild Created: 16/Oct/14 01:31 PM  
                Updated: 21/Dec/14 01:07 PM
 |  |  
            | Component/s: | None |  
            | Affects Version/s: | 5.1.34 |  
            | Fix Version/s: | 6.0.0 |  |  | 
        
            
	| Original Estimate: | Unknown | Remaining Estimate: | Unknown | Time Spent: | Unknown |  | 
 
	| 
            Please implement proof build support for AccuRev.
 The command that proof builds should use for retrieving relevant changes form the users workspace is:
 accurev stat -d
 This gives all active elements in the workspace and this is normally what the user should send to a proof build.
 
 I would argue that uncommitted changes are not really interesting although they are quite simple to retrieve:
 accurev stat -m
 This would give all elements that have been modified.
 
 Kept changes however would be interesting to send to a proof build. I think it is not more than reasonable that the user does keep before he/she sends changes to a proof build.
 accurev stat -k
 This gives all the kept elements.
 
 The flags -k and -m cannot be used together, but as mentioned above -d already gives the relevant list of files.
 
 New files (external) are normally filtered using .acignore files so it would also be possible to get the relevant external files using:
 accurev stat -x
 However I really do not see the point of sending external files to a proof build. The user simply has to add them first, which would then put them in the active elements list.
 
 In conclusion:  the flag -d is what should be used.
 
 
 |  
	| Description |    Please implement proof build support for AccuRev.
The command that proof builds should use for retrieving relevant changes form the users workspace is:
accurev stat -d
This gives all active elements in the workspace and this is normally what the user should send to a proof build. 
 
I would argue that uncommitted changes are not really interesting although they are quite simple to retrieve:
accurev stat -m
This would give all elements that have been modified. 
 
Kept changes however would be interesting to send to a proof build. I think it is not more than reasonable that the user does keep before he/she sends changes to a proof build.
accurev stat -k
This gives all the kept elements.
 
The flags -k and -m cannot be used together, but as mentioned above -d already gives the relevant list of files. 
 
New files (external) are normally filtered using .acignore files so it would also be possible to get the relevant external files using:
accurev stat -x
However I really do not see the point of sending external files to a proof build. The user simply has to add them first, which would then put them in the active elements list.
 
In conclusion:  the flag -d is what should be used.
 | Show » |  
    
        
            
            
 |