Andres Gomez <ago...@igalia.com> writes: > Until now we were only running the python unit tests. > > It seems desirable to also check that the CMake based build compiles > successfully. We do that now using docker. > > The docker build can be tweaked with some environment variables and, > also, be stored in the docker hub if desired. Check the changes for > extra details regarding these variables. > > v2: Removed other build possibilities other than just from inside > Travis-CI, as suggested by Juan. > v3: Replaced the "RELEASE" parameter to create the docker image with > "PARENT" and removed some unneeded documentation after v2, as > suggested by Juan. > > Cc: Dylan Baker <dy...@pnwbakers.com> > Cc: Juan A. Suarez <jasua...@igalia.com> > Signed-off-by: Andres Gomez <ago...@igalia.com> > Reviewed-by: Juan A. Suarez <jasua...@igalia.com>
I'm definitely interested in extending our tests using Travis, but could you add some comments explaining what this system does? Do we do a bunch of image build work (numpy/six/mako install) on each Travis build, or does it get cached? Do I need to do any setup in Travis in order for this to take effect?
signature.asc
Description: PGP signature
_______________________________________________ Piglit mailing list Piglit@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/piglit
