Author Archives: Mike Swainston

Manipulating File Names in Structure101 C/C++ Models

C and C++ models can prove challenging to interpret if the file structure of the model does not reflect the structure that the project team are used to seeing (which might happen for a number of reasons). Structure101 Studio has … Read More

Using Structure101 Build with SonarQube

When using Structure101 Build with SonarQube the detection of new structural issues can be delegated to SonarQube. This simplifies the configuration of Structure101 Build but requires an appropriate SonarQube Quality Gate to be defined. [Build 14507 and later of the … Read More

Using Structure101 Build with Jenkins and SonarQube

Structure101 Build and the Structure101 SonarQube plugin can be incorporated into your existing Jenkins CI process. This post describes the necessary configuration. [Build 14507 and later of the Structure101 SonarQube plugin] Structure101 Build performs architectural checks and can publish a snapshot … Read More

Using the Structure101 SonarQube Plugin with Maven

The Structure101 Key Measures can be reported via SonarQube. The configuration to do this is straight forward and can re-use an existing Structure101 Build configuration file. [Build 14385 of the Structure101 SonarQube plugin] It is assumed that SonarQube Scanner is already … Read More

Configuring Structure101 Build

Structure101 Build can be added to your existing CI processes to check for new structural violations and deteriorating key measures. Structure101 Build is delivered as a zip archive. Installation is simply unpacking to a suitable folder location. The core jar file is … Read More

Using the Structure101 SonarQube Plugin with Gradle

The Structure101 Key Measures can be reported via SonarQube. The configuration to do this is straight forward and can re-use an existing Structure101 Build configuration file. [Build 14385 of the Structure101 SonarQube plugin] It is assumed that SonarQube Scanner is already … Read More

Structure101 Build Configuration with Workspace based Studio Projects

Structural refactoring initiatives typically make use of the synchronisation that is possible between Studio and Workspace.  Careful configuration of Structure101 Build will ensure the Key Measures can be tracked consistently across Studio, Workspace, SonarQube and the Structure101 Web Application. Workspace … Read More

Merging Structure101 Studio Action Lists

The action lists created in Structure101 Studio are saved in the project .hsp file. Currently there is no ‘Merge Action List’ feature in Studio. But the lists can be merged by editing the .hsp XML file. To avoid overwriting your … Read More

Structure101 Workspace IntelliJ IDEA and Gradle

The IDEA gradle import creates module compile output paths that are different to the gradle build output paths. Structure101 Workspace uses the IDEA module compile output paths to find the bytecode. So, running a gradle build will not propagate changes to … Read More

Monolith to Modular, Part 4 – Sizing and Estimating Scope

Module extractions with many tens or hundreds of violations to resolve will benefit from preparatory planning and estimation. This is the fourth post in a series that will explore the challenges of migrating a monolithic code base to a modular … Read MoreRead More