How to prepare a Changeset without changing the Source?
It seems that a Source control change set can be prepared If and only if I am doing some changes in the source file.
I want to include a files into change set which is not changed in the Local repository. Is it possible?
This will be useful in the following scenario.
For a development, two different change sets will be delivered to testing team. Which ever is approved first, that change set will be delivered to client. But, to make sure that some base files are present in both the change set, I want to include a file in both the change set even there is no modification in the source file.
Thanks in advance.
2 answers
as far as I know a change set can actually only contain files that have actually changed.
How this is supposed to work with RTC: The fix is against some baseline/build/release. The test engineers should have repository workspaces loaded with the baseline the changes are supposed to go in. Then they can accept the changes into their repository workspace which will contain all the other files needed.
Comments
Ralph,
I understood the RTC flow and there is no problem regarding the testers since they are using Local repositories.
But we are depending on Change Set when delivering developments to clients.
So, its not sure which change set the testers will complete first. for example, if change set 2 got tested first and the same was delivered to the client without a dependency file which we included in change set 1, in such case, testers local repo will have this file but the same will be missed in client side. it will create problem,
So rephrasing my question, Is it possible to add a same file in more than one change set?
Not that I would be aware without changing the file.
Ralph,
Today we faced another scenario. That a Developer deleted his change set from the Work item. But we are unable to recreate the same change set with same files. Because, during deliver RTC repository is updated with that files already. Hence no pending changes is showing to prepare the change set already.
How to handle this kind of situations?
You can search for change sets by various criteria and add them back to the work item.
In general for all I know, the RTC SCM today is optimized to work with streams, baselines and snapshots. It is not file based and there are, as far as I can tell no file versions available.
You can, based on a baseline, create repository workspaces and you can accept single changesets from work items into a repository workspace (as long as there are no gaps).
A change set does not represent a file but the change to the file. You can, as far as I can tell load a files that are represented by a change set to a local location. However, finally RTC is only interested in the difference between the local workspace and the stream it points to.
I am not aware of another usage model. However there are people that are more capable in Jazz SCM then I am and might be able to correct me.
Comments
hi,
What I am talking about is nothing related with Internal office / Local repository synchronization. We can even deliver the change set one after another to ensure the dependencies.
We have developed some plug-in which will generate Release Pack which will be delivered to the client. This process is totally depends on CHANGE SETS. So, I want to ensure that some important files will be present in all the change Set of a work item. So, which ever change set is processed and delivered first, my files will present there.
I am not sure what "internal office / Local repository synchronization" is referring to.
But in any case, how does "which ever change set is processed and delivered first, my files will present there" differ from the definition of work item 71191, which is "dependent change sets should always be delivered or accepted when A is delivered or accepted".