AppVeyor vs Travis CI

What AppVeyor is

AppVeyor is a hosted continuous-integration service with YAML or UI build configuration, build matrices, hosted workers and bring-your-own-cloud workers. Its public free tier is scoped to open-source projects; private-project allowances, concurrent jobs and self-hosted job capacity vary by paid plan.

What Travis CI is

Travis CI runs repository-defined build, test and deployment jobs from a .travis.yml configuration. Current purchasing options include usage-based credits, fixed-concurrency subscriptions and Travis CI Enterprise Server; job cost, available virtual machines and queue behavior depend on the selected plan and execution environment.

What AppVeyor is built to do

YAML or UI configuration

Defines the pipeline in appveyor.yml or through project settings, with documented precedence rules.

Build matrix

Expands selected environment dimensions into separate build jobs.

Build workers

Runs jobs on hosted environments or qualifying self-hosted and BYOC capacity.

Secure variables

Encrypts secret values for YAML and restricts their default use in pull-request builds.

What Travis CI is built to do

.travis.yml pipelines

Stores primary build configuration with the repository in YAML.

Hosted build jobs

Runs selected jobs in temporary environments under plan and virtual-machine rules.

Usage or concurrency billing

Supports credit consumption or fixed concurrency with excess jobs queued.

Pull-request security settings

Controls whether selected encrypted variables or SSH keys reach fork-originated builds.

Choose AppVeyor if

• Open-source projects that fit the public-project free tier and one hosted concurrent job
• Teams expressing multi-environment builds through a repository YAML file
• Organizations combining hosted CI control with their own worker infrastructure

Skip AppVeyor if

• A private project must remain on a free hosted plan
• Required concurrent or self-hosted capacity exceeds the acceptable subscription cost
• Your scripts cannot be hardened to fail reliably and keep secrets out of logs

Choose Travis CI if

• Projects that want build configuration versioned in .travis.yml
• Teams able to forecast credit consumption or required concurrent jobs
• Maintainers prepared to separate trusted deployment jobs from untrusted pull-request checks

Skip Travis CI if

• Neither current credit pricing nor fixed-concurrency pricing fits the workload
• Forked pull requests require secrets that security policy should not expose
• The required operating system, architecture or virtual-machine capacity is unavailable on the selected plan

AppVeyor: pros & cons

• Repository configuration: Builds can be defined in appveyor.yml and carried with the source repository.
• Build matrices: Creates jobs across selected operating systems, platforms, configurations and environment variables.
• Hosted and self-hosted execution: Pricing documents Windows, Linux and macOS options plus BYOC workers.
• Secret variables: Account-specific encryption supports protected values in visible YAML files.
• Narrow free scope: The listed free plan is for unlimited public open-source projects, not private repositories.
• Concurrency queue: Jobs beyond the plan's concurrent-job allowance wait for capacity.
• Plan limits: Private projects, concurrent hosted jobs and simultaneous self-hosted jobs differ by tier.
• Script error handling: AppVeyor warns that PowerShell non-terminating errors can leave a build reported as successful unless configured to stop.

Travis CI: pros & cons

• Repository-owned configuration: Uses .travis.yml as the primary build configuration language.
• Plan choice: Offers usage-credit and fixed-concurrency approaches for different workload shapes.
• Ephemeral jobs: Hosted build environments are removed after a job completes.
• Pull-request controls: Documents how encrypted variables and SSH keys behave for fork-originated builds.
• Cost forecasting: Usage plans consume credits according to job duration and virtual-machine type.
• Queueing: Jobs wait when the account reaches its selected concurrency limit.
• Secret-dependent fork tests: External pull requests may not receive encrypted variables, depending on repository security settings.
• Configuration ownership: Teams must maintain YAML, conditions, credentials and deployment behavior as the project changes.