Release Notes

Public

11.0.16.7348: Aug 25 2022

New

All platforms - PlasticX, GluonX: Delete current workspace could throw non-controlled exceptions

If the user deleted the current workspace in use in the GUI (using the GUI or delete workspace command), further operations with that deleted workspace would throw non-controlled exceptions that could close the program; we fixed this issue.

New

All platforms - PlasticX: Show warning when the user tries to delete changeset involved in a pending merge

We now show a warning message and stop the delete changeset operation if you try to delete a changeset that is the source of a pending merge link. We do it because deleting the merge source puts you in an invalid state where you cannot later check in the merge.

New

All platforms - All client applications: Upgraded interface assembly consumed by issue tracker extensions

We support connecting any client application to an issue tracker to retrieve a user's list of assigned tasks, create a proper branch, or open a task in the issue tracker.

We provide built-in connectors for many issue trackers, such as Jira, Bugzilla, etc.

And we also published an interface so you can write your own connector for a custom issue tracker. This interface is located at issuetrackerinterface.dll file, in the client binaries folder of a Plastic SCM installation.

We've upgraded the issuetrackerinterface.dll and now is compiled in netstandard2.0 (instead of net framework 2.0). This will enable further improvements in the issue tracker subsystem of plastic.

Just in case you have a custom extension compiled in net framework 2.0, you will have two options:

* Upgrade your custom extension and compile it in net framework 4.0 or above

* Use the legacy issuetrackerinterface.dll compiled in net framework 2.0, located at client/extensions directory of a windows installation of Plastic SCM

New

All platforms - PlasticX, GluonX: added warning for an empty check-in comment

We have added an optional warning if you accidentally try to check in with no check-in comment. It looks like this.

.

You can activate it in Preferences -> Comments:

New

Command-line client: 'cm history' shows if the revision was archived.

The 'cm history' command shows whether the revision's data was archived. It adds a new entry for each history entry specifying the data status. The possible values are 'Available' or 'Archived'. The value is empty for the moved/removed history entries.

Default output:

D:08/09/2022 10:26 CS:1   B:/main
DATA:Archived
C: my comment

Long output (--long):

...
Repository spec: repo@server:8087
Data status: Available

Xml output (--xml):

...
<RepositorySpec>repo@server:8087</RepositorySpec>
<DataStatus>Archived</DataStatus>

New

All platforms - PlasticX: Branch filtering on new history view

Further improving the new history view, a dedicated branch filtering popup has been added!

Filtering by one or as many branches as needed is now possible. You can try it out by viewing the history of any file or directory and clicking the 'branch' button near the search bar.

Bug

All platforms - Plastic, PlasticX, Gluon, GluonX: pending changes check status preserved when Incoming changes applied

Previously, pending changes you had unchecked in the Pending Changes view (or Check-in view in Gluon) were being checked when Incoming Changes were viewed or applied. We now preserve your chosen checked state.

Note, that merging can still check previously unchecked items. This is because all items involved in a merge must be checked in together. To help you avoid issues trying to check in a subset of a merge we automatically check all the items involved in the merge.

Bug

All platforms - PlasticX: Create button not refreshed in create branch dialog

The Create button status needs to be refreshed depending on the content of the text fields of the current displayed tab in "Create branch dialog". When an issue tracker was previously configured, two ways of creating a new branch will be available, Manual and From task. The branch name will be mandatory to create a new branch.

Bug

Command-line client: A workspace created with 'cm wk mk' unexpectedly points to the default repository

When creating a workspace there is no need to specify a repository. A default one will be selected instead.

If a non-existent repository is specified when creating a workspace, the command was silently falling back to picking a default repository. This behavior was misleading.

Now, the command just fails and shows an error:

> cm wk mk Project ./Project ProjectTYPO@thecompany@cloud
The specified repository couldn't be found: ProjectTYPO@thecompany@cloud.

> cm wk mk Project ./Project Project@thecompany@cloud
Workspace Project has been correctly created

Bug

Command-line client: The 'cm wk mk' subcommand does not always accept the 'rep:' prefix

Creating a workspace pointing to a repository specified with the 'rep:' prefix failed silently if a server address was not specified.

> cm wk mk Project ./Project rep:project@thecompany@cloud # This works.
> cm wk mk Project ./Project rep:project # This fails silently.
> cm wk mk Project ./Project project # This works even so.

Now the second command works as you would expect.



              
Bug

All platforms - PlasticX: corrected GUI hang when switching during Undo

Attempting to switch to another workspace while a long Undo operation was in progress would cause the GUI to hang.

Now, if an operation is in progress, we inform the user and don't allow the switch until the operation has been completed.

Bug

All platforms - PlasticX: Fixed changeset -1 exception

There was an exception thrown when selecting the Home changeset in the Branch Explorer when there was a diff view in the background.

We fixed this issue

Bug

All platforms - PlasticX: exception thrown if pending merge source changeset not found

If the source changeset of a pending merge link could not be found (probably because it was deleted), an exception was thrown in the Pending changes view. Now, in this case, we display some helpful text in the merge link description, letting you know you will not be able to check in the merge (because the source changeset is missing).

Bug

All platforms - PlasticX: Hide the "add" repository button before org is created

Fixed issue that allowed the user to click 'add' repository button. The 'add' repository button has been hidden when a user is not part of an organization yet.

Bug

Windows - PlasticX, GluonX: allow file rename changing case only

We fixed the validation in the Rename dialog of the Items view to allow renames that only change the case of the name.