March 2008 - Posts
-
|
Welcome back to the plastic dark side! Today we'll be moving deeper in branching concepts, and trying to explain how labels and branches work. In the previous post I've introduced several important concepts like how selector rules are evaluated...
|
-
|
A few days ago I was re-reading the book "Continuous integration" by Paul Duvall . I find it a really interesting reading, especially when you use agile practices. The book dates from mid 2007, so is quite new, and there's a chapter at the...
|
-
|
I could have titled this blog post "the most complete trip trough workspace selectors ever", which is probably more accurate, but too boring. I will try to explain, step by step, how the key component inside the plastic server works, because...
|
-
|
It's very likely you've drawn a diagram like this one at least once... (and I'll bet probably you do it very often). It is just a tipycal branch diagram, showing the relationships between branches, merges and labels (changesets are not normally...
|
-
|
Plastic SCM handles two different file types: binaries and text files. By default it tries to identify a newly added file using an internal algorithm and a built-in list of known extensions. But sometimes a file that should be binary is identified as...
|
-
|
One of the most important new features in Plastic 2.0 is the distributed system. Today I'm going to talk about the set up I'm using to work from my laptop, disconnected from any network, and how I use the distributed system to synchronize changes...
|
-
|
It's very simple to set up, you only need to create (or edit) a file named 'db.conf' at the server installation directory. Its content must be like the following: <dbconfig> <providername>mysql</providername> <connectionstring>Server...
|
-
|
By default Plastic server logs both activity and errors to a file (loader.log.txt) located at the server's installation directory. Since Plastic uses <a href="http://logging.apache.org/log4net">log4net</a> as logging mechanism...
|
-
|
The introduction of Plastic 2.0 saw the inclusion of MySQL as the server back-end to store the repository. Not only does this open up a number of excellent possibilities and improvements for Plastic, but also makes the Mac OS X server functional. Plastic...
|
|
|
|