Re: Testing our UI code

2015-09-10 Thread Kevin Sweeney
+1 On Thu, Sep 10, 2015 at 1:30 PM, Joseph Smith wrote: > Agreed, this seems awesome. > > Thanks Josh! > > > > On Sep 10, 2015, at 1:09 PM, David McLaughlin > wrote: > > > > +1 to this, seems like an ideal solution to getting testing into the UI > > asap. > > > > On Thu, Sep 10, 2015 at 10:30 A

Re: Testing our UI code

2015-09-10 Thread Joseph Smith
Agreed, this seems awesome. Thanks Josh! > On Sep 10, 2015, at 1:09 PM, David McLaughlin wrote: > > +1 to this, seems like an ideal solution to getting testing into the UI > asap. > > On Thu, Sep 10, 2015 at 10:30 AM, Joshua Cohen > wrote: > >> One question: will this effort get us any clos

Re: Testing our UI code

2015-09-10 Thread David McLaughlin
+1 to this, seems like an ideal solution to getting testing into the UI asap. On Thu, Sep 10, 2015 at 10:30 AM, Joshua Cohen wrote: > One question: will this effort get us any closer to improving > iteration speed? I.e. not requiring gradle run on a host machine > before jumping into vagrant? >

Re: 0.10.0 Feature Requests

2015-09-10 Thread Bill Farner
I agree, documentation overhauls are best decoupled from releases. On Thu, Sep 10, 2015 at 10:49 AM, Jake Farrell wrote: > Think that this is a great idea and agree that we need to spend some time > improving our user content, but it should not be a blocker to the next > release candidate. Impro

Re: 0.10.0 Feature Requests

2015-09-10 Thread Jake Farrell
Think that this is a great idea and agree that we need to spend some time improving our user content, but it should not be a blocker to the next release candidate. Improving our documentation and website should be an ongoing effort -Jake On Thu, Sep 10, 2015 at 1:43 PM, Zameer Manji wrote: >

Re: 0.10.0 Feature Requests

2015-09-10 Thread Zameer Manji
One thing I would like to see in 0.10.0 is improvement to our documentation. We have a lot of documentation but I don't think it is well organized or very accessible to a new user or a prospective user. This might involve writing new documentation, improving our, website, etc. On Tue, Sep 8, 2015

Re: Testing our UI code

2015-09-10 Thread Joshua Cohen
One question: will this effort get us any closer to improving iteration speed? I.e. not requiring gradle run on a host machine before jumping into vagrant? No, this won't have any impact on iteration speed, as things currently stand, there's going to be some need for gradle to run on the host mac

Re: Testing our UI code

2015-09-10 Thread Zameer Manji
+1 I look forward to having some sort of test infrastructure for the JavaScript code. Anything is better than our current situation. On Thu, Sep 10, 2015 at 9:20 AM, Joshua Cohen wrote: > Yes, it should be. I haven't actually verified it myself yet, but based on > the description of the gradle

Re: Testing our UI code

2015-09-10 Thread Jake Farrell
+1 to that, thanks for looking into this -Jake On Thu, Sep 10, 2015 at 12:20 PM, Joshua Cohen wrote: > Yes, it should be. I haven't actually verified it myself yet, but based on > the description of the gradle node.js plugin[1], it seems completely > painless: > > This plugin enables you to run

Re: Testing our UI code

2015-09-10 Thread Bill Farner
+1! On Thu, Sep 10, 2015 at 9:20 AM, Joshua Cohen wrote: > Yes, it should be. I haven't actually verified it myself yet, but based on > the description of the gradle node.js plugin[1], it seems completely > painless: > > This plugin enables you to run any NodeJS script as part of your build. It

Re: Testing our UI code

2015-09-10 Thread Maxim Khutornenko
+1. Thanks for driving this Joshua! One question: will this effort get us any closer to improving iteration speed? I.e. not requiring gradle run on a host machine before jumping into vagrant? On Thu, Sep 10, 2015 at 9:20 AM, Joshua Cohen wrote: > Yes, it should be. I haven't actually verified it

Re: Testing our UI code

2015-09-10 Thread Joshua Cohen
Yes, it should be. I haven't actually verified it myself yet, but based on the description of the gradle node.js plugin[1], it seems completely painless: This plugin enables you to run any NodeJS script as part of your build. It does not depend on NodeJS (or NPM) being installed on your system. Th

Re: Testing our UI code

2015-09-10 Thread Bill Farner
I think this is great! Am i understanding correctly that this will all be self-bootstrapping on dev machines? On Thu, Sep 10, 2015 at 8:44 AM, Joshua Cohen wrote: > Hi all, > > I recently posted an update on this ticket: > https://issues.apache.org/jira/browse/AURORA-451 describing what I see a

Testing our UI code

2015-09-10 Thread Joshua Cohen
Hi all, I recently posted an update on this ticket: https://issues.apache.org/jira/browse/AURORA-451 describing what I see as the best way forward to enable tests for our UI code. I figured this warranted some extra attention so calling it out here as well. To restate what's in the ticket, I propo

issue running docker container in aurora

2015-09-10 Thread Siddharth, Gopalsamy
Hi dev folks , I am using mesos 23.0 and aurora 0.9.0 which I installed from deb files. Is there any requirement for thermos_executor to have libmesos /python 2.7 in the container because the container runs fine out of aurora? i`m seeing a few errors of the following : MesosDriver not found :