Need advice about which tool to choose?Ask the StackShare community!

Appveyor

125
131
+ 1
94
LambCI

4
13
+ 1
0
Add tool

Appveyor vs LambCI: What are the differences?

Appveyor: Continuous Integration and Deployment service for busy Windows developers. 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; LambCI: A continuous integration system built on AWS Lambda. LambCI is a package you can upload to AWS Lambda that gets triggered when you push new code or open pull requests on GitHub and runs your tests (in the Lambda environment itself) – in the same vein as Jenkins, Travis or CircleCI.

Appveyor and LambCI can be primarily classified as "Continuous Integration" tools.

LambCI is an open source tool with 3.6K GitHub stars and 210 GitHub forks. Here's a link to LambCI's open source repository on GitHub.

Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of Appveyor
Pros of LambCI
  • 20
    Github integration
  • 18
    Simple, reliable & powerful
  • 12
    Hosted
  • 11
    YML-based configuration
  • 10
    Nuget support
  • 6
    Windows support
  • 4
    Free for open source
  • 4
    Automatic deployment
  • 3
    Great product, responsive people, free for open-source
  • 2
    Easy PowerShell support
  • 2
    Easy handling of secret keys
  • 1
    Remote Desktop into Build Worker
  • 1
    Advanced build workers available
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    Cons of Appveyor
    Cons of LambCI
    • 1
      Complex user interface
    • 1
      Poor documentation
      Be the first to leave a con

      Sign up to add or upvote consMake informed product decisions

      - No public GitHub repository available -

      What is Appveyor?

      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.

      What is LambCI?

      LambCI is a package you can upload to AWS Lambda that gets triggered when you push new code or open pull requests on GitHub and runs your tests (in the Lambda environment itself) – in the same vein as Jenkins, Travis or CircleCI.

      Need advice about which tool to choose?Ask the StackShare community!

      Jobs that mention Appveyor and LambCI as a desired skillset
      What companies use Appveyor?
      What companies use LambCI?
        No companies found
        Manage your open source components, licenses, and vulnerabilities
        Learn More

        Sign up to get full access to all the companiesMake informed product decisions

        What tools integrate with Appveyor?
        What tools integrate with LambCI?

        Sign up to get full access to all the tool integrationsMake informed product decisions

        What are some alternatives to Appveyor and LambCI?
        TeamCity
        TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.
        Jenkins
        In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
        CircleCI
        Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.
        Azure DevOps
        Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support.
        GitLab
        GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.
        See all alternatives