April 13, 2015

Pro environment upgrade and data center migration

Pro environment build servers have been upgraded with faster hardware. Build workers are featuring the latest Xeon 2690 v3 (Haswell) processors and have 2,500 MB of RAM.

Also, to fix connectivity issues with GitHub build servers were moved to a San-Jose SoftLayer data center.

If you even configured firewall to allow deployments from build workers please update its settings with new build worker IPs:

169.54.128.0/27
169.54.128.128/27

Enjoy!

April 04, 2015

AppVeyor 2.5.5

What’s new

  • #22 Unzip artifacts before uploading to Azure Storage deployment (documentation).
  • #204 Build worker reboot.
  • #207 New: API method to clear project build cache (documentation).
  • #208 Do not fail entire NuGet deployment if symbolsource.org is down.
  • #209 Fixed: GitHub Releases deployment provider fails on invalid auth_token.
  • #210 Add nuget delete command sample to account NuGet page.
  • #218 Delete and create scenario for Azure Cloud Service deployment provider - recreate Azure Cloud Service deployment instead of update. Could be enabled on UI or in appveyor.yml with recreate_deployment: true. Default is false - update mode.
  • #222 Added –non-interactive –trust-server-cert to svn checkout command.
  • #224 Alternative implementation of FTP provider (documentation).

Build worker updates

  • io.js 1.6.2, io.js 1.6.3 x86 and x64 added. Use Install-Product node 1 cmdlet to switch runtime to the latest io.js version.
  • Node.js 0.10.38, Node.js 0.12.2 x86 and x64 added. Use Install-Product node 0 cmdlet to switch runtime to the latest Node.js version or Install-Product node 0.10 to the latest 0.10.x build.
    • Node.js 0.10.38 x86 is default Node.js in PATH
  • Azure SDK 2.5.1
  • Microsoft Visual Studio Installer Projects extension installed (.vdproj support).
  • Bundler 1.9.2 is pre-installed to all Rubies.
  • Python 2.7.9 replaces Python 2.7.8 in C:\Python27 and C:\Python27-x64.
  • Python 3.4.3 replaces Python 3.4.1 in C:\Python34 and C:\Python34-x64.

Previous worker images

There are build worker images available from previous deployment. You can use them in case of any issues with the current images:

  • Previous Windows Server 2012 R2
  • Previous Unstable
  • Previous Visual Studio 2014 CTP4
  • Previous Visual Studio 2015 CTP
  • Previous Visual Studio 2015 CTP 6
  • Previous Visual Studio 2015 Preview
  • Previous MinGW

You can select build worker image in OS dropdown on Environment tab of project settings or if you use appveyor.yml:

os: Previous Windows Server 2012 R2

Note to “Pro” customers: Whenever custom build worker image is chosen the build will run on Azure, so there is about 3-4 minutes delay before build starts to provision build worker virtual machine.

March 21, 2015

AppVeyor 2.5.4

What’s new

  • #175 Commit message indentation is not retained.
  • #177 Fixed: Slash is not supported in build version number.
  • #180 Trigger new builds on Visual Studio Online fast forward commits and tag pushes.
  • #181 Fixed: Install-product cmdlet is broken on new Node.js or io.js releases.
  • #183 Slack incoming webhooks support. In appveyor.yml Slask notification provider could be configured to use incoming webhook:

    ```yaml

    • provider: Slack incoming_webhook: http://incoming-webhook-url

    # …or as before using auth token

    • provider: Slack auth_token: secure: kBl9BlxvRMr9liHmnBs14A== channel: development ```
  • #184 Agent environment settings are sortable now with drag and drop.
  • #187 Added “Tag name” (tag) setting to GitHub deployment provider for separate tag and release name templates.
  • #188 New NuGet deployment provider:
    • Does not rely on nuget.exe
    • Retries pushing package if 500 response status received
    • Does not fail if package already exists
  • #189 Increase file name column on Artifacts page of build results
  • #190 New environment variables to distinguish forced and repetitive builds:
    • APPVEYOR_FORCED_BUILD (True or undefined) - builds started by “New build” button or from the same API.
    • APPVEYOR_RE_BUILD (True or undefined) - build started by “Re-build commit/PR” button of from the same API.
  • #191 Display build/job start and end times in popup hint over status message.
  • #192 Fixed: “Access is denied” when restoring build cache over read-only items.
  • #193 Azure build worker should use build cache from the same region.
  • #195 Deployment agent: Add skip_dirs, skip_files to “Windows Application” deployment.
  • #197 Fixed: Build cache update fails for dependencies with very long path.
  • #198 Build email notifications are off by default for newly added user/collaborator.
  • #203 Fixed: Web Deploy provider deploying from zip fails on very long paths

Build worker updates

  • io.js 1.6.1 x86 and x64 added. Use Install-Product node 1 cmdlet to switch runtime to the latest io.js version.
  • Node.js 0.10.37 x86 and x64 added. Use Install-Product node 0 cmdlet to switch runtime to the latest Node.js version or Install-Product node 0.10 to the latest 0.10.x build.
    • Node.js 0.10.37 x86 is default Node.js in PATH
  • xUnit 2.0 runners updated to the latest 2.0.0 RTM.

Previous worker images

There are build worker images available from previous deployment. You can use them in case of any issues with the current images:

  • Previous Windows Server 2012 R2
  • Previous Unstable
  • Previous Visual Studio 2014 CTP4
  • Previous Visual Studio 2015 CTP
  • Previous Visual Studio 2015 CTP 6
  • Previous Visual Studio 2015 Preview
  • Previous MinGW

