Continuous builds with Gradle! Adds a CI-like addon to your status bar, showing you the last build-status and let you access the last build-reports.

This package is inspired by Cliff Rowley's atom-circle-ci-package. I also snooped into MindscapeHQ's atom-raygun-package to learn more about atom-views. Thank you guys! 🍭

Toggle the result-pane via the Packages-menu, the context-menu or through a click on the GradleCi-status-badge on the right side in your status-bar.

• Refactored package-architecture.
• Fixed issue where the result-pane could get stuck being displayed wrong.
• Fixed issue where the loading of the package could end in a fatal error.
• Fixed several issues behind the curtain.
• 🍬 Added tooltips for the states (disabled & no builds) where the result-pane is inactive.
• 🍬 Added configuration-setting to customize the number of results being held in memory.
• 🍬 Added icon-coloring to make last build-state more visible (green/red), added corresponding configuration-setting.
• 🍬 Added relative time-stamps to the build-results.
• 0.2.3 - Refactored the pane to use Panetastic, which fixes also the placement of the resize-handle during scrolling.
• 0.2.2 - Added animated gif to this readme.
• 0.2.1 - 🍬 Added tooltip for the states where the result-pane is active.

• Fixed project-path as command-line-option.

• Fixed an issue which interrupted the update process. To force an update launch apm upgrade from your command-line.

There are five settings - in your GradleCi's Atom package-settings - available.

Lets you decide if the build-icon is colored or not. Only the two build-states "succeeded" (green) and "failed" (red) are colored to minimize disturbance.

The result-history of build defaults to 3 results. You're able to change that number to every positive number. If the given number is invalid the setting defaults internally to 3 again.

Warning A higher number results in higher memory consumption (depending on the output of your gradle-configuration), this may slow down the whole editor in general.

The result history is not perstisted between different use session. This feature is planned later on.

Calls Gradle with the `--daemon'-option. Gradle then internally starts a daemon, which is able to cache a lot of work. This function is supposed to speed your build-process up to three times. As a Gradle standard the daemon dies automatically after three hours of inactivity.

This field may contain the task you'd like to call for your build. As a default the task test is defined. Since the content of that field is only appended to the commandline, you're free to use it to add options and arguments.

This setting lets GradleCI listen to changes to the project-root-directory. The trigger may namely build after save but listens in fact on every change in the directory. So renaming, adding, deleting files will inoke a build, too.

GradleCi uses a library to watch the directory via filesystem-notifications if possible. If not it falls back (namely on Mac OS) to a polling mechanism. The polling-interval is currently set to 500ms to lower the resource consumption.

There are currently many limitations for the moment - please be patient:

• gradle must be accessible in the "normal" environment.
• The package only holds 3 reports in the memory.
• There's currently only the file-modification trigger.
• There's currently no associated version to your build.

• More robust gradle-execution, based on environment-vars
• Displaying diffed build-results
• Alternative triggers
• Build-versions (does somebody need that?)
• Persistent results (between use-sessions)

Issues, suggestions and pull requests are more than welcome.