Databases
StackOverflow2013
Postsdbo
POTypical best-practice ClearCase project structure
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POTypical best-practice ClearCase project structure
    primarykey
    data
    text
    <p>During a development project, the delivered code can go between different stages different environment before it reaches the production (e.g. Development Environment for testing deployment processes, Internal Testing for QC, Pre-Production and finally production).</p> <p>This development effort produces many candidate release in which a certain release can be nominated to move upwards in the development process until it reaches production, also, there might be some cases where the code deployed on the production might require hot-fixes in parallel to the current internal development lines (i.e. Parallel Development).</p> <p>For a certain UCM project maintained by IBM Rational ClearCase (CC), what is the recommended project structure to be created on "Project Explorer" to accommodate for the following:</p> <ol> <li>The developers should mainly connect and deliver their work on the internal development line (or in CC terminology the development stream).</li> <li>Once the delivered code to this development stream is considered acceptable, the Technical Team Lead (TTL) can create a baseline. This baseline can be later retrieved by the Deployment Engineer to be deployed on the local Development Environment.</li> <li>If this baseline was found acceptable, this baseline can be delivered as a whole to the Internal Testing stream to be deployed for further Quality Control (QC) test.</li> <li>If this baseline was found acceptable, this baseline can be delivered as a whole to the Pre-Production and so forth to the production similar to what was described above.</li> <li>Of course, if any of these baselines were not accepted by its receiving party, it can be rejected, and the receiving party will wait for another baseline to be recommended for their stream.</li> </ol> <p><strong>Note</strong>: The Deployment Engineer will always use a dedicated stream for each environment to get his/her files required to carry out the build/deployment activities.</p> <p>My apologies for everybody here since I understand that answering this can be long, but my question more concentrates on the exact type of streams and/or views that need to be created in "Project Explorer" to suffice the above objectives.</p> <p>I am really trying to come up with the best practice approach for release management using CC and how it can be best used this purpose.</p> <p>I would appreciate your help guys and many thanks to all in advance ...</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMachavity
    1. USyazankhs
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POTypical best-practice ClearCase project structure
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POTypical best-practice ClearCase project structure
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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