Gitea vs Travis CI

Overview

Travis CI

Stacks28.0K

Followers6.7K

Votes1.7K

Gitea

Stacks323

Followers448

Votes123

GitHub Stars51.8K

Forks6.2K

Gitea vs Travis CI: What are the differences?

Integration with Git repositories: Gitea is a git repository management application that allows self-hosting, while Travis CI is a continuous integration service that integrates with GitHub. Gitea provides a platform for hosting and managing git repositories, whereas Travis CI focuses on automating the testing and deployment process.
Build and test automation: Travis CI automates the build and test process, providing a centralized tool for continuous integration, whereas Gitea offers a platform for code hosting and collaboration but lacks advanced automation features like Travis CI.
Community support and extensions: Gitea has a growing community of contributors and users, with an active development community supporting the project, while Travis CI is a well-established service with extensive integrations and plugins available, making it a comprehensive solution for CI/CD pipelines.
Deployment options: Travis CI offers deployment tools and integrations with popular cloud services for deploying applications, providing a seamless pipeline from code to production environments, while Gitea primarily focuses on code hosting and collaboration without extensive deployment features.
Scalability and customization: Gitea can be self-hosted and customized based on specific requirements, allowing for scalability and flexibility in managing git repositories, whereas Travis CI is a cloud-based service that may have limitations in customization and scalability for large projects.
User interface and user experience: Gitea provides a user-friendly interface for managing repositories, issues, and pull requests, making it easy for users to navigate and collaborate on projects, while Travis CI focuses on providing a streamlined interface for setting up and monitoring CI/CD pipelines, targeting developers and DevOps professionals.

In Summary, Gitea and Travis CI differ in their focus on git repository management and continuous integration, with Gitea serving as a self-hosted platform for code collaboration and Travis CI specializing in automating the build and test process for efficient deployment workflows.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Travis CI, Gitea

Kamaleshwar

Software Engineer at Dibiz Pte. Ltd.

Jul 8, 2020

Decided

Out of most of the VCS solutions out there, we found Gitlab was the most feature complete with a free community edition. Their DevSecops offering is also a very robust solution. Gitlab CI/CD was quite easy to setup and the direct integration with your VCS + CI/CD is also a bonus. Out of the box integration with major cloud providers, alerting through instant messages etc. are all extremely convenient. We push our CI/CD updates to MS Teams.

740k views740k

Comments

Felipe

May 24, 2020

Needs advice

My website is brand new and one of the few requirements of testings I had to implement was code coverage. Never though it was so hard to implement using a #docker container.
Given my lack of experience, every attempt I tried on making a simple code coverage test using the 4 combinations of #TravisCI, #CircleCi with #Coveralls, #Codecov I failed. The main problem was I was generating the .coverage file within the docker container and couldn't access it with #TravisCi or #CircleCi, every attempt to solve this problem seems to be very hacky and this was not the kind of complexity I want to introduce to my newborn website.
This problem was solved using a specific action for #GitHubActions, it was a 3 line solution I had to put in my github workflow file and I was able to access the .coverage file from my docker container and get the coverage report with #Codecov.

198k views198k

Comments

StackShare

Apr 17, 2019

Needs advice

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

529k views529k

Comments

Detailed Comparison

Travis CI	Gitea
Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.	Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD. It published under the MIT license.
Easy Setup- Getting started with Travis CI is as easy as enabling a project, adding basic build instructions to your project and committing code.;Supports Your Platform- Lots of databases and services are pre-installed and can simply be enabled in your build configuration, we'll launch them for you automatically. MySQL, PostgreSQL, ElasticSearch, Redis, Riak, RabbitMQ, Memcached are available by default.;Deploy With Confidence- Deploying to production after a successful build is as easy as setting up a bit of configuration, and we'll deploy your code to Heroku, Engine Yard Cloud, Nodejitsu, cloudControl, OpenShift, and CloudFoundry.	-
Statistics
GitHub Stars -	GitHub Stars 51.8K
GitHub Forks -	GitHub Forks 6.2K
Stacks 28.0K	Stacks 323
Followers 6.7K	Followers 448
Votes 1.7K	Votes 123
Pros & Cons
Pros 506 Github integration 388 Free for open source 271 Easy to get started 191 Nice interface 162 Automatic deployment Cons 8 Can't be hosted insternally 3 Feature lacking 3 Unstable 2 Incomplete documentation for all platforms	Pros 24 Self-hosted 16 Lightweight 15 Free 12 Simple 9 Multiple code maintainers Cons 3 Community-fork of Gogs 0 Easy Windows authentication is not supported
Integrations
Amazon S3 Heroku AWS CodeDeploy MySQL Red Hat OpenShift Nodejitsu npm GitHub Engine Yard Cloud cloudControl	Raspberry Pi DingTalk Discord OpenLDAP Drone.io Jenkins Vagrant MySQL SQLite PostgreSQL

What are some alternatives to Travis CI, Gitea?

GitHub

GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.

Bitbucket

Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.

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.

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.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

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.

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.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

RhodeCode

RhodeCode provides centralized control over distributed code repositories. Developers get code review tools and custom APIs that work in Mercurial, Git & SVN. Firms get unified security and user control so that their CTOs can sleep at night

Related Comparisons

Gitea vs Travis CI: What are the differences?

Integration with Git repositories: Gitea is a git repository management application that allows self-hosting, while Travis CI is a continuous integration service that integrates with GitHub. Gitea provides a platform for hosting and managing git repositories, whereas Travis CI focuses on automating the testing and deployment process.
Build and test automation: Travis CI automates the build and test process, providing a centralized tool for continuous integration, whereas Gitea offers a platform for code hosting and collaboration but lacks advanced automation features like Travis CI.
Community support and extensions: Gitea has a growing community of contributors and users, with an active development community supporting the project, while Travis CI is a well-established service with extensive integrations and plugins available, making it a comprehensive solution for CI/CD pipelines.
Deployment options: Travis CI offers deployment tools and integrations with popular cloud services for deploying applications, providing a seamless pipeline from code to production environments, while Gitea primarily focuses on code hosting and collaboration without extensive deployment features.
Scalability and customization: Gitea can be self-hosted and customized based on specific requirements, allowing for scalability and flexibility in managing git repositories, whereas Travis CI is a cloud-based service that may have limitations in customization and scalability for large projects.
User interface and user experience: Gitea provides a user-friendly interface for managing repositories, issues, and pull requests, making it easy for users to navigate and collaborate on projects, while Travis CI focuses on providing a streamlined interface for setting up and monitoring CI/CD pipelines, targeting developers and DevOps professionals.

Gitea vs Travis CI

Overview