Hi Edward, I am happy that you like Travis and the "continuous integration" workflow.
I have seen Travis being used at several github projects and it is a very efficient bug eliminating step. At my work, we use MS Team Foundation Server (TFS) as git repo and then Jenkins to continuously build and deploy all the different software projects. If you like Travis, you would love Jenkins. :) But be aware, it's a project that can steal valuable time ;) You can literally do anything in it. :) And schedule and trigger different jobs under all kinds of conditions. The "brew update". I don't remember, so its probably not important. Either is is a leftover from a tutorial or me wanting "the newest packages". Try to kick it. :) Den tor. 25. apr. 2019 kl. 15.24 skrev Edward d'Auvergne < [email protected]>: > Hi Troels, > > I'm not sure if you've seen, but I have been working on improving our > usage of Travis CI: > > https://travis-ci.com/nmr-relax/relax > > My changes include: > > - Naming of the build jobs. > > - Execution of the software verification tests. > > - Installation of wxPython to enable GUI testing and the running > of the whole test suite. This is currently only for the "Linux > (Ubuntu 14.04), Python 2.7, single processor, all tests." build job. > > - Putting the system tests back before the unit tests to avoid > hiding some nasty relaxation dispersion bugs. > > - Fix for matplotlib on Mac OS X so that the tests will finally > run on this OS. I don't know why the job passed previously with the > Python import errors, but now we have the tests running. > > - A new build job for the API documentation. This is the epydoc > compilation of the HTML API manual. The job checks that the relax > docstrings are compliant with the epydoc format. > > - A new build job for the Free Software Foundation copyright > validation script. This strictly checks that the copyright notices in > relax are correct. > > These changes simplify the relax release process as the previous > preparation steps are now performed automatically by Travis CI for > each push to the GitHub mirror repository. > > Regards, > > Edward > > > P. S. I have one question about your Travis CI set up and that is, > why do you run 'brew update' on Mac OS X? This takes a huge amount of > build time (half of our allowed time) and can cause the build job to > sometimes fail due to timeouts. >
_______________________________________________ nmr-relax-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nmr-relax-devel
