Re: Where are builds taking place?

["Mattmann, Chris A (3980)" <ch...@jpl.nasa.gov>]

+1 to PIP snapshots and yes, if lewismc makes it happen, then
nothing to complain about (as Mike Jimmy Joyce stated).

Cheers,
Chris

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattmann@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++






-----Original Message-----
From: Michael Joyce <jo...@apache.org>
Reply-To: "dev@climate.apache.org" <de...@climate.apache.org>
Date: Wednesday, October 29, 2014 at 7:21 PM
To: "dev@climate.apache.org" <de...@climate.apache.org>
Subject: Re: Where are builds taking place?

>I think we're mixing nomenclature and getting confused. The PRs are merged
>and the toolkit tests (UI backend python tests and OCW library tests) are
>run on PRs. Nothing is built. We don't push snapshot releases. Master is
>always the stable snapshot since we test the PRs going in (in theory at
>least), but we don't publish a snapshot somewhere. The existing system's
>functionality is to test PRs when they come in. Nothing more than that.
>It's simply a way to ensure that people have at least run the test suite
>before making a PR.
>
>As to pushing snapshot artifacts I don't see a reason to, but I'm open to
>hear compelling reasons for why we should. Treating master as a stable
>snapshot is sufficient in my opinion. As for builds, I'm open to hear what
>you would want to build. Do you have any ideas? Off the top of my head,
>you
>could build ocw-vm but that takes quite a while to build from nothing to a
>working VM, so that might not be desirable to do daily. Having the VM
>available for each release is sufficient in my opinion (although we don't
>have that available ATM). The OCW library could be pushed to a package
>manager like PyPI but with the amount of dependencies needed I don't see
>being able to run "pip install ocw" as particularly useful, especially
>since we can't easily install all the dependencies for the user with
>setup.py functionality. That's also why easy-ocw isn't simply a list of
>dependencies that are 'pip installed'.
>
>If you see some functionality that you want added please take the lead on
>it and make it happen! I don't think anyone is going to be bothered by
>someone working on making the project better :)
>
>
>
>-- Joyce
>
>On Wed, Oct 29, 2014 at 4:27 PM, Lewis John Mcgibbney <
>lewis.mcgibbney@gmail.com> wrote:
>
>> Hi Mike,
>>
>> On Wed, Oct 29, 2014 at 4:18 PM, <de...@climate.apache.org>
>> wrote:
>>
>> >
>> > Subject: Re: Where are builds taking place?
>> > Builds are run on an external Jenkins with each PR, not nightly.
>> >
>> >
>> >
>> OK. I understood that builds were being triggered on every commit.
>> I am just puzzled as to what is being tested? Are builds successful or
>>just
>> stable? Are we pushing SNAPSHOT artifacts to anywhere? Is there
>>motivation
>> to do this?
>> None of this appears to be public so excuse the questions.
>> Thanks
>> Lewis
>>