Gradle Eclipse support is developed by the SpringSource STS team. You can either use it via STS or install it separately. The Gradle Eclipse plugin provides the best IDE integration so far. It allows you to import Gradle projects into Eclipse. The information from the Gradle build script is used to configure your project in Eclipse. The import wizard is pretty smart. You can do partial imports of multi-project builds. You can also choose different naming patterns for sub-projects. You can even define Gradle tasks that should be run before and after an import/refresh. Additionally the Gradle plugin provides a runner for executing Gradle builds. The Gradle plugin also detects Gradle build scripts and automatically enables Groovy editor support for those files. That gives you syntax highlighting, syntax check and auto formatting.
Of course you can also use the Eclipse plugin for Gradle to generate the Eclipse metadata.
Jetbrains has added support for Gradle with IDEA 11. You can import a Gradle project like you can import a Maven one. There is much more to come. New versions of the Gradle plugin will be released independently of IDEA.
Of course you can also use the IDEA plugin for Gradle to generate IDEA metadata.
Geertjan Wielenga, Principal Product Manager in the Oracle Developer Tools group, initiated the Gradle plugin for NetBeans. This plugin is now developed by Attila Kelemen and is hosted at https://github.com/kelemen/netbeans-gradle-project.
With the Gradle wrapper you can use Gradle for any CI server. If you do it this way, it does not matter if a Gradle plugin exists for a particular CI server or in the case it exists, whether it is installed. You would just choose the command line runner and the rest will be figured out by the Gradle wrapper.
Nonetheless it is nice when the CI server provides dedicated support for Gradle. This can add a lot of smartness to the logging, reporting, configuration, and so on.
There is a good Jenkins plugin for Gradle. We are also working with the Jenkins team on a couple of other issues:
- Enable deployment of Jenkins jobs from Gradle
- Build Jenkins plugins with Gradle
TeamCity ships with excellent, out-of-the-box Gradle support. See the for how to set up Gradle build steps.
Bamboo does not ship with dedicated Gradle support. You can either use the Gradle wrapper or the Bamboo Artifactory plugin which includes a runner for Gradle.
Gradle has excellent integration with the JFrog Artifactory. We cooperate very closely with the Artifactory team to provide the best possible support.
Gradle plays nicely with Nexus. Gradle can autogenerate a pom.xml and can deploy to any Maven repository and thus also to Nexus.
There is an excellent Gradle Sonar plugin. We cooperated with SonarSource to develop it.
There is a Gradle JRebel plugin for automatic, customizable generation of JRebel configuration files by the build.
Heroku integration is work in progress but will be announced soon. If you want to become a beta tester, please contact us on the forums.
No special integration here. Nonetheless it is cool that GitHub recognizes Gradle build scripts and provides nice syntax highlighting for them.