On 6/14/14 2:34 AM, Takashi Sato wrote:
+1
How about automated test?
http://svn.apache.org/repos/asf/httpd/test/
Yes there should be automated testing that runs. But sadly that test suite is
pretty limited. It needs a lot of work and a commitment to adding regression
tests for bugs as we
This is pretty interesting. A project I work on, Traffic Server, needs to
improve the test infrastructure as well. In particular we need better
integration and end-to-end tests. It feels there ought to be significant
overlap here between ATS and HTTPD? Maybe we could pool development efforts?
Does it make sense to setup a CI for the 2.4 branch and
trunk builds of httpd such that after each commit, the system
makes sure that it at least builds?
I know I am guilty of making and committing simple changes
w/o a local test build, which, unfortunately, have typos
which cause the build to
+1
Regards
Rüdiger
-Ursprüngliche Nachricht-
Von: Jim Jagielski [mailto:j...@jagunet.com]
Gesendet: Freitag, 13. Juni 2014 16:06
An: httpd
Betreff: CI for httpd 2.4 and trunk?
Does it make sense to setup a CI for the 2.4 branch and
trunk builds of httpd such that after each
+1
On Fri, Jun 13, 2014 at 4:05 PM, Jim Jagielski j...@jagunet.com wrote:
Does it make sense to setup a CI for the 2.4 branch and
trunk builds of httpd such that after each commit, the system
makes sure that it at least builds?
I know I am guilty of making and committing simple changes
w/o
+1 as well
Le 13/06/2014 16:05, Jim Jagielski a écrit :
Does it make sense to setup a CI for the 2.4 branch and
trunk builds of httpd such that after each commit, the system
makes sure that it at least builds?
I know I am guilty of making and committing simple changes
w/o a local test build,
+1
How about automated test?
http://svn.apache.org/repos/asf/httpd/test/
And I want CI for doc build (at least validate-xml).
