Gitea vs Jenkins: What are the differences?
Developers describe Gitea as "A painless self-hosted Git service". Gitea is a community managed lightweight code hosting solution written in Go. It published under the MIT license. On the other hand, Jenkins is detailed as "An extendable open source continuous integration server". 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.
Gitea belongs to "Code Collaboration & Version Control" category of the tech stack, while Jenkins can be primarily classified under "Continuous Integration".
"Self-hosted" is the top reason why over 8 developers like Gitea, while over 497 developers mention "Hosted internally" as the leading cause for choosing Jenkins.
Gitea and Jenkins are both open source tools. Gitea with 14.4K GitHub stars and 1.56K forks on GitHub appears to be more popular than Jenkins with 13.2K GitHub stars and 5.43K GitHub forks.
Instacart, Lyft, and Twitch are some of the popular companies that use Jenkins, whereas Gitea is used by osu! Ripple, LunchBadger, and PlayNet. Jenkins has a broader approval, being mentioned in 1753 company stacks & 1479 developers stacks; compared to Gitea, which is listed in 8 company stacks and 10 developer stacks.
What is Gitea?
What is Jenkins?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to add, upvote and see more consMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
All of our pull requests are automatically tested using Jenkins' integration with GitHub, and we provision and deploy our servers using Jenkins' interface. This is integrated with HipChat, immediately notifying us if anything goes wrong with a deployment.
Jenkins is our go-to devops automation tool. We use it for automated test builds, all the way up to server updates and deploys. It really helps maintain our homegrown continuous-integration suite. It even does our blue/green deploys.
- Continuous Deploy
- Dev stage: autodeploy by trigger push request from 'develop' branch of Gitlab
- Staging and production stages: Build and rollback quicly with Ansistrano playbook
- Sending messages of job results to Chatwork.
Currently serves as the location that our QA team builds various automated testing jobs.
At one point we were using it for builds, but we ended up migrating away from them to Code Pipelines.
We use Jenkins to schedule our Browser and API Based regression and acceptance tests on a regular bases. We use additionally to Jenkins GitlabCI for unit and component testing.