Changes between Version 5 and Version 6 of AppVeyor

Timestamp:

Jan 20, 2016, 8:10:54 PM (8 years ago)

Author:

Christian Boos

Comment:

add a few more tips and caveats for running the contrib/appveyor.ps1 script locally

AppVeyor

@@ -36 +36 @@
 See all [kwquery:appveyor related tickets].
 
-Note that 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.
 
-Note that you may need to first enable sourcing local scripts, in that shell:
+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)
+ - 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)
+    - `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`)
 
+For example:
 {{{#!ps1
 > cd 1.0-stable
+> cp Makefile.cfg Makefile.cfg.custom # if needed...
 > Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
 > . .\contrib\appveyor.ps1
+> $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:APPVEYOR_REPO_BRANCH = '1.0-stable' 
+> $env:SVN_BRANCH = '1.0-stable' 
 > $DebugPreference = "Continue"            # to see the Appveyor API calls
 > Trac-Install