Jenkins vs Shipit

Overview

Jenkins

Stacks59.2K

Followers50.4K

Votes2.2K

GitHub Stars24.6K

Forks9.2K

Shipit

Stacks49

Followers42

Votes6

GitHub Stars5.3K

Forks196

Jenkins vs Shipit: What are the differences?

1. **Architecture**: Jenkins is a self-contained, open-source automation server that can be used to automate all sorts of tasks. Shipit, on the other hand, is specifically designed for orchestrating and running deployment tasks. 2. **Extensibility**: Jenkins has a vast plugin ecosystem that allows users to extend its functionality for various use cases. Shipit, while extensible, has a limited plugin ecosystem tailored towards deployment tasks. 3. **Workflow**: Jenkins is more generalized and can be used for a variety of automation tasks including building, testing, and deploying software. Shipit, on the contrary, is focused on the deployment workflow and lacks extensive support for other automation tasks. 4. **Ease of Use**: Jenkins is known for its ease of use and user-friendly interface, making it popular among developers and DevOps teams. Shipit, while user-friendly, may require a steeper learning curve due to its focus on deployment-specific tasks. 5. **Community Support**: Jenkins has a large and active community that provides support, plugins, and continuous development. Shipit, being a more focused tool, has a smaller community but with expertise in deployment workflows. 6. **Integration with Platforms**: Jenkins has robust integrations with various platforms, tools, and services making it versatile for different environments. Shipit, being deployment-centric, may have limited integrations compared to Jenkins for other types of tasks.

In Summary, Jenkins and Shipit differ in architecture, extensibility, workflow focus, ease of use, community support, and integrations with platforms.

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, Shipit

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	Shipit
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.	Shipit is an automation engine and a deployment tool written for node / iojs. Shipit was built to be a Capistrano alternative for people who don't know ruby, or who experienced some issues with it. If you want to write tasks in JavaScript and enjoy the node ecosystem, Shipit is also for you.
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	-
Statistics
GitHub Stars 24.6K	GitHub Stars 5.3K
GitHub Forks 9.2K	GitHub Forks 196
Stacks 59.2K	Stacks 49
Followers 50.4K	Followers 42
Votes 2.2K	Votes 6
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 2 Agentless 2 Great configuration 2 Simple

What are some alternatives to Jenkins, Shipit?

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.

Ansible

Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.

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.

Chef

Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others.

Terraform

With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.

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.

Capistrano

Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows.

Related Comparisons

Jenkins vs Shipit: What are the differences?

In Summary, Jenkins and Shipit differ in architecture, extensibility, workflow focus, ease of use, community support, and integrations with platforms.

Jenkins vs Shipit

Overview