Jazz SCM equivalent to CVS modules
Hi there
Using CVS over the years I've noticed that my team and others, often use
a CVS 'module' definition to work with a subset of a given CVS project.
For example, my team does porting work for a large existing product. We
load the entire product source tree (> 1.2Gig) into CVS. Throughout the
development project, we need to work with a much smaller (fixed) subset
(say only 300MB) of that tree. We define a CVS 'module' that includes
only the portion of the source that needs to be worked on so that
developers need not checkout gigabytes of data that they mostly never use.
After that long-winded description ...
1) is there any equivalent feature in the Jazz SCM
and if not
2) do teams using the Jazz SCM ever face this need see a 'subset' view
of their code ?
Cheers
Dave
Using CVS over the years I've noticed that my team and others, often use
a CVS 'module' definition to work with a subset of a given CVS project.
For example, my team does porting work for a large existing product. We
load the entire product source tree (> 1.2Gig) into CVS. Throughout the
development project, we need to work with a much smaller (fixed) subset
(say only 300MB) of that tree. We define a CVS 'module' that includes
only the portion of the source that needs to be worked on so that
developers need not checkout gigabytes of data that they mostly never use.
After that long-winded description ...
1) is there any equivalent feature in the Jazz SCM
and if not
2) do teams using the Jazz SCM ever face this need see a 'subset' view
of their code ?
Cheers
Dave
4 answers
You would use a Jazz SCM "component" to partition your source tree into
separate pieces.
Cheers,
Geoff (ClearCase Connector team)
David Ward wrote:
separate pieces.
Cheers,
Geoff (ClearCase Connector team)
David Ward wrote:
Hi there
Using CVS over the years I've noticed that my team and others, often use
a CVS 'module' definition to work with a subset of a given CVS project.
For example, my team does porting work for a large existing product. We
load the entire product source tree (> 1.2Gig) into CVS. Throughout the
development project, we need to work with a much smaller (fixed) subset
(say only 300MB) of that tree. We define a CVS 'module' that includes
only the portion of the source that needs to be worked on so that
developers need not checkout gigabytes of data that they mostly never use.
After that long-winded description ...
1) is there any equivalent feature in the Jazz SCM
and if not
2) do teams using the Jazz SCM ever face this need see a 'subset' view
of their code ?
As Geoff said, components are the first level of decomposition, but in
reality many projects already have a directory structure that they don't
want to split or refactor. There are a couple of things happening to
support finer grain loading that are being discussed in
https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=42933
At a minimum we will support loading at any folder level for 1.0, a P2
is to remember this as you can with CVS modules or SVN externals.
Hope this helps.
Jean-Michel
Jazz Source Control Team
David Ward wrote:
reality many projects already have a directory structure that they don't
want to split or refactor. There are a couple of things happening to
support finer grain loading that are being discussed in
https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=42933
At a minimum we will support loading at any folder level for 1.0, a P2
is to remember this as you can with CVS modules or SVN externals.
Hope this helps.
Jean-Michel
Jazz Source Control Team
David Ward wrote:
Hi there
Using CVS over the years I've noticed that my team and others, often use
a CVS 'module' definition to work with a subset of a given CVS project.
For example, my team does porting work for a large existing product. We
load the entire product source tree (> 1.2Gig) into CVS. Throughout the
development project, we need to work with a much smaller (fixed) subset
(say only 300MB) of that tree. We define a CVS 'module' that includes
only the portion of the source that needs to be worked on so that
developers need not checkout gigabytes of data that they mostly never use.
After that long-winded description ...
1) is there any equivalent feature in the Jazz SCM
and if not
2) do teams using the Jazz SCM ever face this need see a 'subset' view
of their code ?
Cheers
Dave
Thanks to everyone who replied.
Componentization seems the right thing to do and I'm looking at that now.
The 1.0 support to select root folders is interesting ; is this likely
to surface in a milestone release before GA ?
Jean-Michel Lemieux wrote:
Componentization seems the right thing to do and I'm looking at that now.
The 1.0 support to select root folders is interesting ; is this likely
to surface in a milestone release before GA ?
Jean-Michel Lemieux wrote:
As Geoff said, components are the first level of decomposition, but in
reality many projects already have a directory structure that they don't
want to split or refactor. There are a couple of things happening to
support finer grain loading that are being discussed in
https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=42933
At a minimum we will support loading at any folder level for 1.0, a P2
is to remember this as you can with CVS modules or SVN externals.
Hope this helps.
Jean-Michel
Jazz Source Control Team
David Ward wrote:
Hi there
Using CVS over the years I've noticed that my team and others, often
use a CVS 'module' definition to work with a subset of a given CVS
project.
For example, my team does porting work for a large existing product.
We load the entire product source tree (> 1.2Gig) into CVS.
Throughout the development project, we need to work with a much
smaller (fixed) subset (say only 300MB) of that tree. We define a CVS
'module' that includes only the portion of the source that needs to be
worked on so that developers need not checkout gigabytes of data that
they mostly never use.
After that long-winded description ...
1) is there any equivalent feature in the Jazz SCM
and if not
2) do teams using the Jazz SCM ever face this need see a 'subset' view
of their code ?
Cheers
Dave