Oops:
I believe you're correct -- there is no "gemfire-pulse" so that job should
*not* be referring to it.
On Fri, Jul 22, 2016 at 11:02 AM, Kirk Lund wrote:
> I believe you're correct -- there is no "gemfire-pulse" so that job should
> be referring to it.
>
> -Kirk
>
>
> On Fri, Jul 22, 2016
I thought the git clean 'gemfire-pulse' was there to catch issues when it
was renamed to 'geode-pulse', do we still need it anymore? I think it can
be removed.
--Mark
On Fri, Jul 22, 2016 at 11:02 AM, Kirk Lund wrote:
> I believe you're correct -- there is no "gemfire-pulse" so that job should
I believe you're correct -- there is no "gemfire-pulse" so that job should
be referring to it.
-Kirk
On Fri, Jul 22, 2016 at 10:34 AM, William Markito
wrote:
> Here is the current configuration on geode-nightly:
>
> git clean -d -f gemfire-pulse/src/main/resources/
>
> Shouldn't this be :
>
>
Here is the current configuration on geode-nightly:
git clean -d -f gemfire-pulse/src/main/resources/
Shouldn't this be :
git clean -d -f geode-pulse/src/main/resources/
Thanks
--
~/William