LemonTree.Pipeline.Tools

They are availble for downloard from the LieberLieber Nexus:
https://nexus.lieberlieber.com/#browse/browse:lemontree-pipeline-tools

LemonTree.Pipeline.Tools.ModelCheck.exe

Used to check Models for LemonTree Readiness. https://nexus.lieberlieber.com/repository/lemontree-pipeline-tools/LemonTree.Pipeline.Tools.ModelCheck.exe

Commandline Reference

  --Out               File to output .md e.g.: 'out.md'

  --NoCompact         If set the Checks that compact the Model are not run!

  --FailOnErrors      If set the Exitcode will be 2 if there is at least on Check of Status Error!

  --FailOnWarnings    If set the Exitcode will be 1 if there is at least on Check of Status Warning!

  --TableSize         If set the size of the tables in the database will be reported!

  --Orphans           If set Model Orphans will be reported!

  --ChecksConfig      Path to JSON file with checks configuration. If not set, hardcoded checks will be used.

  --NoProjectStatistics    If set the Project Statistics will not be included in the output!

  --details           File to output JSON details report e.g.: 'details.json'. Contains all check results
                      including affected EA elements for failed checks.

  --junit             File to output JUnit XML report e.g.: 'junit.xml'.

  --Model             Required. The  'Model' used for the operation.

  --help              Display this help screen.

  --version           Display version information.

Custom Checks Configuration

ModelCheck supports loading checks from a JSON configuration file using the --ChecksConfig parameter. If no configuration file is specified, the tool uses hardcoded default checks.

To use a custom checks configuration:

LemonTree.Pipeline.Tools.ModelCheck.exe --model "model.qeax" --ChecksConfig "./checks-config.json" --out ".\output.md"

The JSON configuration file should follow this structure:

{
  "checks": [
    {
      "id": "check-id",
      "query": "SELECT COUNT(*) FROM [table] WHERE [condition]",
      "passedTitle": "Title when check passes",
      "failedTitle": "Title when check fails",
      "passedDetail": "Details when check passes",
      "failedDetail": "Details when check fails",
      "passedLevel": "Information",
      "failedLevel": "Error"
    }
  ]
}

Parameters:

id (required): Unique identifier for the check
query (required): SQL SELECT query returning a scalar count — check fails when count > 0
queryOnFail (optional): SQL SELECT query executed when the check fails; returns the affected rows for the details report
passedTitle (required): Title displayed when check passes
failedTitle (required): Title displayed when check fails ({count} is replaced with the actual count)
passedDetail (optional): Details shown when check passes
failedDetail (optional): Details shown when check fails
passedLevel (optional): Severity level when check passes (Passed, Information, Warning, Error)
failedLevel (optional): Severity level when check fails (Passed, Information, Warning, Error)

See the sample checks-config.json in the repository for a complete example with all default checks.

JSON Details Report (`--details`)

Use --details to produce a structured JSON file containing all check results, including the list of affected EA elements for any failed check that has a queryOnFail defined.

LemonTree.Pipeline.Tools.ModelCheck.exe --model "model.qeax" --ChecksConfig "./checks-config.json" --details "details.json"

Output structure:

{
  "checks": [
    {
      "id": "Suspected Tracebility Links",
      "level": "Error",
      "title": "Model has 1 suspected traceability links",
      "detail": "Some requirements have suspected traceability links. Please review and confirm the traceability links.",
      "affectedElements": [
        {
          "CLASSGUID": "{775328B3-8DB0-4b11-99E2-693710DBC2D7}",
          "CLASSTYPE": "Class",
          "TargetName_of_SuspectedLink": "Block1"
        }
      ]
    },
    {
      "id": "Baselines",
      "level": "Passed",
      "title": "No Baseline entries in the model",
      "detail": null,
      "affectedElements": []
    }
  ]
}

The affectedElements array is always present — it is empty for passed checks or checks without a queryOnFail. This output is suitable for pipeline scripts that need to evaluate results programmatically.

PowerShell example — listing affected elements for a specific check:

$details = Get-Content "details.json" -Raw | ConvertFrom-Json

$check = $details.checks | Where-Object { $_.id -eq "Suspected Tracebility Links" }

if ($check.level -eq "Passed") {
    Write-Host "✅ No suspected traceability links found."
} else {
    Write-Host "❌ Affected elements:"
    $check.affectedElements | Format-Table -AutoSize
}

See run-suspected-links-check.ps1 for a full working example.

Powershell Example:

&"C:\Program Files\Git\mingw64\bin\curl.exe" https://nexus.lieberlieber.com/repository/lemontree-pipeline-tools/LemonTree.Pipeline.Tools.ModelCheck.exe --output LemonTree.Pipeline.Tools.ModelCheck.exe

LemonTree.Pipeline.Tools.ModelCheck.exe  --model "model.qeax" --out ".\output.md" --FailOnErrors --FailOnWarnings
echo "finished validation with $LASTEXITCODE"
echo "Exit codes of LemonTree.Pipeline.Tools.ModelCheck.exe:"
echo "* -2 = other runtime exception occurred"
echo "* -1 = CLI argument parsing error occurred"
echo "*  0 = model is valid "
echo "*  1 = model has at least one warning (only if --FailOnWarnings or --FailOnErrors)"
echo "*  2 = model has at least one error  (only if --FailOnErrors)"

Sample Output:

LemonTree ModelCheck results

	Severity	Issue	Message
🔴	Error	Auditing is enabled.	Auditing is not helpful or required if you manage a model inside a VCS with LemonTree.
🔴	Error	Model has 12 Audit Entries	Audits are not helpful or required if you manage a model inside a VCS with LemonTree.
🔴	Error	Model has 1 Resource Allocation Entries	Resource Allocations are not supported when using LemonTree.
🟠	Warning	Model has 1 VCS enabled Packages	Models with Package based VCS are not a supported scenario.
🟢	Passed	No DIAGRAMIMAGEMAP entries in the model
🟢	Passed	No Baseline entries in the model
🟢	Passed	User Security not enabled in the Model
🟢	Passed	No embedded binary images or document entries in the model
🟢	Passed	No ModelDocument entries in the model
🟢	Passed	No t_image entries in the model
🟢	Passed	Model size before compact 1.45 MB after 1.45 MB	If you run compact on the model you can reduce the size to 99.46%
🟢	Passed	Model size before strip and compact 1.45 MB after 1.43 MB	If you strip the model from binary content and run compact on the model you can reduce the size to 98.66%

Project Statistics

Count	Measure
0	Attributes in Elements
0	Constraints on Elements
0	Efforts on Elements
0	Element Testing
10	Elements in Diagrams
0	File on Elements
0	Metrics on Elements
3	Note
0	Opertions in Elements
7	Package
0	Parameters in Operations
1	Part
0	Requirements in Elements
1	Resources Allocated to Elements
0	Risks on Elements
2	Signal
0	Total Connectors
4	Total Diagrams
13	Total Elements
8	Total Packages
1	Total Root Packages