Planet SCM

Let´s see now how to use Plastic SCM and JIRA using the "task on changeset" working mode: the first steps for setting up the extension would be the same ones as explained on the previous post for the "task on branch" option, the only difference is on the "jiraextension.conf" file, in this case its configuration must be the following one:

<JiraExtensionConfiguration>
 <HttpUrl>http://192.168.1.14:8080</HttpUrl>
 <User>root</User>
 <Password>root</Password>
 <ProjectKey>PRJ</ProjectKey>
 <BranchPrefix>SCM</BranchPrefix>
 <WorkingMode>TaskOnChangeset</WorkingMode>
 <CustomFieldId>customfield_10000</CustomFieldId>
 </JiraExtensionConfiguration>

On the series of posts about Plastic SCM extension I am going to explain how to use Plastic SCM and JIRA for the benefit of users of this task tracking system. Plastic SCM for Atlassian JIRA provides reliable data mapping features that allow data type transformation between both tools; this highly improves your development´s traceability. Let´s see how it works!
First we have to set up the extension, in order to do this a new "Custom Field" named Plastic SCM must be created in Jira, if you want to have a look at further information on how to create a custom field in Jira you can go to our Extension´s Guide.

On the Plastic side, in order to start working you must have copied "jiraextension.dll" on the Plastic SCM client folder, adding the following lines (circled in red, which will indicate that Jira is the extension used), on the client.conf file:


The next step to ensure that the extension is properly set up is creating a "jiraextension.conf" file; on this file we indicate the extension parameters. Here we have to options, the first one is the "Task on branch" option which is used to link one task in Jira with a branch in Plastic, in order to use this option the "jiraextension.conf" file must have the following appearance:

<JiraExtensionConfiguration>
  <HttpUrl>http://192.168.1.14:8080</HttpUrl>
  <User>root</User>
  <Password>root</Password>
  <ProjectKey>PRJ</ProjectKey>
  <BranchPrefix>SCM</BranchPrefix>
  <WorkingMode>TaskOnBranch</WorkingMode>
  <CustomFieldId>customfield_10000</CustomFieldId>
</JiraExtensionConfiguration>

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:

<TracExtensionConfiguration>

  <XmlRpcUrl>
    http://localhost:8080/trac/login/xmlrpc
  </XmlRpcUrl>

  <ShowTicketUrl>
    http://localhost:8080/trac/ticket
  </ShowTicket>

  <User>tester</User>

  <Password>PR</Password>

  <Branchprefix>SCM</Branchprefix>

  <workingmode>TaskOnChangeset</workingmode>

</TracExtensionConfiguration>

As you may have already seen on previous post, Plastic SCM provides with the option of using it integrated with different task tracking tools as it integrates with some of the most extensively used systems in the market, you can have a look at the list of options here.

One of them is TechExcel DevTrack!


On this post I am going to explain with examples, how to use Plastic SCM integrated DevTrack.

First of all we have to know that Plastic SCM not only integrates with this system, but also offers customizable options for the integration.

Why do we provide with different options? So you can use the one that better adjusts to your working pattern: Let´s see the “Task on Branch” working mode on this post.

The first step in order to set up the DevTrack extension on your client machine you have to copy “devtrackextension.dll” on the folder where Plastic SCM client is installed and add the following lines (circled in red) in order to indicate the client to use this extension:



And you would also need to create a file “devtrackextension.conf”, its appearance by default is the following one:

<devtrackextensionconfiguration >
  <dtlinkplusurl>
    http://192.168.1.237/LinkPlusWebService/WSDTIncident.asmx
  </dtlinkplusurl>

  <user>terry-j</user>

  <projectid>daveProject</projectid>

  <systemid>daveSystem</systemid>
  <branchprefix>issue</branchprefix>
  <dtbuginfobrowserurl>
    http://192.168.1.237/scripts/texcel/devtrack/buginfo.dll
  </dtbuginfobrowserurl>
</devtrackextensionconfiguration>

<devtrackextensionconfiguration>
  
  <dtlinkplusurl>
    http://192.168.1.237/LinkPlusWebService/WSDTIncident.asmx
  </dtlinkplusurl>

  <user>terry-j</user>
  <projectid>daveProject</projectid>     
  <systemid>daveSystem</systemid>  
  <branchprefix>issue</branchprefix>
  <dtbuginfobrowserurl>
    http://192.168.1.237/scripts/texcel/devtrack/buginfo.dll
  </dtbuginfobrowserurl>

  <workingmode>
    TaskOnBranch
  </workingmode> 

</devtrackextensionconfiguration>

On the series of posts about Plastic SCM extension with task tracking tool, let´s see how to use Mantis extension!

As on the case of other extensions, Plastic SCM extension with Mantis provides with two different working mode options: "task on branch" and "task on changeset", on this post I will talk about the first of them. To set up the extension in Plastic you must copy the ‘mantisextension.dll’’ library to the folder where you have installed Plastic SCM client and insert the following lines (circled in red) on the "client.conf" file:



You also need to create a "mantisextension.conf" file, which must have the following appearance:

<MantisExtensionConfiguration>
 <MantisBaseUrl>http://localhost:8888</MantisBaseUrl>
 <Branchprefix>SCM</Branchprefix>
 <workingmode>TaskOnBranch</workingmode>
</MantisExtensionConfiguration>