|
Sort Order:
I'm planning to switch to "setcs -current" - I actually had a good chunk of the I'm aiming at a 1.1 release once we've accumulated enough misc bug fixes I've no access to CC from home so i cannot really verify this. But the element * CHECKEDOUT and this is definitely not what i would want). Regarding setcs -current: it would then probably make sense to also add cleartool setcs -overwrite -current Code changed in hudson Version 1.1 has broken ClearCase access for me. I believe the -overwrite arg is unrecognized by my version cleartool. Here's the error message: I'm using an older version of the ClearCase client (on Linux): Any suggestions for fixes on my side? Thanks... love the plugin! Created Issue 5212 (Clearcase UCM) Using 1.1.1, this doesn't seem fixed to me, it is still running cleartool update instead of the cleartool setcs command and therefore my view doesn't get new config specs. Is there anything else to check besides checking the 'Use update' checkbox? There seem to be a few areas of weirdness with the UCM snapshot views. We're calling setcs with a config spec (with the config spec just being what we got from running catcs on the view) when the load rules change - which, if I remember correctly, we're doing because that's the only way to remove defunct load rules. Then we run cleartool updates for each load rule - I'm not sure why we do that. It might be a legacy thing - can you think of a reason to do that rather than the setcs -current? Here is the list of use cases that it should cover
In any case this is not optimal because to cover all use cases we need 2 updates : one for updating config spec from server, one other if we want to include new load rules, although this could be optimized if we can compute the difference between the current load rules, and the set that generated the previous config spec for the view. After hitting this problem again, I came up with a patch that uses setcs every time. In my case the previous code were still calling cleartool update on every load rule, because the required config spec update was not due to the change of load rules. This code triggers a full update of the view with correctly updated config spec, the logic is also way simpler than before. Code changed in hudson Code changed in hudson Code changed in hudson
Code changed in hudson
Code changed in hudson
|
||||||||||||||||||||||||||||||||||||||||||
Improvement
Closed
Major
Use 'cleartool setcs -current' instead of 'cleartool update'
Added myself to cc