nikhilhs Posted December 4, 2010 Report Share Posted December 4, 2010 As a point of reference, I've been a perforce user, and am trying out plasticscm. Is there a way to create changelists? If I want to add a file to the repository, is there a way to put it into my pending changes instead of immediately adding it? Thank you. -Nick Link to comment Share on other sites More sharing options...
psantosl Posted December 5, 2010 Report Share Posted December 5, 2010 Hi! No, we don't use changelists in Plastic, but we normally use branches to achieve even better results. Take a look at http://codicesoftware.blogspot.com/2010/08/branch-per-task-workflow-explained.html and please let me know what you think. When you add a file it goes directly to the repo (added, now from the GUI we add and checkin on a single step). But, if you prefer to use a "svn like" cycle (or git like) you can just add everything during checking looking for "private" files. Hope it helps. pablo Link to comment Share on other sites More sharing options...
nikhilhs Posted March 25, 2011 Author Report Share Posted March 25, 2011 I apologize for bringing back an old thread, but I'm about to setup plastic scm, and though I'd try to use it "properly" instead of a perforce replacement. I have a couple questions on branch per task 1) If you're working on multiple tasks, wouldn't this leave multiple copies of your code on your hard disk? 2a) How would you use this with TeamCity? Should I only have it build and unit test the mainline and major branches? 2b) Can you do a try-build on a merge? Link to comment Share on other sites More sharing options...
psantosl Posted March 28, 2011 Report Share Posted March 28, 2011 Hi! - If you're working on multiple tasks/branches: normally you'll just switch your workspace to a different branch, so just a single copy (unless you want to use separate workspaces, up to you but not mandatory). - You can build and unit test all branches, whether you do it on a build server or not depends on your setup. You can set an attribute to a branch/task, something like "finished", and then run the tests (have your server polling for branches in "done" status) - "Try-build" on a merge? You mean without checking in? Link to comment Share on other sites More sharing options...
nikhilhs Posted April 6, 2011 Author Report Share Posted April 6, 2011 - If you're working on multiple tasks/branches: normally you'll just switch your workspace to a different branch, so just a single copy (unless you want to use separate workspaces, up to you but not mandatory). Does plastic recognize that the branch has changed, and then only update what's different between the branches? - "Try-build" on a merge? You mean without checking in? Yes, in Perforce and SVN, I'm able to have it attempt a build without checking it in. If the build is successful, then it is checked in. I do this using a TeamCity plugin. Link to comment Share on other sites More sharing options...
psantosl Posted April 7, 2011 Report Share Posted April 7, 2011 > Does plastic recognize that > the branch has changed, and > then only update what's different > between the branches? Absolutely. That's how the update works. > Yes, in Perforce and SVN, > I'm able to have it attempt > a build without checking it in. > If the build is successful, > then it is checked in. I do this > using a TeamCity plugin. Then it means you run the tests on the same workspace you use to perform changes, right? If so, I don't see why you can't do the same in Plastic. pablo Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.