Run
→Edit Configuration
→+
.
- Select configuration type your typical run task is.
- Name: something meaningful, like
*-remote-build
.
- Name: something meaningful, like
- Remove standard
Make
/etc step fromBefore Launch
section (ha!). - Create a step in
Before Launch
section forRun External Tool
.- Name: use something meaningful, like
remote assembleDebug
. - Program:
bash
. - Parameters:
mainframer.sh somebuildcommand with parameters
or any command you want*. - Working directory:
$ProjectFileDir$
.
- Name: use something meaningful, like
This also works for tests, you can compile tests on remote machine and then IntelliJ will simply run compiled code on your local machine.
Tip: you can override default run configuration options to to run tasks through mainframer by default.
Note to IntelliJ team: please keep things as is so we can do crazy stuff like mainframer
!
Follow mainframer IntelliJ Plugin development.
For example, assembleDebug
for specific module.
$ ./gradlew :app:assembleDebug
Instead of.
$ ./gradlew assembleDebug
If your build system supports some kind of daemoning like Gradle does or Buck, please enable it on remote machine to achieve maximum performance.