delta/curl.git - github.com: bagder/curl.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	travis: removed option to rebuild autotool from source	Sergei Nikulov	2016-08-03	1	-1/+1
\| \| \| \|	Fixes #943
*	travis: fix OSX build by re-installing libtool	Sergei Nikulov	2016-08-01	1	-0/+1
\| \| \| \| \| \| \|	Apparently due to a broken homebrew install fixes #934 Closes #939
*	Revert "travis: Install libtool for OS X builds"	Jay Satiro	2016-07-28	1	-1/+1
\| \| \| \| \| \|	Didn't work. This reverts commit 50723585ed380744358de054e2a55dccee65dfd7.
*	travis: Install libtool for OS X builds	Jay Satiro	2016-07-28	1	-1/+1
\| \| \| \|	CI is failing due to missing libtoolize, so I'm trying this.
*	travis.yml: Add OS X testbot.	Jactry Zeng	2015-08-21	1	-0/+8
\|
*	travis: Upgrading to container based build	Rémy Léone	2015-08-20	1	-0/+2
\| \| \| \| \| \|	http://docs.travis-ci.com/user/migrating-from-legacy Closes #388
*	.travis.yml: Change CI make test to make test-full	Jay Satiro	2015-03-10	1	-0/+2
\| \| \| \| \| \| \| \| \| \| \| \| \|	- Change the continuous integration script to use 'make test-full' instead of just 'make test' so that the diagnostic log output is printed to stdout when a test fails. - Change the continuous integration script to use './configure --enable-debug' instead of just './configure' so that the memory analyzer will work during testing. Prior to this change Travis used its default C test script: ./configure && make && make test
*	Adding a .travis.yml file to use the travis-ci.org	Rémy Léone	2013-10-21	1	-0/+11
	From wikipedia: Travis CI is a hosted, distributed continuous integration service used to build and test projects hosted at GitHub. Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the GitHub repository. Travis CI automatically detects when a commit has been made and pushed to a GitHub repository that is using Travis CI, and each time this happens, it will try to build the project and run tests. This includes commits to all branches, not just to the master branch. When that process has completed, it will notify a developer in the way it has been configured to do so — for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. It can be configured to run the tests on a range of different machines, with different software installed (such as older versions of a programming language, to test for compatibility).