Re: Still Failing: apache/mesos#1269 (master - b74ed17)

We use Jenkins as our primary post-commit CI infrastructure. https://builds.apache.org/job/mesos/ The Travis build has been failing ever since it was created, although these emails may be new. Looks like Travis CI recently upgraded to a container-based infrastructure. On Thu, Oct 8, 2015 at 4:19

custom(ized) conteinerization

Triggered by the thread on potential deprecation of external containerizer, I wonder what would make sense to do to address the following set of requirements: 1. I need resource isolation for individual tasks (mainly for QoS reasons), so having container per task seems reasonable 2. I have

Re: Still Failing: apache/mesos#1269 (master - b74ed17)

I have a travis file which could test mesos build in OSX https://github.com/haosdent/mesos/blob/master/.travis.yml Build result could pass. https://travis-ci.org/haosdent/mesos Should I add it back to Mesos? On Fri, Oct 9, 2015 at 5:14 PM, Adam Bordelon wrote: > We use

[VOTE] Release Apache Mesos 0.25.0 (rc3)

Hi all, Following up with an RC with the build fix suggested by Kapil: Please vote on releasing the following candidate as Apache Mesos 0.25.0. 0.25.0 includes the following: * [MESOS-1474] - Experimental

Re: custom(ized) conteinerization

(1) is something that has come up before. The containerizer deals with a variable sized container, the semantics of a task are defined by the executor, there is no way for the containerizer to understand the meaning of a task currently. Some tasks are "special" in that they don't have an executor

Re: Proposal: moving Mesos website to project codebase

Artem: SGTM. Let's upstream it! On Fri, Oct 9, 2015 at 3:28 PM, Artem Harutyunyan wrote: > I am the maintainer of the > https://github.com/mesosphere/mesos-website-container repo. I can just > go ahead and post a review on Review Board and add the entire repo to > ASF mesos

Re: Proposal: moving Mesos website to project codebase

Done https://reviews.apache.org/r/39194/. Folks, please take a look and let's have a couple of iterations over this. Cheers, Artem. On Fri, Oct 9, 2015 at 3:30 PM, Adam Bordelon wrote: > Artem: SGTM. Let's upstream it! > > On Fri, Oct 9, 2015 at 3:28 PM, Artem Harutyunyan

Re: apply-reviews.py

Maybe we can think of stripping verify_reviews.py down and making it concentrate just on the verification part and call into apply-reviews.py for fetching reviews. Another alternative would be to merry the two together (like you're suggesting, and Adam mentioned it too at some point). I personally

Re: Proposal: moving Mesos website to project codebase

I am the maintainer of the https://github.com/mesosphere/mesos-website-container repo. I can just go ahead and post a review on Review Board and add the entire repo to ASF mesos (say under support/website). Once we do that we will retire mesosphere/mesos-website-container repo to avoid confusion.

Re: Proposal: moving Mesos website to project codebase

Sounds good Artem, however I'd put the Dockerfile into the new "site" directory which is where you now run rake from. With the process now being quite a lot simpler I'm not sure the run_site.sh script is needed anymore and the "bundle install && rake && rake dev" line could probably go directly

Re: Proposal: moving Mesos website to project codebase

Adam, I wasn't aware of https://github.com/mesosphere/mesos-website-container, no none of us tried building the site in a docker container, but I'm happy to take a look at that at some point soon. That repo doesn't have a LICENSE file, I'd be keen to move the Dockerfile into the site directory of

Re: Proposal: moving Mesos website to project codebase

+1 to incorporating the mesos-website-container, I've found that very helpful for catching formatting issues when making documentation changes. (thanks Artem! :-) On Fri, Oct 9, 2015 at 2:33 PM, Jonathon Rossi wrote: > Adam, I wasn't aware of >

Re: Proposal: moving Mesos website to project codebase

@Jonathon: absolutely right, mate, you guys totally blew us away with was possible in just one day of coding! Again congrats on a well-deserved win! — Sent from my iPhone, which is not as good as you'd hope to fix trypos n abbrvtn. On Fri, Oct 9, 2015 at 10:34 PM, Jonathon Rossi

Re: apply-reviews.py

Depending on how sophisticated one wants to get, we could abstract away common behavior in a class and have the scripts use the functionality.  You know, you can write well-designed OO code in Python too ;-) Happy to help where I can.  — Sent from my iPhone, which is not as good as

