Plastic SCM 4.1.10.426 External Release is out!!
Plastic SCM 4.1.10.426 (Athens) is now available!!Get a list of the detailed changes in the release notes. Visit the Plastic SCM download page to install or upgrade your Plastic SCM deployment.
Suggest and vote for new features on the Plastic SCM Forum page and tell us your opinion about Plastic SCM or use the User's Voice channel, as well.
Lots of interesting stuff published this week, for your interest:
Bugs
Visual Studio package: Fixed a "file is being used by other process" exception that could happen (not very often) when saving a file in Visual Studio 2008 (we just could reproduce this bug with this version of the IDE, but could apply to others).Workspaces management: Suppose that you have a workspace pointing to a repository that does not
longer exist. Then if you tried to switch to another branch in another repository Plastic SCM failed (both on CLI and GUI).
It's quite a strange case to remove repositories (properly speaking: disconnect), but this could happen after an evaluation of the product, when you start working normally and you want to reuse a evaluation workspace for production. So, there you are.
Diff command: This operation was not working properly when it was executed from the command line outside of a workspace.
New
FogBugZ Issue Tracker extension: Now the Plastic SCM configuration panel for this extension includes a checkbox that allows enabling or disabling the checkin log feature:
This feature writes automatically a report of the items changed on a recently created changeset after a checkin operation has been performed on the associated task.
By default, this option is selected, therefore logging the checkin operations.
Command line: A new option "--ancestors" has been added to the log command. This is useful to get the reachable parent changesets from the given changeset. This option works the same as the "git rev-list" command, for those that know how Git works. If the “from changeset” is given, it will be used as lower limit for all paths (not only for the “from changeset path”).
This option doesn't show the changesets changes, but the changesets information.
The following are some examples. Suppose that we have the following history in our Plastic SCM repository:
 |
| Plastic SCM repository look like for the cm log --ancestor examples |
Example #1: All parents:
Changeset number: 8
Branch: /main
Owner: Borja
Date: 01/04/2013 18:19:08
Comment:
------------------------------------------------------------
Changeset number: 7
Branch: /main/task001
Owner: Borja
Date: 01/04/2013 18:18:39
Comment:
------------------------------------------------------------
Changeset number: 6
Branch: /main/task001/tests
Owner: Borja
Date: 01/04/2013 18:18:20
Comment:
------------------------------------------------------------
Changeset number: 4
Branch: /main/task002
Owner: Borja
Date: 01/04/2013 18:17:14
Comment:
------------------------------------------------------------
Changeset number: 3
Branch: /main/task001
Owner: Borja
Date: 01/04/2013 18:15:13
Comment:
------------------------------------------------------------
Changeset number: 2
Branch: /main
Owner: Borja
Date: 01/04/2013 18:14:31
Comment:
------------------------------------------------------------
Changeset number: 0
Branch: /main
Owner: all
Date: 01/04/2013 18:12:55
Comment: Root dir
------------------------------------------------------------
Example #2:
Changeset number: 8
Branch: /main
Owner: Borja
Date: 01/04/2013 18:19:08
Comment:
------------------------------------------------------------
Changeset number: 7
Branch: /main/task001
Owner: Borja
Date: 01/04/2013 18:18:39
Comment:
------------------------------------------------------------
Changeset number: 6
Branch: /main/task001/tests
Owner: Borja
Date: 01/04/2013 18:18:20
Comment:
------------------------------------------------------------
Changeset number: 4
Branch: /main/task002
Owner: Borja
Date: 01/04/2013 18:17:14
Comment:
------------------------------------------------------------
Example #3: All parents with a lower limit on a different path
Changeset number: 8
Branch: /main
Owner: Borja
Date: 01/04/2013 18:19:08
Comment:
------------------------------------------------------------
Changeset number: 7
Branch: /main/task001
Owner: Borja
Date: 01/04/2013 18:18:39
Comment:
------------------------------------------------------------
Changeset number: 6
Branch: /main/task001/tests
Owner: Borja
Date: 01/04/2013 18:18:20
Comment:
------------------------------------------------------------
Example #4: Custom format
7 (/main/task001)
6 (/main/task001/tests)
3 (/main/task001)
2 (/main)
0 (/main)
Enjoy!
0 comentarios: