| | 1 | = [http://www.appveyor.com/ AppVeyor] - Continuous Integration service for Windows |
| | 2 | //AppVeyor aims to give powerful Continuous Integration and Deployment tools to every .NET developer without the hassle of setting up and maintaining their own build server.// |
| | 3 | |
| | 4 | They offer their service free of charge for Open Source projects, like Trac. |
| | 5 | |
| | 6 | We plan to use it soon for automating our builds on Windows (see TracDev/AutomaticBuilds for the other automated build services we use). |
| | 7 | |
| | 8 | Planned URL: https://ci.appveyor.com/project/edgewall/trac |
| | 9 | |
| | 10 | We'll also have an [source:trunk/.appveyor.yml .appveyor.yml] file, similar to our [source:trunk/.travis.yml .travis.yml] file. |
| | 11 | |
| | 12 | Currently experimenting in: https://ci.appveyor.com/project/cboos/trac |
| | 13 | |
| | 14 | == Known issues |
| | 15 | |
| | 16 | === Test failures |
| | 17 | |
| | 18 | There are still a number of test issues only seen on !AppVeyor that need to be resolved before getting a "green" build, mostly SQLite related. |
| | 19 | |
| | 20 | All [kwquery:appveyor] related tickets. |
| | 21 | |
| | 22 | === Project not building |
| | 23 | |
| | 24 | It can happen that the build won't trigger, and no matter what you do about it, the jobs stay in the "queued" state for ever instead of just a few minutes. |
| | 25 | |
| | 26 | If this happens, [mailto:team@appveyor.com ask the support] to do a global reset on the project. They're very friendly and responsive. |