Re: Proposal: moving Mesos website to project codebase

+1! On Oct 9, 2015 10:37 PM, "Kevin Sweeney" wrote: > +1! > > On Fri, Oct 9, 2015 at 3:35 PM Marco Massenzio > wrote: > > > +1 > > > > Dave - great stuff! > > > > *Marco Massenzio* > > > > *Distributed Systems Engineerhttp://codetrips.com

Re: Proposal: moving Mesos website to project codebase

+1 On Fri, Oct 9, 2015 at 8:59 AM, haosdent wrote: > +1! > On Oct 9, 2015 10:37 PM, "Kevin Sweeney" wrote: > > > +1! > > > > On Fri, Oct 9, 2015 at 3:35 PM Marco Massenzio > > wrote: > > > > > +1 > > > > > > Dave - great stuff! > >

Re: Proposal: moving Mesos website to project codebase

+1 Dave - great stuff! *Marco Massenzio* *Distributed Systems Engineerhttp://codetrips.com * On Fri, Oct 9, 2015 at 3:05 PM, Dave Lester wrote: > As part of the #MesosCon Europe hackathon, my team has been making > improvements to the website. Among

Proposal: moving Mesos website to project codebase

As part of the #MesosCon Europe hackathon, my team has been making improvements to the website. Among these changes, we'd like to propose changing where the website source files live by moving them to the main Mesos codebase. Our current progress / working branch of this is available on GitHub:

Re: Proposal: moving Mesos website to project codebase

+1! On Fri, Oct 9, 2015 at 3:35 PM Marco Massenzio wrote: > +1 > > Dave - great stuff! > > *Marco Massenzio* > > *Distributed Systems Engineerhttp://codetrips.com * > > On Fri, Oct 9, 2015 at 3:05 PM, Dave Lester wrote: > > > As

Re: Proposal: moving Mesos website to project codebase

+1 for making it easier for contributors to understand the website code and collaboratively maintain it! -- Jiang Yan Xu @xujyan On Fri, Oct 9, 2015 at 5:21 PM, Paul Brett wrote: > +1 > > On Fri, Oct 9, 2015 at 8:59 AM,

Re: Proposal: moving Mesos website to project codebase

+1 On Fri, Oct 9, 2015 at 1:02 PM, Niklas Nielsen wrote: > +1 > > On 9 October 2015 at 09:50, Yan Xu wrote: > > > +1 for making it easier for contributors to understand the website code > and > > collaboratively maintain it! > > > > -- > > Jiang Yan Xu

Re: apply-reviews.py

Is this going to be combined with the logic to do the same thing in https://github.com/apache/mesos/blob/master/support/verify_reviews.py which is used for the Jenkins Mesos CI? They are doing about the same thing now in "download a whole set of reviews in order". Be nice to just have one. On

Re: Proposal: moving Mesos website to project codebase

+1 On 9 October 2015 at 09:50, Yan Xu wrote: > +1 for making it easier for contributors to understand the website code and > collaboratively maintain it! > > -- > Jiang Yan Xu @xujyan > > On Fri, Oct 9, 2015 at 5:21 PM, Paul Brett

Re: [VOTE] Release Apache Mesos 0.25.0 (rc2)

Hi everyone, Thanks everyone for testing the RC! Due to the -1, we will cherry pick bfeb070a2aef52f445eb057076d344fd184eb461 and send out an RC3 today. Stay tuned and thanks for the prompt feedback! Cheers, Mpark, Joris and Niklas On 8 October 2015 at 06:40, Bernd Mathiske

Re: Still Failing: apache/mesos#1269 (master - b74ed17)

I think travis currently just uses default settings, which fail always. I don't know how valuable OSX build CI is on its own, but Jenkins only tests Linux, so OSX on Travis would give us better test coverage. Comments from a quick first look: - Can you make it `make check` or `make distcheck`