-
Notifications
You must be signed in to change notification settings - Fork 8
Wget: Continuous Integration
Wget needs more and frquest tests on multiple platforms and over various option permutations. We already have a test suite that covers a significant percentage of possible issues, but not all of them.
| Platform | Continuous Integration | Status | Comments |
|---|---|---|---|
| Linux | Travis-CI | Complete | |
| OSX | Travis-CI | Not Started | Python needs some extra work |
| Windows | Appveyor | Not Started | Next target |
| BSD | N/a | Need to look for one. FreeBSD? | Send an email soon |
| Solaris | Dagobert's Build Farm | Complete | |
| VMS | N/a | No Idea |
Extending the current Travis setup for OSX will be hard. Since Python is not available by default on the OSX images, and requires some manual steps to get it working.
I recently spoke to a few developers from FreeBSD, and they stated that FreeBSD has a couple of Build Farms that run 24x7 to ensure that various software is ported correctly to and compiles well on BSD machines. We could ask them for a slot for Wget to ensure proper running of Wget on those machines too.
Recently, I've also found out that GNU has access to a CI system that can test on Linux, Windows, BSD and Solaris. Need to look into that too
We currently have LLVM's Static Analyzer running on Wget's code base daily on Daniel's server. The mailing list requires more visibility about that.
Maintain a coverity branch on GitHub. On merging, it will fire a coverity scan. However setting up the token and scan hooks is complex and will take some effort