- Plastic SCM Community
- → Most Liked Content
Most Liked Content
Posted by diegobowen on 27 January 2012 - 09:23 PM
Posted by mvdzwaan on 08 May 2013 - 07:56 AM
One of our employees deleted several repositories, which are hosted on a plastic 4 server with sql server backend.
I know the actual repository db does not get deleted when this happens, but how can I restore them ?
The administrator guide only talks about reconnecting archived *.fdb repositories.
My first thought was to restore a backup of the 'repositories' database, but I find out now these backups are not ok (only diff files, but the bak got deleted).
Posted by manu on 18 April 2013 - 01:22 PM
What do you think about it?
Reddit discussion here: www.reddit.com/r/programming/comments/1ck8m3/c_semantic_merge_beta_just_launched/
Posted by diegohb on 10 April 2013 - 11:34 PM
I'm trying to understand the code-review process as designed in plastic... Who creates the code-review item, the developer who made the changes requests it by creating it and assigning it to the architect or teammate? This teammate then approves or discards the code-review? What does it mean to discard a code-review?
Thank you and I apologize as i'm only familiar with the concept, never done formal code-reviews but I think it's greatly facilitated with Plastic's integrated functionality for it.
Posted by hampsterx on 25 March 2013 - 10:23 PM
It's pretty painful when hunting through the history of a file.
Currently have two options
- view history
- view history as 2D revision tree
Either way it seems there is no easy way to either see all the changes in one window or have the detail appear in a side window when you click on an changeset. Have to Ctr-D, zoom down to changes, close window, next item..
Sometimes I find myself having to hunt down a change and performing the old "binary chop" to figure out which changeset the change was made in rather than scrolling or simpling clicking my way through a list to quickly pin point it.
PS Plastic still rocks my world after a year and a half of usage, very very happy
Posted by psantosl on 11 March 2013 - 05:59 PM
Manu shared the news a week ago or so, but we're entering "closed beta" of our new merge-tool.
In case you didn't notice yet, you can join the program here: http://plasticscm.com/sm/index.html
The tool is awesome and able to do inside a single file what Plastic merge engine does for files and directories.
Please sign up, give it a try, share it with as many beta-testing volunteers as you can find and check how the future of merging is going to be :-)
Also, do not forget to join the conversation at #mergebegins.
Posted by wvd_vegt on 07 February 2013 - 05:36 PM
We'll to start with all at least your sources, but you also have even more files in the .git directory where git does it's bookkeeping.
Adding a website to git of 140MB with 278 files in 23 folders led to a '.git' directory of 117 MB with 295 files and 181 files. And after the first commit the filecount is up to 325 files in 194 dirctories and 117MB. For each commit the numbers will probably grow (but i'm not sure about that) as will the size.
In PlasticScm it would be 1 file/database + 1 for bookkeeping for all repositories (talking about MSSqlCE, other databases create different number of files). At least easier to backup and with modern SQL Servers more fault tolerant than a file system based system.
Others like CVS and SVN are not much better (and good old sourcesafe also delivers a large amount, my projects with fit into around 80 files in PlasticScm (one per project) would take up 17,820+ files in SourceSafe. Each file no matter how small takes a cluster of diskspace so lots of small files can take up huge amounts of space.
Posted by cidico on 09 January 2013 - 05:20 PM
Ok, I've added it. But I have run out of votes, so other voters must push it.
Btw., I understand that big features like WebUI or Git bisync have bigger marketing potentiality, however these small things are those which makes people like us happy in the end. And happy people talk to friends about their source of happiness. ;-)
I think the same thing! This is why I ended up using Plastic in the first place and I really feel happy at the end of day!
And now I can't see myself using any other tool.
I talk a lot about plastic and people usually ask me if I work for the company who develop the Plastic...
I'm out of votes, but as soon they come back, I'll vote for your request!
Posted by EdDev on 05 January 2013 - 08:21 PM
After reviewing the triggers documentation I could not answer this hot to:
I will like to issue a pre-checkin validation on "release" branches (only) by triggering the CI to build the project and run the Unit Tests.
There seems to be no environment variable that specifies the repo and branch in question.
I will like to perform this using Jenkins.
Posted by cidico on 04 January 2013 - 04:29 PM
Just to add some info here...
I'm trying the 4.2 and I asked about how licensing would work importing a guthub project with more than 15 users...
The answer is: every user that performed a commit counts as a new user in your licensing.
I tried importing NHibernate codebase and I started having problems with licence.
Not sure how you would handle this "problem" (if it is a problem at all...)
Posted by wvd_vegt on 10 September 2012 - 08:06 AM
I have coupple of request for client improvements:
1) In the list of repositories it would be nice if there was an indicator of workspaces behind in updates (so are not working on the tip). I'm currently working on two places and using sync to synchronize, but besides syncing i also need to set the workspace to the most recent version before starting to work on it. It would be handy if i could see what project need this kind of attention without opening branch explorers for all of them.
2) Activate a workspace when double clicking them (maybe optional) but right-clicking all the time is not that easy to do. and bad for RSI.
3) I would like to see a view with full comments like typed in in the changeset view or in a report vreated from it with multi-line comments (not flattend to a single line). I normally use a (numbered) bullet style. So i would like to see a kind of changelog with changeset numbers, labels and full multi-line comments. Just a exportable report would be fine too.
4) Have an option for some basic formatting in the chec-in comment dialog (bulltets or numbers).
5) Get a warning if you try to close the check-in dialog without checking-in something when there are changes. The current check-in button is far from intuiitive and the current close button is where i would expect the check-in button. The close button should perhaps be named cancel.
Wim van der Vegt
Posted by manu on 22 June 2012 - 09:05 AM
I'm glad to announce a new public release! The 18.104.22.1682 (BL302). The last Public release was the 22.214.171.1246 so here it comes the changes between them:
Now when working with xlinks, the check-in is verified in all the
repositories before confirming it in none of them. This way, we avoid
commiting changes to the children repositories when the check-in fails
in the parent repository.
The replica could build wrong changeset trees in destination under high
Improved the directory differences, showing more info: FSProts, RevId,
Type, Name. The File System Protections field is shown only if there are
any file system protection defined for any child. The revision Id field
is shown to differenciate the changes between two directory revisions.
The type indicates whether the child is a dir or a file. The name is the
child name, as usual.
When comparing a branch and there is no content to compare an error was
shown. Now a message is shown as an informative message.
In the Plastic SCM GUI, labels flickered unnecessarily sometimes. Fixed.
Small issue regarding the log added in the previous release.
Posted by Greg Sohl on 21 June 2012 - 07:49 PM
Keep the core in a nice obfuscated set of DLLs. Expose an API on top. Open up the source around the edges.
Just an idea.
Posted by Olaf Kober on 30 May 2012 - 03:06 PM
Posted by Greg Sohl on 27 April 2012 - 03:13 PM
Clearly you and your user base are excited about the 4.1 release. It is huge and very nice. Yet as far as I can see, there is yet to be a blog post, an announcements forum entry or a tweet about its release earlier this week.
Today, there is a release in the downloads area (Version 126.96.36.1998) which is one newer than I downloaded earlier in the week. There are no release notes for this release. The latest release notes are for Version 188.8.131.527. Was 268 not important enough to tell users about?
So here's the question (I said I had one). What am I missing? How are we to learn of your great work?
Whoops, that was two questions.
It's not enough to just write great software folks. Don't forget the other stuff too.
(I'm not just talking to Codice about that everyone. This goes for all our industry!)
BTW, my evaluation of SCCM systems is now complete. Plastic is my recommendation. That is an almost certainty of adoption. My interest in the type of thing I'm asking about above (along with many of the details I've previously written about) is now heightened. As I've said, I'm a fan and pulling for your success.
Posted by cidico on 06 January 2012 - 12:25 PM
Let me give you the good news:
In my company, we've decided to use Plastic SCM instead any other tool.
Until now, we've been using SVN, Source Safe and Plastic. (I know, a chaos....)
You did a wonderful job making the best source control tool made by man kind.. !
The tool made me a passionate user!
Just for curiosity, the final word was given by our interface developer (a.k.a, our designer), which is using SVN and Plastic at the same time in two different projects.
He's using Plastic for 2 months now and he turned to our director and said:
"There's no way we can compare SVN with Plastic. Really, NO WAY! I've been using both and Plastic is muuuuuch better. The merge support, the branch explorer is perfect!"
He doesn't even use 10% of Plastic that I do!
Posted by Guest on 27 November 2007 - 11:35 AM
Posted by dave on 10 December 2010 - 07:50 AM
Find all the details on this blog post announcement:
And in the official Labs page for the project: