3 ms·
I worked at a company that used Perforce. It took 2 weeks to get a branch created. No thank you.
by icedchai 6y ago
I worked at a company that used Perforce. It took 2 weeks to get a branch created. No thank you.
- dijit 6y agoReally not defending perforce, but "branches" are not how you usually work, a branch is basically a fork of the repo, it's almost impossible to reconcile. "Branches", the way we use them in git are more like perforce Shelved CLs.
- icedchai 6y agoYes, I remember using "shelves" a lot. The branch was created for a major refactor of the code base, and the team I was on moved to that branch. Not sure what happened to it. I hated that company and left after a few months.
- koenigdavidmj 6y agoI wonder if it’s a workplace I worked at. We ended up having a bunch of generic branch names (one org had colors, another had star-related things), and when a project was done, they just used that branch for something else.
- Jochim 6y agoIt's worth pointing out that shelved changes don't have any history though, so cross your fingers to make sure you don't accidentally delete/overwrite something. Fwiw the only major issue I've had with branching is the fact its a full fat copy of your source which can end up taking up a load of space depending on how large your application is post build and how many binaries you dump into perforce. They seem to be pushing towards "streams" now, but I've heard they make it easier to create development branches but haven't worked with them to find out.
- jayd16 6y agoNah, shelves have no history. They're more like a patch. P4 streams are the closest to git branches.
- m463 6y agop4 branch <name> (fill out the mapping) p4 integrate -b branch //...
- icedchai 6y agoI wonder what took the "IT department" so long then...
- TheRealDunkirk 6y agoI'm sure that using commercial source control software doesn't HAVE to suck, per se, but the kind of companies that can afford Perforce are usually so bloated and political that you can't avoid that kind of bureaucracy.