Squore 19.0 was released on April 30th 2019.

This release brings REST API on project data, the possibility to apply a model on all project versions, a new home page, support of multi dashboards and management of findings from Source Code.

Read on to take a visual tour of the new features of Squore 19.0!

New Features

New Home Page

The home page is now refurbished.

A timeline presents chronological information related to projects builds, pinned artefacts and comments added by other users.

The timeline provides filters to allow users to focus on particular activitiy or project. It also provides a period selector which allows users to display a particular period of time.

The previous blocks "last projects visited", "pinned artefacts", "tasks" and "documentation" are still accessible.

The Squore REST API

Squore now includes a full REST API which you can use to retrieve projects, versions, artefacts, metrics and user management.

You can browse the API documentation directly from your Squore Server (? > API Documentation). To help you get started with the API, we have written an API Quick Start Guide.

Reapply Model

Now, it is possible to apply a new model (or updated one) using the project data in database, without executing repository connectors and data providers!

Go to the project page and click on "Reapply model":

Then select a wizard to apply, and choose between:

• Update this projet
• Duplicate into new project

Finally, click on "Run" to update or create the projet with an up-to-date model.

Cloning A Project Version

To branch a project version, this option will help you to keep all data of a build version (build option, relaxation states, ...).

Go to the "My projects" page, click "Manage" on the desired project, in the "Versions" tab a new "Clone" column is available:

Then fill the following form to create a new project using this version as the first version of the new project:

Multi-dashboards & Roles Permission

To simplify the role management, we removed the "view as" popup that filtered elements visible only for a specific project role. 

Roles/team continue to be defined as before but if you are "developer" and "project manager", you can now view all items that you have the right to see at the same time. 

For example:

• action items without "roles" permission
• action items with role permission "developer" or "project manager"
• not the action items with role permission "tester"

It is available for all main elements:

• Dashboards
• Action items
• Highlights
• Exports
• Reports

In most cases, it doesn't change the page design, except for dashboards. It allows you to have access to several dashboards for a same artefact/model/group, so it is possible to switch from one dashboard to another just above the charts in one click!

Of course it impacts also the dashboard editor with a more powerful permission management, including a new "groups" permission that limit the visibility of a dashboard to one or more specific user groups.

Manage Findings From Source Code

Users are now able to create, relax or close findings manually, directly through the "source code" user interface.

• To create a finding, click on the line number placed on the gutter to display the dedicated form (see below). User has to select the finding rule and fill a description.
  
  

• To relax a finding, click on the warning icon to display the dedicated form (see below). If several findings are positioned at a code line, user has to select the desired one among them.
  User has to select the relaxation status and add a comment.
• In addition, the form allows users to remove findings if added manually. 
  
  
  
  

Indicators & Information Support For TextValues Charts

On the 18.1 version, only measures were allowed on the "TextValues" chart, now, it is possible to add textual information and indicators.

"View Source" Automatic Link

To return to the source code or to follow the original URL of a ticket for example, it was necessary to add the "SourceCode" chart on the dashboard.

Now, it is a simple link added automatically on the top right corner of the dashboard tab:

Note that the "SourceCode" chart is now deprecated.

New Scripting Language Groovy

A new language is now available to write scripts for data providers, repository connectors, exports and such : Groovy.

Why Groovy :

• is a JVM based language
• is developer friendly (easy to read/write)
• can be embedded in Squore and doesn't have system dependencies

A simple example of the configuration to execute a groovy script (form.xml):

<exec-phase id="add-data">
    <exec name="java">
        <arg value="${javaClasspath(groovy)}"/>
        <arg value="groovy.lang.GroovyShell" />
        <arg value="${getToolConfigDir(jsonToCSVFile.groovy)}" />
         ...
    </exec>
</exec-phase>

Export Scripts Improvements

• Add ${token} parameter to call REST Api.
• All scripts provided by Squore are now written in Groovy instead of nashorn (javascript for Java).

New "Hide Input Tags" Feature

Use the new "displayIf" element on the form.xml files to define conditions on the tagged field to make it visible in the web UI.

<tag type="text" key="config_file"/>
<tag type="text" key="url">
	<displayIf>
		<notEmpty key="config_file" />
	</displayIf>
</tag>

Further reading: Hiding Data Provider Elements In Web UI

Optional Squan Sources

Running Squan Sources is now optional in the Software Analytics model. When launching an analysis with the Software Analytics model, Squan Sources is no longer launched by default, since a Software Analytics project may contain only tickets, requirements or resources, not necessarily source code.

The data provider is now optional, but this means that your scripts must be updated to explicitly launch Squan Sources if you are analysing source code, which was not the case in previous versions.

For most projects, this is as easy as adding -d type=SQuORE to your command line. For more details, refer to the Squan Source command line documentation.

Queue Management Enhancements

