Changes between Version 4 and Version 5 of AppVeyor
- Timestamp:
- Jan 17, 2016, 8:32:16 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
AppVeyor
v4 v5 1 1 = !AppVeyor - Continuous Integration service for Windows 2 2 3 //[http://www.appveyor.com/ 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 !AppVeyor is a continuous integration service for Windows. From their website: 4 5 //[http://www.appveyor.com/ 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.// 4 6 5 7 They offer their service free of charge for Open Source projects, like Trac. 6 8 7 We use it for automating our builds on Windows (see TracDev/AutomaticBuilds for the other automated build services we use).9 We use it for automating our builds on Windows. See TracDev/AutomaticBuilds for the other automated build services we use. 8 10 9 11 It works together with the git repositories hosted on GitHub, like our mirror and their forks: 10 - Builds for the [https://ci.appveyor.com/project/edgewall/trac Trac mirror] (not yet active) 12 - Builds for the [https://ci.appveyor.com/project/edgewall/trac Trac mirror] (not yet active). 11 13 - Builds for developer branches: 12 [https://ci.appveyor.com/project/cboos/trac cboos], ... 14 [https://ci.appveyor.com/project/cboos/trac cboos], ... . 13 15 14 16 == Settings … … 26 28 Another useful tip is that a build [http://www.appveyor.com/docs/how-to/skip-build can be skipped] if the last changeset pushed contains `[skip ci]` in its commit log message. 27 29 28 29 30 == Known issues 30 31 … … 33 34 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. 34 35 35 See all [kwquery:appveyor ] related tickets.36 See all [kwquery:appveyor related tickets]. 36 37 37 Note that if you 're on Windows, you can reproduce the build locally the same way AppVeyor would do it, from a !PowerShell console.38 Note that if you are on Windows, you can reproduce the build locally the same way AppVeyor would do it, from a !PowerShell console. 38 39 39 Note that you may need to first enable sourcing local scripts, in that shell .40 Note that you may need to first enable sourcing local scripts, in that shell: 40 41 41 42 {{{#!ps1 … … 46 47 > $env:TEST_TRAC_DB_URI = 'sqlite:test.py' # example 47 48 > $env:APPVEYOR_REPO_BRANCH = '1.0-stable' 48 > $DebugPreference = "Continue" # in orderto see the Appveyor API calls49 > $DebugPreference = "Continue" # to see the Appveyor API calls 49 50 > Trac-Install 50 51 > Trac-Build … … 52 53 }}} 53 54 54 55 55 === Project not building 56 56 57 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 57 It can happen that the build won't trigger, and no matter what you do about it, the jobs stay in the "queued" state forever instead of just a few minutes. 58 58 59 59 If this happens, [mailto:team@appveyor.com ask the support] to do a global reset on the project. They're very friendly and responsive.
