On 09/17/2018 01:01 PM, Michael wrote: > On 12/09/2018 22:47, Jim Jagielski wrote: >> The idea is that people actually take the time to download the tarballs, >> build a version of httpd for their use and then perform testing on said >> version such that they can vote on whether to release it or not. That >> testing entails such activities as running it through our test framework, >> putting it in a dev/prod environment to see how it works, etc... That is a >> schema that we have had for... let me see... years and decades. > Curious. Does httpd work with buildbots as a way to test things. afaik > it works without git repositories - although most seem to. If yes, I > would be willing to dedicate some processing cycles from my server - > assuming I can get it working. > > As far as downloading tarballs, etc. - done that in the past (although i > am not a registered voter), but generally my 'results' are what the > dutch call "Mustard after the meal" aka "too late to have any utility". > > In short, if yes, or when it moves towards yes - willing to helpout. > > Michael > >
For a one specific build flavour: MSVC + CMake on 64bit WIndows, I maintain these, they poll Git daily: 2.4.x https://ci.modcluster.io/view/Windows/job/httpd-windows/ trunk https://ci.modcluster.io/view/Windows/job/httpd-trunk-windows/ (arbitrary GitHub account is needed to see the Jenkins) There is a trivial smoke test that loads all modules and tries HTTP and HTTPS. The job does not execute the httpd test suite -- it's on my spare time roadmap though... Build script: https://github.com/modcluster/ci.modcluster.io/blob/master/windows/httpd/build.bat Ad "Mustard after the meal", exactly what has been troubling me, so I stitched together this little Jenkins thing :-) Cheers K Michal Karm Babacek -- Sent from my Hosaka Ono-Sendai Cyberspace 7
signature.asc
Description: OpenPGP digital signature
