Hi all,

I've been working on a Gradle plugin to make it easier to write integration 
tests for applications that use Apache Geode, and would like to discuss where 
it should reside.  

To give some background, we have a JUnit Rule called GfshRule that lets you 
write tests that execute gfsh commands. The rule is exported in geode-junit, so 
developers of Geode applications can use the rule to start up a transient 
cluster for their own integration testing, among other things.  
However, the rule relies on having the GEODE_HOME environment variable set to 
an existing installation of Geode, which can be problematic for CI environments 
or tests running inside of containers.

The Gradle plugin will add a task that downloads a distribution of Geode via 
Maven, unzips it into build/install/apache-geode, and sets the proper 
environment variable for any tests that are run through Gradle. 

It would be nice to avoid having the releases of Geode and the plugin tied 
together, so I thought I would suggest having a separate repository for the 
plugin (similar to geode-examples).  Does anyone have thoughts on whether 
that's the correct place for the plugin to live, or on what it should be 
called?  geode-integration-gradle-plugin?

Any feedback is appreciated,
- Jared

P.S. If you want to take a look at the work in progress, it's been pushed here 
for now: https://github.com/jaredjstewart/geode-integration-plugin 
<https://github.com/jaredjstewart/geode-integration-plugin>

Reply via email to