Release Notes

Public

8.0.16.3332: Jun 26 2019

New

macOS - Plastic SCM: We have tweaked the column width and order in several tables across the application.

Now, the relevant information should be more accessible. This change affects only Plastic SCM newcomers - if you already use Plastic SCM for macOS, the order and width of the columns in the applications are stored in a preference. If you want to reset this preference, you can execute the following command:

$ rm -rf /Users/your_username/Library/Preferences/com.codicesoftware.*

Here is how it looks:

Workspace Explorer:

Pending Changes:

Changesets:

Branches:

Labels:

Sync view:

New

Windows - Gluon: we've added a Repository column to the "Checkin changes" view, and we've changed the default column order of the Changesets view to make it consistent across all 3 platforms.

New

Jira Extension: We enhanced our Jira issue tracker extension to disable it when it detects that the entered credentials are invalid. This prevents the extension from performing many unauthorized requests. That would lock users out of their accounts, needing to reset them using CAPTCHAS in some organizations.

New

macOS, Linux - Plastic, Gluon: The differences viewer did not show a mark for added/deleted differences. This is how it looks like in macOS:

New

Linux - Plastic SCM: We have tweaked the column width and order in several tables across the application.

This change will only affect new users of the tool. Existing users of the tool have their view configuration stored in a preferences file. To reset your views to the new default values, close the application and delete the preferences file as follows:

$ sudo rm /home/your_username/.plastic4/gtkgui.conf

Here's how it looks:

New

Windows - Plastic, Gluon: On the repositories lists (Repositories view, Cloud view, and repository list dialog), the Refresh button has been moved to the right of the server entry field, to make it clearer that we are refreshing the view based on the content of that field. Same goes for Gluon's "Available Plastic SCM repositories" dialog.

New

Linux - Plastic, Gluon: On the Repository switcher dialog, and the Cloud view in Plastic, the Refresh button has been moved to the right of the server entry field, to make it clearer that we are refreshing the view based on the content of that field.

What? A screenshot? Oh, go on then!

New

All platforms - Plastic, Command line client: Suppose you've switched your workspace to a past changeset. You edit a file. Then you switch to the head. You wouldn't want your edit to be overwritten would you? And if you tried to checkin that file, you definitely wouldn't want that, because you'd be losing all the changes between that past changeset and the head.

Good news - Plastic (and the CLI) handle all this perfectly. However, the error message we displayed if you tried to checkin in this situation wasn't very clear. More good news - we changed the text to make it clearer what the issue is, and more importantly, how you can resolve the issue.

Incidentally, the solution in this case is to temporarily back out your local changes, update the file to the head version, and reapply your changes.

New

macOS, Linux - Plastic, Gluon: Added the "similarity" column to the Pending Changes view as in the Windows counterparts. For locally moved files, you can see the similarity percentage that determined that the file was indeed moved. Remember that you can change this threshold from the Pending Changes options.

Note: by default the Similarity column is between "Date modified" and "repository", to keep consistency with the Windows GUI. Remember that in macOS and Linux you can reorder columns. Pending Changes' column width and positions are reset after adding the Similarity column to ensure it is displayed OK. If you had customized width and positions in this table, you will need to do so again.

New

Windows - Plastic: We changed the default order of the columns in the Shelvesets view to make the most relevant data more prominent.

New users will see this change when the run Plastic for the first time. Existing users can reset all their view settings to the new default values by deleting the preferences file, located here:

%LOCALAPPDATA%\plastic4\guivisualstate.xml

Here's what the new layout looks like:

New

Plastic, Gluon - macOS: We improved diff rendering. Now the colors are stronger and easier to spot the differences.

Check how it looks like in the clear theme, before and after:

And now the dark theme:

Bug

All platforms - The checkin operation sometimes failed due to a duplicate key error while checking in the results of a merge. This happened if path permissions were applied, the merge included at least one moved+changed change and the user chose to keep the sources in a "loaded twice" conflict. Now it's fixed.

Bug

Jenkins plugin: Changes in release 2.21 altered how workspace names are set. This was disruptive for some setups that rely on workspace names to build. It's fixed now.

Bug

macOS, Linux - Plastic: The directory conflict resolution was not working on the merge-to operation. After resolved the conflict, the process all failed with this error: "There are X directory conflict(s) that must be resolved before processing the merge.". Now it's fixed

Bug

Linux - Plastic, Gluon: In some setups, depending on the GTK icon theme enabled in the computer, Plastic GUIs could flood the user with the error message "Icon 'unknown' not present in theme". Apparently, this error is more common after an Operating System upgrade (for example, from one version of Ubuntu to the next one). The error is now protected - if an icon is not present in your GTK theme, Plastic and Gluon will display an empty one instead.

Tip: you can force a GTK icon theme creating a file with name ".gtkrc-2.0" in your $HOME with the following content:

gtk-icon-theme-name="Humanity"

Replace "Humanity" for one of the icon names you have installed at /usr/share/icons. For changes to take effect you must restart Plastic and Gluon after changing .gtkrc-2.0.

Bug

macOS, Linux - Plastic, Gluon: The update operation was failing when the "Update and checkin operations set files as readonly" & "Update operation sets repository timestamp on files" options are both enabled. Now it's fixed.