Up to Squore 18.1, changing the queue size was complicated (https://support.squoring.com/documentation/latest/install_admin_manual/index.html#sect_queue_size)

This is now a simple parameter in <SQUORE_HOME>/server/standalone/configuration/standalone.xml:

• Stop Squore
• Edit <SQUORE_HOME>/server/standalone/configuration/standalone.xml to change the default value (8 concurrent tasks)

• Start Squore

<managed-executor-service name="squore" jndi-name="java:jboss/ee/concurrency/executor/squore" context-service="default" long-running-tasks="true" core-threads="8"/>

Removed and Deprecated Features Since 18.1

• Export scripts using sqexport.pl file have been removed, use pre-defined highlights exports scripts or custom exports using API instead.
• The "View Source" chart is now deprecated. An automatic link is now available.

Licensing Changes

Your 17.x or 18.x annual subscription license is fully compatible with Squore 19 provided your license has been distributed from March 1st 2019.

If your license has been distributed before March 1st 2019, please contact the Squore support in order to request a new license, compatible with Squore 19.

API Changes

The API user management (user, groups, roles, permissions) has changed.

The information is now wrapped in a JSON object and has an object that contains links to other APIs. Consult the  API documentation.

Squore 18.1 user API example  : 

[{
    "id": 1,
    "login": "admin",
    "locale": "en",
    "timeZone": "Europe/Paris"
},...]

Squore 19.0 user API example  : 

{
 "_links": {
    "self": "http://localhost:8180/SQuORE_Server/api/users"
 },
 "users": [
 {
     "_links": {
          "self": "http://localhost:8180/SQuORE_Server/api/users/1"
      },
      "id": 1,
      "login": "admin",
      "locale": "en",
      "timeZone": "Europe/Paris"
 },....]
}

Changes in Installation Prerequisites

No changes since 18.1

Known Issues

• If you are using Oracle, make sure to deactivate statistics columns before upgrading otherwise the upgrade will fail with the following error : "Caused by: java.sql.SQLException: ORA-54032: column to be renamed is used in a virtual column expression".

  • To know more about Oracle Extended Statistics : https://blogs.oracle.com/optimizer/extended-statistics

Upgrade Notes

From previous minor version to this version :

• Additional disk space required by upgrade: 20% of database size.
• Some benchmarks:
  • Platform: Fedora 29, Intel Core i7-7700HQ, 16 GB RAM, SSD disk. / Time: 160 s/GB.
  • Platform: CentOS 6.7 Final, Intel Xeon CPU E5-1650, 128 GB RAM, HGST Ultrastar 7K4000 disk. / Time: 470 s/GB.

Configuration Changes

For a detailed changelog of the Shared folder, consult the full Configuration Folder Changelog :

• 19.0.9 vs 19.0.10
• 19.0.8 vs 19.0.9
• 19.0.7 vs 19.0.8
• 19.0.6 vs 19.0.7
• 19.0.5 vs 19.0.6
• 19.0.4 vs 19.0.5
• 19.0.2 vs 19.0.4
• 19.0.1 vs 19.0.2
• 19.0.0 vs 19.0.1

Full Changelog

19.0.17

Published on 28th October 2020

• Includes database upgrade: no
• Includes WildFly configuration upgrade: no

• Upgrade Impacts Analysis Model: no

19.0.16

Published on 25th September 2020

• Includes database upgrade: no
• Includes WildFly configuration upgrade: no

• Upgrade Impacts Analysis Model: no

19.0.15

Published on 31st July 2020

• Includes database upgrade: no
• Includes WildFly configuration upgrade: no

• Upgrade Impacts Analysis Model: no

19.0.14

Published on 2nd June 2020

• Includes database upgrade: no
• Includes WildFly configuration upgrade: no

• Upgrade Impacts Analysis Model: no

19.0.13

Published on 27th April 2020

• Includes database upgrade: no
• Includes WildFly configuration upgrade: no

• Upgrade Impacts Analysis Model: no

19.0.12

Published on 15th April 2020

• Includes database upgrade: no
• Includes WildFly configuration upgrade: no

• Upgrade Impacts Analysis Model: no

19.0.11

Published on 20th March 2020

• Includes database upgrade: no
• Includes WildFly configuration upgrade: no

• Upgrade Impacts Analysis Model: no [diff]

19.0.10

Published on 4th December 2019

• Includes database upgrade: no
• Includes WildFly configuration upgrade: no

• Upgrade Impacts Analysis Model: no [diff]

19.0.9

Published on 14th November 2019

• Includes database upgrade: no
• Includes WildFly configuration upgrade: no

• Upgrade Impacts Analysis Model: no [diff]

19.0.8

Published on 6th September 2019

• Includes database upgrade: yes
• Includes WildFly configuration upgrade: no

• Upgrade Impacts Analysis Model: no [diff]

19.0.7

Published on 8th August 2019

• Includes database upgrade: no
• Includes WildFly configuration upgrade: no

• Upgrade Impacts Analysis Model: no [diff]

19.0.6

Published on 2nd August 2019

• Includes database upgrade: no
• Includes WildFly configuration upgrade: no

• Upgrade Impacts Analysis Model: no [diff]

19.0.5

Published on 15th July 2019

• Includes database upgrade: no
• Includes WildFly configuration upgrade: no

• Upgrade Impacts Analysis Model: no [diff]

  
  

19.0.4

Published on 5th July 2019

• Includes database upgrade: no
• Includes WildFly configuration upgrade: no

• Upgrade Impacts Analysis Model: yes, #13544  [diff]

  
  

19.0.2

Published on 21th June 2019

• Includes database upgrade: no
• Includes WildFly configuration upgrade: no

• Upgrade Impacts Analysis Model: no [diff]

  
  

19.0.1

Published on 7th June 2019

• Includes database upgrade: yes
• Includes WildFly configuration upgrade: no

• Upgrade Impacts Analysis Model: yes (from 18.x and lower) | no (from 19.0)

• Also includes all changes and bug fixes from Squore 18.1.6 (release to be published for the week 24)

19.0.0

Published on 30th April 2019

• Includes database upgrade: yes
• Includes WildFly configuration upgrade: yes

• Upgrade Impacts Analysis Model: yes (from any version)

• Also includes all changes and bug fixes from Squore 18.1.5