History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-1035
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Xiang Shen
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
QuickBuild

file loaded but missing

Created: 08/Sep/11 08:14 PM   Updated: 21/Sep/11 12:34 AM
Component/s: None
Affects Version/s: 3.1.42
Fix Version/s: 3.1.59

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment: Linux


 Description  « Hide
If a file is checked out in a ClearCase view and created a new branch according to the config-spec. The file will be "loaded but missing" in the workspace during the build. For our build, we clean-up the work space using the default pre-execuation action. An example config-spec is like following:

time 08-September-2011.16:07:09 # by QuickBuild
element * CHECKEDOUT
element * .../fares_1.6/LATEST
element * FRE.01.20.001_int_110506_b335 -mkbranch fares_1.6
element * /main/0 -mkbranch fares_1.6
element * /main/LATEST
load /vobs/FR1
end time # by QuickBuil

If we do nothing but simply do the same build again, the file will be loaded and the build will be successful.
Please advise. Thanks.

 All   Comments   Work Log   Change History      Sort Order:
Robin Shen [08/Sep/11 10:48 PM]
In case there are checkout files, the workspace should not be cleaned up. Otherwise, checkout files will be missing, as they have not checked in yet. I guess this is not a problem of QuickBuild.

Xiang Shen [08/Sep/11 11:43 PM]
Sorry, I didn't make it clear. The checkout was not made in the workspace, i.e. in the view we were building. The checkout was made in some other views. We actually expect the previous version of the checkout version appearing in the workspace. Most of time it does. However it seems if the version is zero the file will be 'loaded and missing'.

Don Ross [14/Sep/11 09:48 PM]
I haven't worked with ClearCase in a while, but I think I see a problem in your config-spec.

It looks like the selection of 'main/0' will take precedence over 'main/LATEST'.
This will result in files not modified on the fares_1.6 branch, to be invisible.

Xiang Shen [15/Sep/11 02:43 AM]
Actually fares_1.6 branch is a bug-fix branch, which branching off from a labeled baseline. So even the files not modified on the fares_1.6 branch, they will be visible due to the label. the /main/0 line is for the new elements. We actually can remove the /main/LATEST line. Anyway, thanks.