Edgewall Software

Changes between Version 10 and Version 11 of AppVeyor


Ignore:
Timestamp:
Jan 28, 2017, 11:01:47 AM (3 years ago)
Author:
Christian Boos
Comment:

proofreading

Legend:

Unmodified
Added
Removed
Modified
  • AppVeyor

    v10 v11  
     1[[Image(wiki:TracDev/AutomaticBuilds:appveyor-kb-logo.png, align=right)]]
     2
    13= !AppVeyor - Continuous Integration service for Windows
    24
    3 [[Image(wiki:TracDev/AutomaticBuilds:appveyor-kb-logo.png, align=right)]]
    4 
    5 !AppVeyor is a continuous integration service for Windows. From their website:
     5!AppVeyor is a continuous integration service for Windows. \\
     6From their website:
    67
    78 //[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.//
     
    1415 - Builds for the branches in the [https://ci.appveyor.com/project/edgewall-org/trac Trac mirror]
    1516 - Builds for developer topic branches:
    16    [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]
     17   [https://ci.appveyor.com/project/cboos/trac/history cboos],
     18   [https://ci.appveyor.com/project/rjollos/trac/history rjollos],
     19   [https://ci.appveyor.com/project/jun66j5/trac/history jomae]
    1720
    1821== Settings
     
    3841See all [kwquery:appveyor related tickets].
    3942
    40 If you are on Windows, you can reproduce the build locally the same way AppVeyor would do it, from a !PowerShell console.
     43If 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.
    4144
    4245Note that you may need to perform a few preparation steps first in that shell:
    43  - enable sourcing local scripts by setting the execution policy to "unrestricted",
    44  - make a **backup** of your Makefile.cfg if you have it customized (as it will be created by the scripts)
    45  - make sure you have GNU `make.exe` in the Path (grab [http://sourceforge.net/projects/ezwinports/ ezmake] for example)
     46 - enable sourcing local scripts by setting the //execution policy// to "//unrestricted//",
     47 - **backup** your Makefile.cfg if you have customized it, as it will be overwritten by the scripts
     48 - 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])
    4649 - set the environment variables that are normally set up by the "build matrix" in the configuration file, i.e.
    4750    - `PYTHONHOME`, to point to the Python version you want to use
    48     - `TEST_TRAC_DB_URI`, as usual (see TracDev/UnitTests)
     51    - `TEST_TRAC_DB_URI`, as usual (see TracDev/UnitTests for details)
    4952    - `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`)
    5053
     
    5255{{{#!ps1
    5356> cd 1.0-stable
    54 > cp Makefile.cfg Makefile.cfg.custom # if needed...
     57> cp Makefile.cfg Makefile.cfg.custom  # better safe than sorry...
    5558> Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
    56 > $env:PATH = "$($env:PATH);C:/Dev/ez-make-4.1/bin" # example
    57 > $env:PYTHONHOME = 'C:\Python27'          # example
    58 > $env:TEST_TRAC_DB_URI = 'sqlite:test.py' # example
    59 > $env:SVN_BRANCH = '1.0-stable' 
    60 > $DebugPreference = "Continue"            # to see the Appveyor API calls
    61 > . .\contrib\appveyor.ps1
    62 > Trac-Install
    63 > Trac-Build
    64 > Trac-Tests
     59> $env:PATH = "$($env:PATH);C:/Dev/ez-make-4.1/bin"  # example
     60> $env:PYTHONHOME = 'C:\Python27'                    # example
     61> $env:TEST_TRAC_DB_URI = 'sqlite:test.py'           # example
     62> $env:SVN_BRANCH = '1.0-stable'
     63> $DebugPreference = "Continue"        # to see the Appveyor API calls
     64> . .\contrib\appveyor.ps1             # load the Trac-* functions
     65> Trac-Install                         #  - installs dependent software
     66> Trac-Build                           #  - creates DB, `make compile`
     67> Trac-Tests                           #  - `make unit-test`, `make functional-test`
    6568}}}
    6669
     
    7073
    7174If this happens, [mailto:team@appveyor.com ask the support] to do a global reset on the project. They're very friendly and responsive.
     75
     76But frankly, this happened once at the very beginning, when setting up the automatic builds. Since then, it's running flawlessly.