Release Notes
Public
8.0.16.3347: Jul 02 2019
New
macOS, Linux: Plastic, Gluon: Added actions to semantic diffs buttons. Now changed (C) and moved (M) buttons allow to diff changed code and go to moved code.
This is how it looks like in macOS:
And Gtk:
New
Jenkins plugin: We added support for job parameters in Pipeline checkout selectors.
New
Jenkins plugin: The cm path setting in the global plugin settings has now a validation action.
New
DevOps: JiraPlug: The JiraPlug will now be able to connect to Jira Cloud servers using Basic Authentication with an API token instead of user's password.
The related configuration field in JiraPlug will now be more descriptive about this fact:
To create an API token for the user configured with your JiraPlug instance, go to Jira API Tokens page and paste the token in the Password / API Token field of JiraPlug configuration.
New
DevOps: JiraPlug: Improved check connection on plug startup. If the entered credentials are not valid, a proper error message will be logged inside devops/logs folder of your plastic server instance, and the JiraPlug execution will be gracefully stopped. Maybe you are using a Jira Cloud Server and you need to configure an API token for the user configured with JiraPlug to perform queries and status updates.
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
Jenkins plugin: Pipeline checkouts always checked the "use multiple workspaces" option. Fixed!
Bug
Windows - Gluon: Sometimes the switcher window appeared behind the Gluon window where you clicked "Switch workspace". We modified how we display the switcher window to ensure it is displayed in the right place, i.e. over the Gluon workspace window.
Bug
macOS, Linux - Plastic, Gluon: the application could come into an unresponsive state for a few minutes when trying to download the Plastic global configuration from an inaccessible server. This was because of a thread interlocking issue. One easy way to reproduce this problem was as follows: open Plastic SCM in a workspace whose repository server is not available (maybe because it is in another network), and try to change to another workspace. The second Plastic SCM window won't be able to load the Workspace Explorer view until the first one finishes trying to download the inaccessible global configuration. This is now fixed!