Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

2015-06-16 Thread jun aoki
> On June 16, 2015, 11:24 p.m., William Markito wrote: > > Hi Jun, can you please update to be based on the official Dockerfile / > > image for Geode ?https://registry.hub.docker.com/u/apachegeode/geode/ Wow! thank you for letting me know. I think I should have a bit of design discussion with

Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

2015-06-16 Thread Mark Bretl
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35541/#review88159 --- dev-tools/build/Dockerfile (line 10)

Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

2015-06-16 Thread Mark Bretl
> On June 16, 2015, 11:26 p.m., Dan Smith wrote: > > dev-tools/build/Dockerfile, line 7 > > > > > > This probably should be jdk-7u79. I think there were some issues with > > some of the middle versions of jdk-7, and I k

Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

2015-06-16 Thread Dan Smith
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35541/#review88157 --- Cool. I added one comment about the JDK version - it should probably

Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

2015-06-16 Thread William Markito
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35541/#review88156 --- Hi Jun, can you please update to be based on the official Dockerfile

Review Request 35542: GEODE-51 - Hostname for clients property for cache servers

2015-06-16 Thread William Markito
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35542/ --- Review request for geode, Darrel Schneider and Kirk Lund. Bugs: GEODE-51 ht

Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

2015-06-16 Thread jun aoki
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35541/ --- Review request for geode. Bugs: GEODE-60 https://issues.apache.org/jira/bro

Re: geode contribution process proposal

2015-06-16 Thread jun aoki
Anthony, thank you for providing the info. It is straightforward while developing. Some of us think we should run all tests (several hours according to Dan) and there are good reasons to do so. Roman, if you know the answer, please let us know; is it OK to occupy jenkins slaves for several hours o

Re: geode contribution process proposal

2015-06-16 Thread jun aoki
Thank you William, I've got the access! On Tue, Jun 16, 2015 at 2:01 PM, William Markito wrote: > Thanks Jun!! > > Permissions on JIRA should be fine now. > > On Tue, Jun 16, 2015 at 1:58 PM, jun aoki wrote: > > > Could anyone give me access to change Assignee so that I can assign the > CI > >

Re: geode contribution process proposal

2015-06-16 Thread Anthony Baker
What I’m speaking of is a development process where you 1) write some code 2) run some relevant tests 3) repeat until done You can do that with gradle as follows (just as examples): gradle :gemfire-core:test -Dtest.single=ArrayUtilsJUnitTest gradle :gemfire-core:test -Dtest.single=com/gemstone/g

Re: geode contribution process proposal

2015-06-16 Thread William Markito
Thanks Jun!! Permissions on JIRA should be fine now. On Tue, Jun 16, 2015 at 1:58 PM, jun aoki wrote: > Could anyone give me access to change Assignee so that I can assign the CI > task to myself? > > On Tue, Jun 16, 2015 at 1:57 PM, jun aoki wrote: > > > I've made a root ticket and a few sub

Re: geode contribution process proposal

2015-06-16 Thread jun aoki
I've made a root ticket and a few sub tasks https://issues.apache.org/jira/browse/GEODE-59 for the CI work. Anthony, I'm also interested in how to execute a subset of tests. Let me know! On Mon, Jun 15, 2015 at 10:25 PM, Roman Shaposhnik wrote: > On Mon, Jun 15, 2015 at 7:04 PM, Anthony Baker

Re: geode contribution process proposal

2015-06-16 Thread jun aoki
Could anyone give me access to change Assignee so that I can assign the CI task to myself? On Tue, Jun 16, 2015 at 1:57 PM, jun aoki wrote: > I've made a root ticket and a few sub tasks > https://issues.apache.org/jira/browse/GEODE-59 > for the CI work. > > Anthony, I'm also interested in how to

Maturity Level and the Wiki

2015-06-16 Thread William Markito
Folks, Here is the Maturity Level page for Geode tracking the requirements to become a TLP, based on the best of my knowledge for each items, but please go ahead and update properly if something is not right. But yes, things looks good... ;) https://cwiki.apache.org/confluence/display/GEODE/Mat

Re: [jira] [Commented] (GEODE-38) Gfsh init script ignored

2015-06-16 Thread Roman Shaposhnik
On Tue, Jun 16, 2015 at 11:38 AM, William Markito wrote: > Although the best thing here would be have the full control plugin that can > start/close/comment on the tickets, but AFAIK that's not yet available in > ASF. That is correct. Thanks, Roman.

Re: [jira] [Commented] (GEODE-38) Gfsh init script ignored

2015-06-16 Thread William Markito
Well, actually the current options are: You want to update a ticket with your commit message, add the JIRA ticket filter [GEODE-123] so the it updates the ticket. But if you don't want that you can just not include the ticket filter in your message. The idea of tracking any branch is to get aut

Re: [jira] [Commented] (GEODE-38) Gfsh init script ignored

2015-06-16 Thread Dan Smith
Looks like the git-JIRA integration is adding comments for commits that happen on feature branches. I don't think this is what we want, we probably only want to get comments when fixes are merged to develop. I created a bug for this - GEODE-58 - assigned to William. -Dan On Tue, Jun 16, 2015 at