Who we are

We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.

If you want to give it a try, download it from here.

We also code SemanticMerge, and the gmaster Git client.

Plastic SCM working with Trac II

Tuesday, August 19, 2008 mdepedro 3 Comments

Now we are going to see how the extension of Plastic SCM and Trac work, in this case using the second working mode: "task on changeset". As on the previous working mode, to use this extension, the first thing you will have to do is copy the ‘tracextension.dll’’ library to Plastic SCM client folder, and add the Trac extension lines on the client.conf.

And then, for the working mode we are explaining on this post: "task on changeset",
the following "tracextension.conf" file must be created:









Now that the extension is set up you can start working with it!

Depending on your company´s structure, either the project manager or a developer would be in charge of creating the tasks on Trac and then assign them to the developer who would work to solve them.

On this example we create two new tasks: task number 6 as shown on the image below, and we had previously added tasks.

Once the tasks have been created and assigned, the developer starts working, he makes his changes after checking out the items he is going to work on (either from Plastic GUI or from one of its IDE plug ins), and when the changes are done and he checkes his code in Plastic will open a window on which the user can include in the “checkin information”, it has the following appearance:

As you can see, on the top of this window the user can include his check in comments and the list of related items is shown.
The checked in tasks are included at the buttom, by selecting the option "Add new issue" the following window will appear:

Just by entering the task number as we include number 6 for the newly created task, the information of the Trac task will be shown.

Once the check in operation is done we can go to the changeset view and just by clicking on the changeset view and selected a changeset, we can see the Trac Extension information on the right, in this case, by selecting the created changeset, we can see on the extension information about its associated task, number 6; but that is not all...as using the "task on changeset" mode, one or more than one tasks can be related with one or more changeset, from this view we can also add new tasks to the changeset.

Now we have associated two tasks with changeset 23 as both of them have been solved on the same check in operation, by clicking on one of the tasks shown on the extension information we can either delete it necessary, or open the task on the Trac IDE, from which information such as the status of the task can be modified and it will be inmediately reflected on Plastic information of the extension as soon as it is refreshed!


  1. Hello, I am looking for an up-to-date example in regards to developing a new, simple, integration with another bugtracking system we use. I modelled the current one after the single file sample found on the forums. However, it results in an error when attempting to select it: The Format of the file 'xxx.dll' is invalid. Is there a code sample available

  2. @jaapjan, can You be more specific? Specifically, what code exactly do you refer to and where do you get the xx.all error?


  3. It is a .NET 2.0 assembly containing four classes residing in the Codice.Client.Extension namespace which are based on BasePlasticExtension, BaseGuiConfiguration, BaseExtensionConfiguration and BaseConfigurationPanel. The assembly is versioned to the same as Plastic, and the error occurs when selecting it from the issue tracking dropdown in the preferences.