You can select build worker image in OS dropdown on Environment tab of project settings or if you use appveyor.yml:

os: Previous Windows Server 2012 R2

Note to “Pro” customers: Whenever custom build worker image is chosen the build will run on Azure, so there is about 3-4 minutes delay before build starts to provision build worker virtual machine.

March 06, 2015

AppVeyor 2.5.0

What’s new

  • #129 Custom <something>.yml file for project configuration. Now you can specify your own name of .yml file on “General” tab of project settings - it will be used instead of appveyor.yml.
  • #131 Added environment variable support in build.project setting, so you can setup solution or project name to build in environment variable, for example:

    ```yaml environment: my_project: MyApp.sln

    build: project: $(my_project) ```

  • #149 Billing details update form. It includes company name, billing address and VAT number.
  • #148 Billing email address could be changed on Plan page. If not specific account owner’s email is used to sent billing emails.
  • #151 Add an option to Deployment Agent to skip deployment of the same version.
  • #152 Added open-source plans to order page.
  • #164 Asynchronous processing of all webhooks
  • #168 Added caching for build status badges
  • Fixed #162: Build console line is hidden behind fixed header when navigated by its anchor
  • Fixed #165: Cache dependency is not used during the first build
  • Fixed #166: Not the latest commit is getting built in VSO Git push
  • Fixed #167: Increase build cache blob container SAS life-time to 4 hours
  • Fixed #171: Racing condition in VSO token refresh causes token invalidation bug

Build worker updates

  • io.js 1.5.0, io.js 1.4.2 and io.js 1.4.3 both x86 and x64 added. Use Install-Product node 1 cmdlet to switch runtime to the latest io.js version.
  • Ruby 2.0.0 updated to build p643.
  • Ruby 2.2.1 installed:
    • x86 - C:\Ruby22
    • x64 - C:\Ruby22-x64
  • Chocolatey 0.9.8.33
  • Chrome 41.0.2272.87
  • Selenium testing:
    • Chrome WebDriver updated to 2.14
    • IE WebDriver updated to 2.45
  • Erlang OTP runtime 17.4 x64 installed into C:\Program Files\erl6.3
    • ERLANG_HOME set to C:\Program Files\erl6.3
    • C:\Program Files\erl6.3\bin added to PATH
  • AWS SDK and Tools 2.3.24.3

Previous worker images

There are build worker images available from previous deployment. You can use them in case of any issues with the current images:

  • Previous Windows Server 2012 R2
  • Previous Unstable
  • Previous Visual Studio 2014 CTP4
  • Previous Visual Studio 2015 CTP
  • Previous Visual Studio 2015 CTP 6
  • Previous Visual Studio 2015 Preview
  • Previous MinGW

You can select build worker image in OS dropdown on Environment tab of project settings or if you use appveyor.yml:

os: Previous Windows Server 2012 R2

Note to “Pro” customers: Whenever custom build worker image is chosen the build will run on Azure, so there is about 3-4 minutes delay before build starts to provision build worker virtual machine.

February 26, 2015

AppVeyor 2.4.22

What’s new

  • -IncludeReferencedProjects option support during automatic packaging of NuGet artifacts. There is a new Include referenced projects setting on Build tab of project settings and build.include_nuget_references: true|false in appveyor.yml
  • Deployment Agent: For Windows services deploy.ps1 is now run before service is started, so you have an ability to update its app.config.
  • Deployment Agent: For Windows services service_username and service_password settings added to set custom user account to run service under.
  • Pseudo multi-line support in description field of GitHub deployment provider. You can use \n symbol to separate lines in release description which will be replaced with real LF symbol during deployment.
  • Fixed “Object reference not set…” exception when starting a new build with insufficient GitHub/BitBucket permissions.
  • SSH public key is always displayed for all private projects.
  • Credit card on file can now be updated on Plan page.
  • Default notifications mode for newly added users/collaborators is “Builds with my commits only”.
  • Added new Enable deployments in Pull Requests project option for private GitHub projects.

Build worker updates

  • io.js 1.3.0 and io.js 1.4.1 both x86 and x64 added. Use Install-Product node 1 cmdlet to switch runtime to the latest io.js version.
  • Coverity Scan Build Tool 7.6.0 x64 was added to all workers in C:\Tools\Coverity. C:\Tools\Coverity\bin added to PATH.
  • Updated xUnit 2.0 runners to 2.0.0-rc3-build2880
  • Go 1.4.2 x64 made default installation in C:\go path.
    • Go 1.4.2 x86 moved to C:\go-x86
    • Added C:\go-x64 symbolic link to C:\go
    • Set GOROOT variable to C:\go

Previous worker images

There are build worker images available from previous deployment. You can use them in case of any issues with the current images:

  • Previous Windows Server 2012 R2
  • Previous Unstable
  • Previous Visual Studio 2014 CTP4
  • Previous Visual Studio 2015 CTP
  • Previous Visual Studio 2015 CTP 6
  • Previous Visual Studio 2015 Preview
  • Previous MinGW

You can select build worker image in OS dropdown on Environment tab of project settings or if you use appveyor.yml:

os: Previous Windows Server 2012 R2

Note to “Pro” customers: Whenever custom build worker image is chosen the build will run on Azure, so there is about 3-4 minutes delay before build starts to provision build worker virtual machine.