How to get the files in a particular Changeset?
Moderator: SourceGear
How to get the files in a particular Changeset?
I would like to be able to Show Version History and just get the files in that changeset, not the whole tree.
If the get was available when viewing the details (just diff at the moment) that would be OK too, provided I can multi-select all the items.
I tried going the Show Item History route, but it does not group the changes into changesets (displaying the changeset at the current folder level would be useful) and you can only select one file at a time.
A particular team member of ours needs to do this frequently and has offered to buy me lunch if we can get this feature implemented
If the get was available when viewing the details (just diff at the moment) that would be OK too, provided I can multi-select all the items.
I tried going the Show Item History route, but it does not group the changes into changesets (displaying the changeset at the current folder level would be useful) and you can only select one file at a time.
A particular team member of ours needs to do this frequently and has offered to buy me lunch if we can get this feature implemented
I wonder why there is no reply? Is it too trivial?
I can't see a way to do this so I would like to submit this as a feature request.
Its particular useful for merging changes into a 'released' branch of our code when the branch is known to have no other changes. It would be much faster than the Merge Branches wizard.
Its also useful on our build machine where we may not have the working directory set to the source code location. Thus we need to explicitly get the files.
Of course you can get each indvidual file, but that requires you selecting each file in each folder and the correct version of that file. Rather than a simple select the version and get it to a target.
Our customers have a slow upgrade cycle and so we maintain many past releases and also have other customers on premium support who receive patches, which are thankfully in a single branch for all such customers on a particular release
All these releases means that speeding up the merging of files and applying changes to the build is very important for us.
And what should the target be? It needs to be at the same 'level' as the version you are viewing. In this kind of process we would be at the Product level and thus would select a target directory that is also at the product level, though in a branch.
I can't see a way to do this so I would like to submit this as a feature request.
Its particular useful for merging changes into a 'released' branch of our code when the branch is known to have no other changes. It would be much faster than the Merge Branches wizard.
Its also useful on our build machine where we may not have the working directory set to the source code location. Thus we need to explicitly get the files.
Of course you can get each indvidual file, but that requires you selecting each file in each folder and the correct version of that file. Rather than a simple select the version and get it to a target.
Our customers have a slow upgrade cycle and so we maintain many past releases and also have other customers on premium support who receive patches, which are thankfully in a single branch for all such customers on a particular release
All these releases means that speeding up the merging of files and applying changes to the build is very important for us.
And what should the target be? It needs to be at the same 'level' as the version you are viewing. In this kind of process we would be at the Product level and thus would select a target directory that is also at the product level, though in a branch.
Rob,
It would be a multi-step operation. First, use VersionHistory to get the transactions (look for the TxID) for the folder. Then use ProcessCommandTxDetail() to get the transaction details. In the TxInfo object, all of the changes are in the items collection. Check the CommandLineClient.cs and XmlOutput.cs files that are included in the API zip for examples of working with these objects.
It would be a multi-step operation. First, use VersionHistory to get the transactions (look for the TxID) for the folder. Then use ProcessCommandTxDetail() to get the transaction details. In the TxInfo object, all of the changes are in the items collection. Check the CommandLineClient.cs and XmlOutput.cs files that are included in the API zip for examples of working with these objects.
Subscribe to the Fortress/Vault blog
Rob,
Sorry, I just assumed you were talking about the API (since we've talked a lot about the API in the past). I agree that right now, we have Diff as the only menu option in our Changeset Details dialog. It would be helpful to add get to that context menu.
As an (admittedly lame) workaround, the web client's Transaction Details page (you can get a link to it from the File History web page) does have a Get link for the version of the files that were checked in.
Sorry, I just assumed you were talking about the API (since we've talked a lot about the API in the past). I agree that right now, we have Diff as the only menu option in our Changeset Details dialog. It would be helpful to add get to that context menu.
As an (admittedly lame) workaround, the web client's Transaction Details page (you can get a link to it from the File History web page) does have a Get link for the version of the files that were checked in.
Subscribe to the Fortress/Vault blog
If you're on the TransactionDetails.aspx page, clicking on the version number should get that version of the file.
Subscribe to the Fortress/Vault blog
There should be a view details link for every row (excluding labels) in the VaultHistory.aspx page.
Subscribe to the Fortress/Vault blog