Build failed in Jenkins: AuroraBot #1031

See -- Started by timer Building remotely on ubuntu-4 (docker Ubuntu ubuntu4 ubuntu) in workspace > git rev-parse --is-inside-work-tree # timeout=10 Fetching chan

Jenkins build is back to normal : AuroraBot #1032

See

Build failed in Jenkins: AuroraBot #1034

See -- Started by timer Building remotely on ubuntu-4 (docker Ubuntu ubuntu4 ubuntu) in workspace > git rev-parse --is-inside-work-tree # timeout=10 Fetching chan

Jenkins build is back to normal : AuroraBot #1035

See

When (if ever) should we require JDK 8?

Hi folks, JDK 8 was officially released in March 2014, and brought a bunch of new features to the runtime and compiler. A side-effect of using java 8 language features is that it requires a >= 1.8 runtime, This means users currently running the scheduler with java 1.7 would need to upgrade their

Re: When (if ever) should we require JDK 8?

Adopting Java8 syntax would get us significant gains in productivity and code readability. Using JRE8 in production should get us some significant performance gains, though how significant would require performance benchmarks. IMO our target platform is 3-5 servers per Mesos cluster and we should

Re: When (if ever) should we require JDK 8?

Kevin - do you care to propose a concrete release number? -=Bill On Thu, Jan 22, 2015 at 12:00 PM, Kevin Sweeney wrote: > Adopting Java8 syntax would get us significant gains in productivity and > code readability. > > Using JRE8 in production should get us some significant performance gains, >

Re: When (if ever) should we require JDK 8?

How about 0.9, with a deprecation warning at 0.8 On Thu, Jan 22, 2015 at 12:02 PM, Bill Farner wrote: > Kevin - do you care to propose a concrete release number? > > -=Bill > > On Thu, Jan 22, 2015 at 12:00 PM, Kevin Sweeney > wrote: > > > Adopting Java8 syntax would get us significant gains in

Re: When (if ever) should we require JDK 8?

I am big +1 on the migration but I am afraid jumping into it too soon may lock out everyone from upgrading their Aurora cluster until they have 1.8 infra support. The 0.9.0 sounds about right unless there is a pushback from our customers. On Thu, Jan 22, 2015 at 12:04 PM, Kevin Sweeney wrote: >

Re: When (if ever) should we require JDK 8?

+1 to Kevin's proposed cycle. I would like us to use JDK 8 as soon as possible. Kevin's proposal will allow us to get there with the minimal amount of breakage. On Thu, Jan 22, 2015 at 12:04 PM, Kevin Sweeney wrote: > How about 0.9, with a deprecation warning at 0.8 > > On Thu, Jan 22, 2015 at

Thermos external component deprecation plan

Thermos is a standalone task execution system that is not coupled to Aurora or Mesos. This is why by default, Thermos writes out of the sandbox (/var/run/thermos), has a separate observability system (Thermos observer), and CLI (thermos.) Aurora built a Thermos executor as its default executor, b

Build failed in Jenkins: AuroraBot #1046

See -- [...truncated 3934 lines...] def test_integration_stop(self):  with self.yield_sleepy(ThermosTaskRunner, sleep=1000,

Jenkins build is back to normal : AuroraBot #1047

See