This action runs plantuml using a locally downloaded plantuml.jar file.

- uses: dragondive/run-plantuml-local@v1
  with:
    version: 'latest'
    cache-plantuml-jar: 'true'
    cli-arguments: '-h'
    jvm-options: ''

Parameters

• version: The version of plantuml to use.

  
  

  Example values: latest, '1.2024.6'

  Default: latest

  
  

  📝 For the available versions, see plantuml releases.
• cache-plantuml-jar: Cache the downloaded plantuml.jar file, or use the previously cached file, if available.

  
  

  Example values: true, false

  Default: true

  
  

  ❗ When version = latest, this argument is ignored and the latest plantuml.jar file is always downloaded.
• cli-arguments: Command line arguments to plantuml.

  
  

  Example values: -Dmy_var=my_value -o my_output_dir/ -noerror -tsvg my_diagram.puml

  Default: -h

  
  

  📝 For more information on the plantuml CLI, see plantuml command line.
• jvm-options: Options for the JVM.

  
  

  Example values: -Xmx1024m, -DPLANTUML_LIMIT_SIZE=8192, -DPLANTUML_SECURITY_PROFILE=UNSECURE

  Default: ''

• This action's sanity tests also serve as a reference for how to use this action in a Github Actions workflow. Relevant code snippets with minor adaptations are copied below for easy reference.

  steps:
    - name: Checkout repository
      uses: actions/checkout@v4.1.7
  
    - name: Run plantuml
      uses: dragondive/run-plantuml-local@v1.0.1
      with:
        version: '1.2024.6'
        cache-plantuml-jar: true
        cli-arguments: >
          -tsvg -noerror
          -Dinput_data_file=${{ github.workspace }}/plantuml/diagram-data.json
          -Doutput_filename=test_plantuml
          -o ${{ github.workspace }}
          ${{ github.workspace }}/plantuml/diagram.puml
        jvm-options: -DPLANTUML_LIMIT_SIZE=8192 -Xmx1024m

  For the complete workflow, see test.yml.

Q: Why create this new action when there are already many actions for this purpose?

A: Actions that use the plantuml online server or the plantuml docker image work well for most usecases. When working on automating my diagram generations, I had initially included them in my workflows. However, I encountered limitations with diagrams that required file includes and setting JVM options. For full flexibility and control, I needed to use a local plantuml.jar to generate the diagrams, leading to the creation of this action.

The limitations of the server and docker-based actions are detailed in the wiki here: Why create this action instead of using the server-based or docker-based actions.

Q: Why is caching not supported when version is specified as latest?

A: The initial implementation of this action uses the specified version as part of the cache key. With this approach, cache invalidation when plantuml releases a new version becomes a challenge. Issue #2 tracks this enhancement. Caching when version = latest will be supported in a future version.