Re: [python-control-developers] Adding travis to python-control

[Richard M. <mu...@cd...>]

OK this is set up.  Cc'ing the developers list to keep everyone in the loop.

-richard

On 10 Aug 2014, at 16:18 , Clancy Rowley <cwr...@Pr...> wrote:

> Richard, sounds good.  I'm working on integrating jgoppert's stuff into my local clone of the new github repo, but it is not so simple, as he has a monster commit with lots of trivial changes (e.g. to whitespace) that are likely to break things when we merge with the main branch.  But I'm working through it and hope to finish that tonight and push those commits to github.
> 
> But one nice thing he's added is this "Travis CI" functionality, that automatically runs the tests and measures test coverage, and posts the results in a badge on github.  To activate that, we'll need to flip a switch for the new repo on Travis CI, but I believe you need to be an admin to do that, so I think you (or maybe Scott) would need to do that.
> 
> It looks like all you need to do is go to this website:
> 	https://travis-ci.org/
> and log in with your github id.  It should automatically find your repositories, and then you just click a button to activate travis for that repo.  You also need a .travis.yml file in the repo, but jgoppert has that in his fork, so I will add that when I push his changes.
> 
> -clancy
> 
> On Aug 9, 2014, at 5:41 PM, Richard Murray <mu...@cd...> wrote:
> 
>> It would be great to pull in jgoppert's changes and also fix up the issues you noticed with tests.  I'm going to be working on some of the documentation + github notifications, so won't be messing with the source code in the next few days.  
>> 
>> If there is anything that looks iffy, just post an issue and I'll respond to it quickly.
>> 
>> -richard
>> 
>> On 9 Aug 2014, at 14:30 , Clancy Rowley <cwr...@pr...> wrote:
>> 
>>> Richard, cool.  I cloned the new repository, and it seems to be working fine.
>>> 
>>> I noticed you didn't pull in James Goppert's changes--is that something you're planning to do, or something you'd like somebody else to do (e.g. me--I am happy to), or something you'd rather not do at all?  It seems to me that his changes (at least the ones I have looked at) are good ones, for instance improving the way the tests are run, and getting that travis stuff to work, automatically running tests and measuring test coverage.  Also, he renamed the "src" directory "control", which seems to be standard and convenient, as it allows you to use a developer version of the module just by adding the python-control directory to your PYTHONPATH, without installing it with setup.py.  (I believe you can run "python setup.py --build_ext" too, but seems like an unnecessary extra step.)
>>> 
>>> Anyway, please let me know what your plans are with incorporating James Goppert's changes.  I'm happy to copy them over to the new repository if you'd like.
>>> 
>>> It was great to see you at CDS20.  What a wonderful event it was!
>>> 
>>> -clancy
>>> 
>>> On Aug 9, 2014, at 4:08 PM, Richard Murray <mu...@cd...> wrote:
>>> 
>>>> You are receiving this message because you are on the list of developers for python-control on GitHub.  As I mentioned in the previous note to the discussion list, the plan is that this list will be used for developer discussions, including code commit messages.  There are currently 7 people on this list: Sawyer Fuller, Clancy Rowley, Gustavo Goretkin, Richard Murray, Rene van Paassen, Roberto Bucher and Scott Livingston.
>>>> 
>>>> More posts during the weekend as I finish shifting things over.  I'll post something on python-control-announce when things are complete.
>>>> 
>>>> -richard
>>>> 
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> _______________________________________________
>>>> python-control-developers mailing list
>>>> pyt...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/python-control-developers
>>