JetBrains Fleet 1.30 Help

Run configurations

In order to run code, tests, and tasks, JetBrains Fleet uses run configurations.

A run configuration specifies the parameters for running your application. It includes commands, executable paths, environment variables, virtual machine options, arguments, and other necessary context.

Create a run configuration

  1. Press āŒ˜ R or select Run | Run & Debug from the main menu. In the popup that appears, select Create Run Configurations.

    The popup that appears upon invoking Run if there are no run configurations in the workspace

    .fleet/run.json opens. This file contains the definitions for the run configurations in the workspace. The file uses JSON format.

  2. Define new configurations as objects in the configurations array. For example, the following configuration runs script.sh and specifies its location using a macros.

    { "configurations": [ { "name": "Run my script", "type": "command", "program": "$USER_HOME$/script.sh", "args": ["any", "optional", "arguments"] } ] }

    For information on macros, such as $USER_HOME$ in the example above, refer to Run configuration macros.

Launch a run configuration

  • Press āŒ˜ R or select Run | Run & Debug from the main menu. Select the configuration that you are going to run or debug.

Run configuration properties

Each run configuration has the following properties:

Key

Description

name

A human-readable name that identifies the run configuration

type

The type of the run configuration, which defines the startup logic. The rest of the parameters depend on the type of the run configuration.

For more information about available run configuration types and their parameters, refer to the section of the particular language you are using: JavaScript, Java, Kotlin, Go, Python, C#, PHP, Rust.

environment

Custom environment variables for the process in the form of a JSON object. To define an environment variable, add a property, where the key is the variable name and the value is the value of the variable, for example:

"environment": { "TEMP_DIR": "/home/user/temp", "GENERATE_RANDOM_PASSWORD": "true" }

dependsOn

Names of other configurations which will be executed before this configuration, for example: "dependsOn": ["first", "second"]. For more information, refer to Chained run configurations.

workingDir

Working directory for this run configuration.

allowParallelRun

When set to true, more than one instance of this configuration can run in parallel.

Last modified: 26 February 2024