Jenkins vs rkt

Overview

Jenkins

Stacks59.2K

Followers50.4K

Votes2.2K

GitHub Stars24.6K

Forks9.2K

rkt

Stacks29

Followers112

Votes10

Jenkins vs rkt: What are the differences?

Developers describe Jenkins 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. On the other hand, rkt is detailed as "App Container runtime". Rocket is a cli for running App Containers. The goal of rocket is to be composable, secure, and fast.

Jenkins and rkt are primarily classified as "Continuous Integration" and "Virtual Machine Platforms & Containers" tools respectively.

Some of the features offered by Jenkins are:

Easy installation
Easy configuration
Change set support

On the other hand, rkt provides the following key features:

Composable. All tools for downloading, installing, and running containers should be well integrated, but independent and composable.
Security. Isolation should be pluggable, and the crypto primitives for strong trust, image auditing and application identity should exist from day one.
Image distribution. Discovery of container images should be simple and facilitate a federated namespace, and distributed retrieval. This opens the possibility of alternative protocols, such as BitTorrent, and deployments to private environments without the requirement of a registry.

"Hosted internally" is the primary reason why developers consider Jenkins over the competitors, whereas "Security" was stated as the key factor in picking rkt.

Jenkins and rkt are both open source tools. Jenkins with 13.3K GitHub stars and 5.48K forks on GitHub appears to be more popular than rkt with 8.71K GitHub stars and 832 GitHub forks.

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 Jenkins, rkt

Balaramesh

Apr 20, 2020

Needs adviceon

Azure Pipelines

.NET

Jenkins

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

663k views663k

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?"

530k views530k

Comments

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

Jenkins	rkt
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.	Rocket is a cli for running App Containers. The goal of rocket is to be composable, secure, and fast.
Easy installation;Easy configuration;Change set support;Permanent links;RSS/E-mail/IM Integration;After-the-fact tagging;JUnit/TestNG test reporting;Distributed builds;File fingerprinting;Plugin Support	Composable. All tools for downloading, installing, and running containers should be well integrated, but independent and composable.;Security. Isolation should be pluggable, and the crypto primitives for strong trust, image auditing and application identity should exist from day one.;Image distribution. Discovery of container images should be simple and facilitate a federated namespace, and distributed retrieval. This opens the possibility of alternative protocols, such as BitTorrent, and deployments to private environments without the requirement of a registry.;Open. The format and runtime should be well-specified and developed by a community. We want independent implementations of tools to be able to run the same container consistently.
Statistics
GitHub Stars 24.6K	GitHub Stars -
GitHub Forks 9.2K	GitHub Forks -
Stacks 59.2K	Stacks 29
Followers 50.4K	Followers 112
Votes 2.2K	Votes 10
Pros & Cons
Pros 523 Hosted internally 469 Free open source 318 Great to build, deploy or launch anything async 243 Tons of integrations 211 Rich set of plugins with good documentation Cons 13 Workarounds needed for basic requirements 10 Groovy with cumbersome syntax 8 Plugins compatibility issues 7 Limited abilities with declarative pipelines 7 Lack of support	Pros 5 Security 3 Robust container portability 2 Composable containers

What are some alternatives to Jenkins, rkt?

Docker

The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere

Travis CI

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.

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.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Related Comparisons

Bitbucket vs GitHub vs GitLab

AWS CodeCommit vs Bitbucket vs GitHub

Docker Swarm vs Kubernetes vs Rancher

Grunt vs Webpack vs gulp

Grafana vs Graphite vs Kibana

Jenkins vs rkt: What are the differences?

Jenkins and rkt are primarily classified as "Continuous Integration" and "Virtual Machine Platforms & Containers" tools respectively.

Some of the features offered by Jenkins are:

Easy installation
Easy configuration
Change set support

On the other hand, rkt provides the following key features:

Composable. All tools for downloading, installing, and running containers should be well integrated, but independent and composable.
Security. Isolation should be pluggable, and the crypto primitives for strong trust, image auditing and application identity should exist from day one.
Image distribution. Discovery of container images should be simple and facilitate a federated namespace, and distributed retrieval. This opens the possibility of alternative protocols, such as BitTorrent, and deployments to private environments without the requirement of a registry.

"Hosted internally" is the primary reason why developers consider Jenkins over the competitors, whereas "Security" was stated as the key factor in picking rkt.

Jenkins and rkt are both open source tools. Jenkins with 13.3K GitHub stars and 5.48K forks on GitHub appears to be more popular than rkt with 8.71K GitHub stars and 832 GitHub forks.