Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><a href="https://stackoverflow.com/questions/346788/difference-between-baseline-and-benchmark-in-performance-of-an-application/346835#346835">About Baselines</a>: A <a href="http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m0/index.jsp?topic=/com.ibm.rational.clearcase.cc_ref.doc/topics/ct_mkbl.htm" rel="nofollow noreferrer"><code>mkbl</code></a> depends on the selection mechanism (the config spec) of the local access mechanism (snapshot or dynamic view) providing said selection mechanism.</p> <blockquote> <p>For each element in the component, the baseline records the version of that element selected by the stream's configuration at the time <code>mkbl</code> is executed.</p> </blockquote> <p>So the <code>-view</code> parameter is only there to reference the Stream (and its associated config spec):</p> <pre><code>-vie/w view-tag </code></pre> <blockquote> <p>Specifies the view from which to create baselines. Baselines are created in the stream that the view is attached to.</p> <p>For example, if you are working in <code>coyne_dev_view</code>, but want to create a baseline from the configuration specified by the view <code>coyne_integration_view</code>, use <code>-view coyne_integration_view</code>.<br> This option creates a baseline in the project's integration stream that includes all the checked-in versions contained in <code>coyne_integration_view</code>.<br> If you do not specify view-tag, the current view is used.</p> </blockquote> <p>In your case, if your UCM view is supposed to select <code>v4</code>, but is currently selecting <code>v3</code> because that snapshot view hasn't been updated yet, the baseline should reference <code>v3</code> (what is currently selected by the view).</p> <p>So for your background question, best to perform a <code>cleartool update</code> before the <code>mkbl</code>.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload