Ramz-UK Posted October 31, 2017 Report Share Posted October 31, 2017 I'm evaluating Plastic SCM and trying to work out how best to manage multiple, independent projects that are worked on by the same core team. Note we're mainly working with documents rather than code. I've scoured the web for advice but haven't quite found an answer yet. In a subversion setup, we've managed to do this by having a single repo with subfolders , e.g. 'Project A' and 'Project B', each with the usual branch, trunk and tag folders. It's then easy to view the change activity across the projects because they're all in the same repository. Just open the log and filter as necessary. However, I understand that in Plastic, the usual approach is to establish a repository for each project. Trouble is, all the searches and queries available from the GUI seem to be focused on the current workspace, which is tied to a repository. So, if i wanted to list all the changesets across the two repositories, or see pending changes that the team needs to deal with, it seems I have to go into each repository separately. Basically I'm trying to understand how an admin can get an oversight of all the work that's going on, or be able to search across repositories (or even down into sub-repositories) to find relevant revisions. I've read a bit about xlinks but this isn't quite what i need. Link to comment Share on other sites More sharing options...
psantosl Posted October 31, 2017 Report Share Posted October 31, 2017 While the discussion of whether you should go for a single repo or many is an interesting one (for docs one is fine), the answer to your question is easy: cm find "changesets where date >='2017/10/30' on repositories 'repo0@server:8084','repo1@server1:8084'" Or alternatively type this on a advanced query box in the GUIs find changesets where date >='2017/10/30' on repositories 'codice@codice@cloud','pnunit@codice@cloud' You can query together from not only different reps, but also different servers. Link to comment Share on other sites More sharing options...
Ramz-UK Posted October 31, 2017 Author Report Share Posted October 31, 2017 Ah thanks; after much further searching I've stumbled on a similar question on the forums. Maybe using one repository is the only way to go. Link to comment Share on other sites More sharing options...
psantosl Posted October 31, 2017 Report Share Posted October 31, 2017 Hi, You can use several ones, of course. It is just a matter of scripting "on repositories". Anyway, as the post you mention says, "on repositories" is only an issue when you have hundreds, which I don't know if is your case. Link to comment Share on other sites More sharing options...
Ramz-UK Posted November 1, 2017 Author Report Share Posted November 1, 2017 Hmm, depending on the approach it could be at least tens of repositories, growing over time. Shame that a wildcard doesn't work... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.