Changes between Version 10 and Version 11 of AppVeyor

Timestamp:

Jan 28, 2017, 11:01:47 AM (7 years ago)

Author:

Christian Boos

Comment:

proofreading

AppVeyor

@@ +1 @@
+[[Image(wiki:TracDev/AutomaticBuilds:appveyor-kb-logo.png, align=right)]]
+
 = !AppVeyor - Continuous Integration service for Windows
 
-[[Image(wiki:TracDev/AutomaticBuilds:appveyor-kb-logo.png, align=right)]]
-
-!AppVeyor is a continuous integration service for Windows. From their website:
+!AppVeyor is a continuous integration service for Windows. \\
+From their website:
 
  //[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.//
@@ -14 +15 @@
  - Builds for the branches in the [https://ci.appveyor.com/project/edgewall-org/trac Trac mirror]
  - Builds for developer topic branches:
-   [https://ci.appveyor.com/project/cboos/trac/history cboos], [https://ci.appveyor.com/project/rjollos/trac/history rjollos], [https://ci.appveyor.com/project/jun66j5/trac/history jomae]
+   [https://ci.appveyor.com/project/cboos/trac/history cboos],
+   [https://ci.appveyor.com/project/rjollos/trac/history rjollos],
+   [https://ci.appveyor.com/project/jun66j5/trac/history jomae]
 
 == Settings
@@ -38 +41 @@
 See all [kwquery:appveyor related tickets].
 
-If you are on Windows, you can reproduce the build locally the same way AppVeyor would do it, from a !PowerShell console.
+If you are on Windows, you can reproduce the build locally the same way AppVeyor would do it, from a !PowerShell console. In some cases, if the problem only happens on !AppVeyor build workers, it can be useful to [https://www.appveyor.com/docs/how-to/rdp-to-build-worker/ run the test manually there via RDP], the procedure is similar.
 
 Note that you may need to perform a few preparation steps first in that shell:
- - enable sourcing local scripts by setting the execution policy to "unrestricted", 
- - make a **backup** of your Makefile.cfg if you have it customized (as it will be created by the scripts)
- - make sure you have GNU `make.exe` in the Path (grab [http://sourceforge.net/projects/ezwinports/ ezmake] for example)
+ - enable sourcing local scripts by setting the //execution policy// to "//unrestricted//", 
+ - **backup** your Makefile.cfg if you have customized it, as it will be overwritten by the scripts
+ - make sure you have a GNU `make.exe` in the Path (grab [http://sourceforge.net/projects/ezwinports/ ezmake] for example; on !AppVeyor workers you have [https://www.appveyor.com/docs/installed-software/#mingw-msys-cygwin plenty of choice])
  - set the environment variables that are normally set up by the "build matrix" in the configuration file, i.e.
     - `PYTHONHOME`, to point to the Python version you want to use
-    - `TEST_TRAC_DB_URI`, as usual (see TracDev/UnitTests)
+    - `TEST_TRAC_DB_URI`, as usual (see TracDev/UnitTests for details)
     - `SVN_BRANCH`, to indicate the "base" branch (e.g. if you forked a topic branch from [source:cboos.git@1.0-stable 1.0-stable], set it to `1.0-stable`)
 
@@ -52 +55 @@
 {{{#!ps1
 > cd 1.0-stable
-> cp Makefile.cfg Makefile.cfg.custom # if needed...
+> cp Makefile.cfg Makefile.cfg.custom  # better safe than sorry...
 > Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
-> $env:PATH = "$($env:PATH);C:/Dev/ez-make-4.1/bin" # example
-> $env:PYTHONHOME = 'C:\Python27'          # example
-> $env:TEST_TRAC_DB_URI = 'sqlite:test.py' # example
-> $env:SVN_BRANCH = '1.0-stable' 
-> $DebugPreference = "Continue"            # to see the Appveyor API calls
-> . .\contrib\appveyor.ps1
-> Trac-Install
-> Trac-Build
-> Trac-Tests
+> $env:PATH = "$($env:PATH);C:/Dev/ez-make-4.1/bin"  # example
+> $env:PYTHONHOME = 'C:\Python27'                    # example
+> $env:TEST_TRAC_DB_URI = 'sqlite:test.py'           # example
+> $env:SVN_BRANCH = '1.0-stable'
+> $DebugPreference = "Continue"        # to see the Appveyor API calls
+> . .\contrib\appveyor.ps1             # load the Trac-* functions
+> Trac-Install                         #  - installs dependent software
+> Trac-Build                           #  - creates DB, `make compile`
+> Trac-Tests                           #  - `make unit-test`, `make functional-test`
 }}}
 
@@ -70 +73 @@
 
 If this happens, [mailto:team@appveyor.com ask the support] to do a global reset on the project. They're very friendly and responsive.
+
+But frankly, this happened once at the very beginning, when setting up the automatic builds. Since then, it's running flawlessly.