For the complete documentation index, see llms.txt. This page is also available as Markdown.

GitHub Actions

Run BoxLang in your GitHub Actions seamlessly with the official setup action.

πŸš€ Automate your BoxLang setup - This GitHub Action sets up the BoxLang Dynamic JVM Language runtime for CI/CD workflows with optional CommandBox CLI and module installation (https://github.com/marketplace/actions/setup-boxlang-cli)

⌨️ Action Inputs

Configure your BoxLang setup using these input parameters:

Input
Type
Default
Description

boxlang_home

string

${GITHUB_WORKSPACE}/.boxlang

Custom directory for BoxLang installation. Defaults to a writable directory in the workspace to avoid read-only filesystem issues.

commandbox_version

string

latest

The CommandBox version to install. Only used if with-commandbox is true.

commandbox_modules

string

---

If added, a comma-delimited list of CommandBox packages to install. Only used if with-commandbox is true.

forgeboxAPIKey

string

---

If added, it will configure the ForgeBox API Key in CommandBox. Only used if with-commandbox is true.

modules

string

---

If added, a space-delimited list of modules to install upon installation of the binary for you.

with-commandbox

boolean

false

If true, it will install the latest CommandBox as well.

version

semver

latest

The BoxLang version to install, if not passed we use the latest stable.

Version Options:

  • latest - Latest stable release

  • snapshot - Latest development build

  • 1.2.0 - Specific version number

  • 1.x - Latest in major version series

πŸ”³ Usage Examples

Simple Setup

πŸ“¦ With BoxLang Modules

🎯 Specific Version

πŸ“¦ With CommandBox

πŸ”§ CommandBox with Specific Version

πŸ› οΈ CommandBox with Modules

βš™οΈ Full Configuration Example

πŸ”‘ With ForgeBox API Key

🎯 Specific Version with Modules

πŸ“¦ Action Outputs

This action provides the following outputs for use in subsequent workflow steps:

  • boxlang-version: The version of BoxLang that was installed

  • installation-path: The path where BoxLang was installed

πŸ”§ Complete CI/CD Examples

Quick Start Example

Web Application Testing

Module Development Workflow

Multi-Platform Testing

Enterprise CommandBox Deployment

πŸ› Troubleshooting

Common Issues

Action fails with Java not found:

  • The action automatically installs OpenJDK 21. If you see Java errors, try updating to the latest action version.

Module installation timeout:

  • Large modules may take time to install. Consider caching or installing only necessary modules.

Permission errors on Windows:

  • Ensure your workflow has proper permissions set for the Windows runner.

Debug Mode

Enable debug output for troubleshooting:

Last updated

Was this helpful?