It's all about the answers!

Ask a question

Too many change sets


Curtis d'Entremont (1.3k3) | asked Jul 05 '07, 2:55 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
I am working on a new development set up for the jazz.net community site using TeamConcert, so that we can get source control, history, etc.

The system is too big to replicate for testing locally.. you need an HTTP server, J2EE server, DB2, LDAP server, Export verifications server, SMTP server, etc. So we have a shared testing server with everything set up.

I have one stream where you deliver changes to production servers, and one workspace where you deliver changes for testing, because the test environment is shared. A continous build automatically sends any delivered changes to the corresponding web server.

The problem:

During development, I deliver lots of little change sets to the testing server, e.g. tweaking a CSS file until it looks just right. When I switch flow target to the production stream to put the changes in production, it shows me every little outgoing change set I sent for testing, instead of showing one big change set containing the differences between my workspace and the production stream. It's too messy.. I don't want a complete history of my testing in the production stream.

Is there some way I can merge all these little change sets into one big one, or somehow get it to just have one change set? Thanks in advance

One answer



permanent link
Jean-Michel Lemieux (2.5k11) | answered Jul 17 '07, 4:28 p.m.
JAZZ DEVELOPER
We don't currently have a way of collapsing the changes into one
change-set. However, we will be providing an option in the Pending
Changes view to show only the changed files instead of the history of
change-sets. This is basically like showing the overview of the files
that have been modified by the mentioned change-sets, where each file
could of been modified multiple times.

Some background information about those "little change-sets". Jazz SCM
is no different than other SCM systems, take Subversion for example.
Everytime you commit you'll create a configuration id for the commit,
this includes every little change you make. Jazz doesn't the same thing
but we currently focus on showing the history of the changes when we
compare repository workspaces and stream instead of the net effect.

Jean-Michel

curtispd wrote:
I am working on a new development set up for the jazz.net community
site using TeamConcert, so that we can get source control, history,
etc.

The system is too big to replicate for testing locally.. you need an
HTTP server, J2EE server, DB2, LDAP server, Export verifications
server, SMTP server, etc. So we have a shared testing server with
everything set up.

I have one stream where you deliver changes to production servers, and
one workspace where you deliver changes for testing, because the test
environment is shared. A continous build automatically sends any
delivered changes to the corresponding web server.

The problem:

During development, I deliver lots of little change sets to the
testing server, e.g. tweaking a CSS file until it looks just right.
When I switch flow target to the production stream to put the changes
in production, it shows me every little outgoing change set I sent for
testing, instead of showing one big change set containing the
differences between my workspace and the production stream. It's too
messy.. I don't want a complete history of my testing in the
production stream.

Is there some way I can merge all these little change sets into one
big one, or somehow get it to just have one change set? Thanks in
advance

Your answer


Register or to post your answer.