It's all about the answers!

Ask a question

Need workspace that behaves like a CC dynamic view of LATEST


Glenn Herbert (12667) | asked Sep 16 '11, 1:30 p.m.
We are in the process of moving all our source code into RTC but not using the build engine (at this point in time). Our current home grown build process runs on multiple UNIX flavors as well as Windows. The nightly build script currently copies sources within a ClearCase dynamic view, which is configured to always reflect the LATEST, from the central view server to the local machine, then builds against that local copy of source (in reality there are 13 separate view copies that occur for the 13 sub-components built via this home grown script). In this manner we can test build submitted changes before attempting milestone builds; basically a sanity build to catch coding errors.

I'm trying to understand how to go about recreating this concept within RTC and am at a loss as to how to configure a workspace to always reflect the LATEST version of sources as one can do within a CC dynamic view by updating the config spec file. I've not seen any forum topics describing this exact situation.

I am interested in methodologies for obtaining the LATEST version of sources from a workspace using the scm command line utility on each build machine. It seems as if I would have to run an scm accept operation on the workspace prior to the scm load operation, but that seems awfully inefficient, possibly time consuming and possibly failing due to merge issues (although maybe this is more a delivery issue).

An additional factor to consider is that the same build process will run at approximately the same time each night on each of the build machines (5 unix/linux + windows). Will running scm accept multiple times against the same workspace cause issues or do I have to limit it to be run once?

Any ideas or suggestions on how to accomplish this would be greatly appreciated and help solve one aspect of this switch over. Thanks in advance!

4 answers



permanent link
Geoffrey Clemm (30.1k33035) | answered Sep 16 '11, 10:15 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
"LATEST" in ClearCase, means "branch/LATEST", for some "branch".
In RTC, a branch is called a "stream". When you are requesting an RTC
build against an RTC stream, you would just set the "Accept latest
changes before loading" option on the Jazz Source Control tab of your
build definition (this is "on" by default). This gives you "LATEST"
behavior for that build.

Cheers,
Geoff

On 9/16/2011 3:38 PM, herbertg wrote:
We are in the process of moving all our source code into RTC but
not using the build engine (at this
point in time). Our current home grown build process runs on multiple
UNIX flavors as well as Windows. The nightly build script currently
copies sources within a ClearCase dynamic view, which is configured
to always reflect the LATEST, from the central view server to the
local machine, then builds against that local copy of source (in
reality there are 13 separate view copies that occur for the 13
sub-components built via this home grown script). In this manner we
can test build submitted changes before attempting milestone builds;
basically a sanity build to catch coding errors.

I'm trying to understand how to go about recreating this concept
within RTC and am at a loss as to how to configure a workspace to
always reflect the LATEST version of sources as one can do within a
CC dynamic view by updating the config spec file. I've not seen any
forum topics describing this exact situation.

I am interested in methodologies for obtaining the LATEST version of
sources from a workspace using the scm
command line utility on each build machine. It seems as if I would
have to run an scm accept operation on
the workspace prior to the scm load
operation, but that seems awfully inefficient, possibly time
consuming and possibly failing due to merge issues (although maybe
this is more a delivery issue).

An additional factor to consider is that the same build process will
run at approximately the same time each night on each of the build
machines (5 unix/linux + windows). Will running scm
accept
multiple times against the same workspace cause
issues or do I have to limit it to be run once?

Any ideas or suggestions on how to accomplish this would be greatly
appreciated and help solve one aspect of this switch over. Thanks in
advance!

permanent link
Glenn Herbert (12667) | answered Sep 19 '11, 3:54 p.m.
All well and good, however this utilizes the build engine, which we are not contemplating for use at this stage. It appears that my only recourse is to run an scm accept on each stream workspace from which I need to obtain source code. Not the greatest solution (IMO) but one I might have to live with since RTC doesn't appear to support an automatic LATEST concept natively.

"LATEST" in ClearCase, means "branch/LATEST", for some "branch".
In RTC, a branch is called a "stream". When you are requesting an RTC
build against an RTC stream, you would just set the "Accept latest
changes before loading" option on the Jazz Source Control tab of your
build definition (this is "on" by default). This gives you "LATEST"
behavior for that build.

Cheers,
Geoff

permanent link
Tim Mok (6.6k38) | answered Sep 19 '11, 4:59 p.m.
JAZZ DEVELOPER
Ensure that you are performing component replaces on the workspace what you want to have the latest from the stream. If there are conflicts that require manual resolution, the 'scm accept' will fail. A component replace gives you the exact configuration of the component that is in the stream.

This work flow is normal and consistent with other version control systems. You have control over what goes into the build.

permanent link
Geoffrey Clemm (30.1k33035) | answered Sep 19 '11, 7:44 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
In my experience, the benefits of having a quick and accurate overview
of what has changed in your branch/stream greatly outweigh the cost of a
single click (on the Accept-All operation in the Pending Changes view).

Cheers,
Geoff

On 9/19/2011 4:53 PM, herbertg wrote:
All well and good, however this utilizes the build engine, which we
are not contemplating for use at this stage. It appears that my only
recourse is to run an scm accept on each
stream workspace from which I need to obtain source code. Not the
greatest solution (IMO) but one I might have to live with since RTC
doesn't appear to support an automatic LATEST concept natively.

gmclemmwrote:
"LATEST" in ClearCase, means "branch/LATEST", for
some "branch".
In RTC, a branch is called a "stream". When you are
requesting an RTC
build against an RTC stream, you would just set the "Accept
latest
changes before loading" option on the Jazz Source Control tab
of your
build definition (this is "on" by default). This gives
you "LATEST"
behavior for that build.

Cheers,
Geoff

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.