I created a snapshot view, all view access properties show the date i created it, date last modified, last accessd etc.. are all the date it should be April 10 BUT the Configurations tab shows a foundation baseline of the next release up May 10
Now I do it difrent; I create a child stream created with the older baseline and then make a snapshot but I would like to know why this snapshot I made 4/10 has a foundation baseline of 5/10
Weird how it shows a foundation baseline that is newer than the date it was created, Maybe CC just knows this is the foudantion of this next release i guess
I did a compare and the files are still the same as the date I created the snapsot is appears but if not I am in trouble...
I am new to CC and devolpement
Thanks in advance
Nothing prevents anybody to rebase the Stream you view is based on, from antoehr view.
Then, when you update your snapshot view, ClearCase will detect the change of configuration of the Stream and proposes to synchronize the config spec of your view with the Stream.
Hence the change of configuration of your view.
Whet you did in that case is correct: create a child Stream based on the right baseline, and work from there.
See "Rebase operation":
A component in Pat’s development stream is configured with baseline BL1.
A rebase operation changes the configuration of the stream to baseline BL2 from the integration stream.
The rebase operation merges files and directories from the integration stream or feature-specific development stream to the development stream.
Related
I want to copy the contents of the integration stream at a certain baseline to a directory outside CC using command line, ie. I want to "export" a baselined version to use a Subversion term. I think the way to do this is to set the view to show the contents of the baseline and perform the copy - or is my thinking wrong for Clearcase? I'm more of a SVN/Git user :)
How can I set a baseline for a snapshot view of an integration stream on command line?
I'm using Clearcase UCM in Windows environment.
If the baseline has been created on that integration stream, you can:
create a child stream (immediately below that integration stream)
rebase it with any of the baselines created on the parent (integration) stream: chose the one you are after
create an UCM snapshot view on that child stream
The content of that snapshot view will be the one of the baseline you wanted to select.
In clear case terminology, what is the difference between integration stream and integration view? Development stream and development view?
More specifically, why "joining an UCM project" involves creating both integration and development views?
If I am a developer, not an integrator, should only one view be enough?
Integration is a term used by convention to designate the first root stream of an UCM project.
Each UCM project has one root stream (and potentially many sub-streams).
The idea is that you will use your integration view as the destination view for deliver coming from sub-streams, effectively "integrated" the work done on said sub-streams on that integration view.
(Froml Stream hierarchy)
Any sub-stream is called by convention a "development" Stream, in that it represents the "configuration" (ie what you need to work) for your current "development effort".
A Stream is a configuration.
An UCM view is a ClearCase view with a config spec done automatically for you following the configuration of the Stream (instead of writing those selection rules manually).
The integration view is a view with the Integration Stream as reference.
A Development view is a view with a development Stream as reference.
The main idea behind this hierarchy of streams is to visualize your merge workflow (ie: once you have finished a work on a branch 'B', where do you need to merge said work?)
merge from a sub-stream to a parent stream: deliver
merge from a parent stream to an immediate child stream: rebase
with ClearCase UCM I can create a baseline in a snapshot view directory. When not all files are up-to-date, which version of a file is included in the baseline?
Example: version 3 of foo.txt is located in the snapshot view directory and there already exists a version 4 of this file. Which version of the file is referenced by the baseline?
Does this depends on the version of ClearCase (I am using ClearCase 7.1)? Do I have to consider something?
Background of the question: for a continuous integration build I want to use a snapshot view. When during creating or updating the snapshot view an other user checks in a file to the same stream this new version may or may not be part of the snapshot. At least I want be to be able to identify which files in my snapshot directory have been used by the build.
About Baselines: A mkbl depends on the selection mechanism (the config spec)
of the local access mechanism (snapshot or dynamic view) providing said selection mechanism.
For each element in the component, the baseline records the version of that element selected by the stream's configuration at the time mkbl is executed.
So the -view parameter is only there to reference the Stream (and its associated config spec):
-vie/w view-tag
Specifies the view from which to create baselines. Baselines are created in the stream that the view is attached to.
For example, if you are working in coyne_dev_view, but want to create a baseline from the configuration specified by the view coyne_integration_view, use -view coyne_integration_view.
This option creates a baseline in the project's integration stream that includes all the checked-in versions contained in coyne_integration_view.
If you do not specify view-tag, the current view is used.
In your case, if your UCM view is supposed to select v4, but is currently selecting v3 because that snapshot view hasn't been updated yet, the baseline should reference v3 (what is currently selected by the view).
So for your background question, best to perform a cleartool update before the mkbl.
Consider a single stream UCM project in ClearCase.
Each developer works in her own snapshot view on the integration stream of the project.
According to the ClearCase documentation when a developer completes an activity, the changes made by the activity become visible to the rest of the developers.
When developer A completes an activity P, are the changes of P immediately visible to developer B and C?
Or do B and C have to refresh their snapshot view in order to actually see the changes?
For a snapshot view (UCM or not), you always have to "cleartool update" your view in order to see the changes committed by your colleagues.
Note: the notion of "completing an activity" might suggest that you are actually using ClearCase with ClearQuest (which will check-in all checked out files associated with an activity, when the related ClearQuest work item is "completed").
This is valid for single-stream UCM projects as well as multi-streams: every time you have several snapshot views on a single stream, you need an update to see your colleagues' commits.
How Can I Revert to Earlier baseline? We have a UCM parallel development(multi-stream) project. Each developer have a snapshot view on Project's Integration stream.
Developers want to see earlier version of the application in their snapshot views so They can debug early version of application to find bugs.
When I want to change an existing snapshot views's foundition baselines, clearcase does not allow me. So How Can I do this?
Since you employ the term Baseline, I will assume you are using UCM.
On a stream, you can not revert backward a baseline.
One possibility is to make a parallel stream, with the desired baseline as foundation: this is the quickest way.
After changes on this new stream, you can make a new rebase to change the foundation baseline, but only if that new rebase is using a more recent baseline from the parent stream (not an older baseline)
For your specific need, I would recommand a non-UCM snapshot view with a simple rule
element * thePreviousBaseline
In order for the developer to have:
his/her current UCM view for development (always set on the LATEST of a branch associated to a stream)
a second snasphot view set to whatever baseline he/she needs.
That second snapshot view is completely not-related to the UCM project and takes advantage of the "full" nature of the baseline (do check that your baseline has been put as "full", not "incremental". If it is "incremental", simply change its type and upgrade it to full)
So, beside your current snapshot UCM view, you can create anywhere you want a non-snasphot view:
cleartool mkview -snap -tag mylogin_myComponentname_csl_snap -vws myPathToViewStorage myPathToRootView
cd myPathToRootView
cleartool edcs
[add the selection rule: element * myOlderBaseline]
[add the load rule at the end: 'load /myVob_Including_MyComponent]
[save, type 'yes']
That is fine for consultation/execution, but if you need to patch (that i is to write, check out and in some files), then I would recommend one UCM stream per baseline to be patched.
That way, the stream clearly represents the patch effort for a given baseline. There should not be too many of them, unless you put into production a new version of your application every five minutes... which is not advisable ;)
So to summarize:
the non-UCM snapshot view is unique and serve for a quick consultation/debug of one older baseline at a time.
for patches (source modification), you create a parallel stream properly named, with the correct foundation baseline, and then a UCM view on it. You can not only debug but also fix some bugs in an activity, the deliver that activity to the main Int stream if that bug need to be retro-fitted on an higher stream.
(note: all bugs do not always need to be delivered: they can be obsolete when compared with the current state of the development)
The way I have solved this problem is by making another Stream, a child Stream of the Integration Stream. The easiest way to create this Stream is to open ClearCase Project Explorer (not Rational ClearCase Explorer) and navigate to the Project and then the Stream in question. Right click on the Integration Stream and select "Create Child Stream..."
Click "Advanced Options" and select a baseline for each component. Do this by selecting the component and then selecting "Change..." and selecting the specific baseline you want to see. You probably want to select "Prompt me to create a View for this Stream." Select "OK".
Any developer can do this. You don't need to be a VOB owner or Project or Stream owner.
Well, it depends. Actually, the answer lies in setting up your config spec to point to the proper files. Your config spec tells your view which versions of elements to look at. But how you do write it depends on your project's approach to baselines. Did you apply a label to mark that baseline? If so, and if you only want to read and not checkout anything new, your config spec can be as simple as
element * <LABELNAME>
If you didn't use labels, you can also set up your config spec to show you files based on dates. It gets more complicated the more rules you need to add to constrain your element choices. If you have more specifics, I can try to elaborate on what rules you might need. Otherwise, I would read the manuals that come with ClearCase. If you view the Extended Help from ClearCase Explorer, and then do "Viewing Rational ClearCase Manuals On-Line" it should give you some links to the Command References. This is where I go whenever I need to modify my config spec in some new way.
Also, note that we only use dynamic views, so I don't know if snapshot views work differently.