IntelliJ IDEA lets you run, debug and manage Gradle tasks in your project.
Run Gradle tasks
You can use several ways to run Gradle tasks such as run them from the Run Anything window, with a run configuration, from a context menu, and even run several tasks with one run configuration.
tip
You can also run Gradle command line options through the Run Anything window.
Run a Gradle task in the Run Anything window
In the Gradle tool window, on the toolbar, click . Alternatively, press Ctrl twice to open the Run Anything window.
In the Run Anything window, start typing a name of the task you want to execute. To execute several tasks, enter task names using space to separate each new task. Alternatively, scroll down to the Gradle tasks section and select the task you need. Press Enter.
If you have linked projects and want to run a task for the specified project then in the Run Anything window, in the top-right corner, from the Project list, select the name of the project and in the search field enter the name of your task.
note
If you have options such as offline mode configured for the project, IntelliJ IDEA will automatically include the configuration into the running scope.
IntelliJ IDEA runs the specified task and displays the result in the Run tool window.
IntelliJ IDEA also saves the task in the Run Anything window under the Recent section as well as under the Run Configurations node in the Gradle tool window.
Run a Gradle task via Run Configurations
You can add some additional parameters to your task, configure it as a run configuration, save it and use that run configuration in your project whenever you need.
Open the Gradle tool window.
Right-click the task for which you want to create the Run configuration.
From the context menu select Create 'task name'.
In Create Run/Debug Configuration: 'task name', specify the task settings and click OK.
IntelliJ IDEA displays the task under the Run Configurations node.
Double-click the task to run it or right-click the task and from the context menu select Run.
In the Run/Debug Configurations dialog, click and select Gradle to add a new configuration.
On the right side of the Run/Debug Configurations dialog, in the Name field, enter the name of your configuration. As an example, specify the following settings:
Gradle project- click and select the registered Gradle project.
Tasks- specify tasks you want to execute with this configuration. You can run more than one task. For example, specify clean and build.
VM options- you can customize VM options. For example, specify -Xmx3g.
Click OK. The created configuration is added to the Run Configurations node in the Gradle Projects tool window.
Double-click the configuration to run the task or right-click the configuration and select Run.
Debug Gradle tasks and scripts
You can debug Gradle tasks and scripts the same way you debug your regular applications.
IntelliJ IDEA opens one tab per debugging session for Gradle scripts and for your regular tests. The Debug tool window contains Frames and Variables, as well as the Console output.
You can perform stepping actions and stop on breakpoints that you set in build.gradle and in the regular test classes under a single tab in the debugging session.
Gif
Configure Gradle debugging process
Create a run/debug configuration. If you have the existing run/debug configuration, select it on the main menu, and click Edit Configurations.
On the Run/Debug Configurations page, click the Gradle Debug tab.
Use the following options to configure the gradle debugging process:
Enable Gradle script debugging: by default, this option is disabled, select it to enable breakpoints in the Gradle build script.
If the Choose per test option is selected in the Gradle settings, IntelliJ IDEA clears the Enable Gradle script debugging option and disables the breakpoints in the Gradle scripts. This is done to speed up your debugging process.
Debug forked tasks in the same session: when this option is selected any new debugging process is run under the same tab in the Debug tool window. Clear this option if you want to see each debugging process in a separate tab.
Debug all tasks on the execution graph: when you select this option, every task in the execution graph will be debugged. For example, all the dependent tasks of the task you are trying to debug will be debugged as well.
Debug a Gradle script task
Open your build.gradle in the editor.
Set your breakpoints and in the gutter right-click the Run icon. From the context menu, select Debug <name>.
note
If you started the debugging session for the regular tests first, then open the existing run/debug configuration, select Enable Gradle script debugging option, save the changes and restart the debugging process.
IntelliJ IDEA starts the debugging session and you can check the results in the Debug tool window.
Debug a Gradle task
Use the Gradle tool window to debug Gradle tasks that implement the org.gradle.process.JavaForkOptions interface, for example, test or run.
In the Gradle tool window, click the project, open the Tasks node, and right-click a task you want to debug.
From the context menu, select Debug.
The debugging process is started and the task is added to the list of the recent tasks located under the Run Configurations node.
Assign a shortcut to a Gradle task
IntelliJ IDEA lets you assign shortcuts to Gradle tasks and execute those tasks with a single key. You can also assign a shortcut to the Gradle run/debug configuration that can contain more than one task.
In the Gradle tool window, right-click the desired task.
In the Keymap dialog, under the Gradle node navigate to your task.
Right-click the task and from the list that opens, select a type of the shortcut you want to assign.
In the dialog that opens, depending on the shortcut's type, configure your shortcut and click OK. In our case let's add a keyboard shortcut.
You can see that the shortcut is displayed against your task in the Gradle tool window.
While in the Keymap dialog, you can add a new task to which you want to assign a shortcut.
In the Keymap dialog, under the Gradle node, click Choose a task to assign a shortcut.
In the dialog that opens, select a task you need and click OK.
The task is added to the list under the Gradle node. Now you can configure the shortcut.
tip
You can create a quick list of favorite Gradle tasks and refer to that list by the associated shortcut.
Configure running triggers for Gradle tasks
IntelliJ IDEA lets you run Gradle tasks before your project's execution or set other conditions using the task activation configuration.
In the Gradle tool window, right-click a Gradle project.
From the context menu, select Tasks Activation.
In the Tasks Activation dialog, click .
On the Choose activation phase menu, choose when to run your task, for example, Before Build, After Sync, and so on.
On the Choose task menu, select the actual task.
The task and activation phase will be added to the list in the Task Activation dialog. You can also see the activation phase name against the selected task in the Gradle tool window.
Alternatively, you can select the activation phase name from the context menu when you right-click the task you want to execute in the Gradle tool window.
You can also create a run/debug configuration that would depend on a Gradle task.
From the main menu, select Run | Edit Configurations to open the run/debug configuration for your project.
In the Run/Debug Configurations dialog, in the Before Launch section, click the icon.
In the list that opens, select Run Gradle task.
In the Select Gradle Task dialog, specify the project and the task that you want to execute before launching the project. You can specify a Gradle linked project or any other Gradle project. Note that if your Gradle project is not linked then IntelliJ IDEA will use the default configurations (for example, a bundled Gradle version) to run the task.
. Alternatively, press Ctrl twice to open the Run Anything window. 
and select Gradle to add a new configuration. 
and select the registered Gradle project. 
icon. From the context menu, select Debug <name>. 
