StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Continuous Integration
  4. Continuous Integration
  5. Gogs vs Travis CI

Gogs vs Travis CI

OverviewDecisionsComparisonAlternatives

Overview

Travis CI
Travis CI
Stacks28.0K
Followers6.7K
Votes1.7K
Gogs
Gogs
Stacks175
Followers306
Votes182

Gogs vs Travis CI: What are the differences?

Developers describe Gogs as "A self-hosted Git service written in Go". The goal of this project is to make the easiest, fastest and most painless way to set up a self-hosted Git service. With Go, this can be done in independent binary distribution across ALL platforms that Go supports, including Linux, Mac OS X, and Windows. On the other hand, Travis CI is detailed as "A hosted continuous integration service for open source and private projects". 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.

Gogs can be classified as a tool in the "Code Collaboration & Version Control" category, while Travis CI is grouped under "Continuous Integration".

Some of the features offered by Gogs are:

  • Activity timeline
  • SSH/HTTP(S) protocol support
  • SMTP/LDAP/reverse proxy authentication support

On the other hand, Travis CI provides the following key features:

  • 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.

"Self-hosted github like service" is the primary reason why developers consider Gogs over the competitors, whereas "Github integration" was stated as the key factor in picking Travis CI.

Gogs is an open source tool with 30.8K GitHub stars and 3.56K GitHub forks. Here's a link to Gogs's open source repository on GitHub.

Lyft, Heroku, and Rainist are some of the popular companies that use Travis CI, whereas Gogs is used by Write.as, OSInet, and GameDuell. Travis CI has a broader approval, being mentioned in 670 company stacks & 624 developers stacks; compared to Gogs, which is listed in 9 company stacks and 10 developer stacks.

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)
or
Manual

Advice on Travis CI, Gogs

Felipe
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
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
Tatiana
Tatiana

Nov 16, 2019

Decided

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

734k views734k
Comments

Detailed Comparison

Travis CI
Travis CI
Gogs
Gogs

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.

The goal of this project is to make the easiest, fastest and most painless way to set up a self-hosted Git service. With Go, this can be done in independent binary distribution across ALL platforms that Go supports, including Linux, Mac OS X, and Windows.

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.
Activity timeline;SSH/HTTP(S) protocol support;SMTP/LDAP/reverse proxy authentication support;Register/delete/rename account;Create/migrate/mirror/delete/watch/rename/transfer public/private repository;Repository viewer/release/issue tracker/webhooks;Add/remove repository collaborators;Gravatar and cache support;Mail service(register, issue);Administration panel;Supports MySQL, PostgreSQL and SQLite3;Social account login(GitHub, Google, QQ, Weibo)
Statistics
Stacks
28.0K
Stacks
175
Followers
6.7K
Followers
306
Votes
1.7K
Votes
182
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
  • 36
    Self-hosted github like service
  • 31
    Very low memory footprint
  • 29
    Easy to install / update
  • 17
    Lightweight (low minimal req.) runs on Raspberry pi
  • 16
    Single binary deploy no dependencies
Integrations
Amazon S3
Amazon S3
Heroku
Heroku
AWS CodeDeploy
AWS CodeDeploy
MySQL
MySQL
Red Hat OpenShift
Red Hat OpenShift
Nodejitsu
Nodejitsu
npm
npm
GitHub
GitHub
Engine Yard Cloud
Engine Yard Cloud
cloudControl
cloudControl
No integrations available

What are some alternatives to Travis CI, Gogs?

GitHub

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

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

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

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

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

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

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.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

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

RhodeCode

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

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana