Re: Shepherding new contributions

Thanks for that background, Henry! That is actually useful for other unrelated thoughts I have had. We will make sure to keep this in mind. On Monday, February 23, 2015, Henry Saputra wrote: > Ok, we need to be careful about this maintainers/owners or shepherds > business. > > Apache Spark got

Re: Shepherding new contributions

Looking at the reviewboard documentation it seems we can set the TARGET_PEOPLE field in .reviewboardrc to ensure the people line is auto-populated for each review. I think populating it initially

Re: Shepherding new contributions

I'm ok with that, as I think it's a better experience for new contributors than the current situation. However, my understanding is that we generally have a policy that you need a ship it from everyone on the People line of a review. If that's the case than the default people need to be cognizant o

Re: Shepherding new contributions

This would work. Anyone assigned as reviewer in the RB need to either execute the review or excuse themselves to make sure all "ship it" votes are accounted for. - Henry On Tue, Feb 24, 2015 at 11:39 AM, Joshua Cohen wrote: > I'm ok with that, as I think it's a better experience for new contribu

Build failed in Jenkins: Aurora #894

See Changes: [maxim] Refactoring CronJobManager interface. -- [...truncated 2938 lines...] x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I

Jenkins build is back to normal : Aurora #895

See

Build failed in Jenkins: Aurora #896

See Changes: [maxim] Renaming storage.thrift job store structs. -- [...truncated 4236 lines...] generated xml file:

time constraint on aurora jobs?

Hello, In apache aurora, there are resource isolations and sizings on CPU, memory and disk space, which can be specified in the job configuration file. Is there any similar way to put a constraint on job running time, like killing a job if it has been running for more than a certain amount of

Re: Sharing scripts for deploying Aurora on Mesosphere

A bit late, but… this is awesome!!! If you’re interested in putting this in a full-blown repo or something, I’d be happy to send in a PR and/or add some comments with more notes, questions, and suggestions if you’re interested :) Thanks for sharing! Joe > On Feb 21, 2015, at 19:16, Hussein Elg

Re: Testing Done in RB?

I’m ambivalent either way, but overall sounds like a good path forward, so filed https://issues.apache.org/jira/browse/AURORA-1147 > On Feb 23, 2015, at 10:55, Joshua Cohen wrote: > > If we decide to remove the 'Testing Done' section from co

Re: [proposal] Deprecate the Thermos CLI

In the mid-term, it can be accessed via the Observer. When that is deprecated, that data will be accessed in whatever manner replaces the Observer, which I assume will not be the Thermos CLI. > On Feb 23, 2015, at 20:07, Zameer Manji wrote: > > Possibly. Without the CLI I don't see how we can

Re: time constraint on aurora jobs?

Very good question.. to my knowledge there is not a ‘time’ constraint. However, you could implement this in a few ways. One of my first thoughts is to setup a custom StatusChecker