Argo vs Jenkins

Need advice about which tool to choose?Ask the StackShare community!

Argo

670
433
+ 1
6
Jenkins

57.7K
48.9K
+ 1
2.2K
Add tool

Argo vs Jenkins: What are the differences?

Argo and Jenkins are both popular tools used for continuous integration and continuous deployment. Let's explore the key differences that set them apart.

  1. Scalability: Argo is designed to handle large-scale deployments and can efficiently manage hundreds or even thousands of pipelines simultaneously. On the other hand, Jenkins is better suited for smaller projects and may face performance issues when dealing with extensive pipelines.

  2. Workflow Orchestration: Argo provides a workflow engine that allows users to define complex dependencies between tasks. This enables the execution of pipelines with tasks running concurrently, sequentially, or conditionally based on specific criteria. In contrast, Jenkins follows a more linear approach, with tasks being executed one after the other in a predefined order.

  3. Containerization and Orchestration: Argo is built on Kubernetes, which means it seamlessly integrates with containerization platforms and can leverage Kubernetes' features for managing containers. Jenkins, on the other hand, relies on plugins to support containerization and requires additional configuration to work with container orchestration platforms.

  4. Event-Driven Architecture: Argo supports event-driven workflows by allowing triggers based on various events such as Git commits, Docker image changes, or time-based schedules. Jenkins, on the other hand, primarily relies on polling for changes, which may not be as efficient as event-driven approaches.

  5. Declarative vs. Imperative: Argo follows a declarative approach, where pipelines are defined using YAML files. This allows for clearly defining the expected state and dependencies of tasks. Jenkins, on the other hand, has a more imperative nature, where pipelines are scripted using a Groovy-based DSL, giving developers more flexibility but potentially leading to more complex configurations.

  6. Community Support and Ecosystem: Jenkins has been around for a longer time and has a large and mature community. There is a vast number of plugins and integrations available for various tools and technologies. Although Argo is gaining popularity, its ecosystem is not as extensive as Jenkins, and finding specific plugins or integrations may be more challenging.

In summary, Argo excels in scalability, event-driven workflows, and containerization and orchestration integration. It embraces a declarative approach with a focus on Kubernetes. On the other hand, Jenkins provides a more flexible and mature ecosystem, making it a suitable choice for smaller projects and those requiring extensive plugin support.

Advice on Argo and Jenkins
Needs advice
on
Azure PipelinesAzure Pipelines
and
JenkinsJenkins

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.

See more
Replies (1)
Recommends
on
GitHubGitHub

If your source code is on GitHub, also take a look at Github actions. https://github.com/features/actions

See more
Mohammad Hossein Amri
Chief Technology Officer at Planally · | 3 upvotes · 491.3K views
Needs advice
on
GoCDGoCD
and
JenkinsJenkins

I'm open to anything. just want something that break less and doesn't need me to pay for it, and can be hosted on Docker. our scripting language is powershell core. so it's better to support it. also we are building dotnet core in our pipeline, so if they have anything related that helps with the CI would be nice.

See more
Replies (1)
Ankit Malik
Software Developer at CloudCover · | 1 upvotes · 474.1K views
Recommends
on
Google Cloud BuildGoogle Cloud Build

Google cloud build can help you. It is hosted on cloud and also provide reasonable free quota.

See more
Needs advice
on
ConcourseConcourse
and
JenkinsJenkins

I'm planning to setup complete CD-CD setup for spark and python application which we are going to deploy in aws lambda and EMR Cluster. Which tool would be best one to choose. Since my company is trying to adopt to concourse i would like to understand what are the lack of capabilities concourse have . Thanks in advance !

See more
Replies (1)
Maxi Krone
Cloud Engineer at fme AG · | 2 upvotes · 392.8K views
Recommends
on
ConcourseConcourse

I would definetly recommend Concourse to you, as it is one of the most advanced modern methods of making CI/CD while Jenkins is an old monolithic dinosaur. Concourse itself is cloudnative and containerbased which helps you to build simple, high-performance and scalable CI/CD pipelines. In my opinion, the only lack of skills you have with Concourse is your own knowledge of how to build pipelines and automate things. Technincally there is no lack, i would even say you can extend it way more easily. But as a Con it is more easy to interact with Jenkins if you are only used to UIs. Concourse needs someone which is capable of using CLIs.

See more
Needs advice
on
JenkinsJenkinsTravis CITravis CI
and
CircleCICircleCI

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

See more
Replies (6)
Dustin Falgout
Senior Developer at Elegant Themes · | 13 upvotes · 543.6K views

We use CircleCI because of the better value it provides in its plans. I'm sure we could have used Travis just as easily but we found CircleCI's pricing to be more reasonable. In the two years since we signed up, the service has improved. CircleCI is always innovating and iterating on their platform. We have been very satisfied.

See more
Peter Thomas
Distinguished Engineer at Intuit · | 9 upvotes · 853.6K views
Recommends
on
Travis CITravis CI
at

As the maintainer of the Karate DSL open-source project - I found Travis CI very easy to integrate into the GitHub workflow and it has been steady sailing for more than 2 years now ! It works well for Java / Apache Maven projects and we were able to configure it to use the latest Oracle JDK as per our needs. Thanks to the Travis CI team for this service to the open-source community !

See more
Recommends
on
Google Cloud BuildGoogle Cloud Build

I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.

I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.

One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.

Feel free to checkout an example: Cloudbuild Example

See more
Recommends
on
Travis CITravis CI

I use Travis CI because of various reasons - 1. Cloud based system so no dedicated server required, and you do not need to administrate it. 2. Easy YAML configuration. 3. Supports Major Programming Languages. 4. Support of build matrix 6. Supports AWS, Azure, Docker, Heroku, Google Cloud, Github Pages, PyPi and lot more. 7. Slack Notifications.

See more
Oded Arbel
Recommends
on
GitLab CIGitLab CI

You are probably looking at another hosted solution: Jenkins is a good tool but it way too work intensive to be used as just a backup solution.

I have good experience with Circle-CI, Codeship, Drone.io and Travis (as well as problematic experiences with all of them), but my go-to tool is Gitlab CI: simple, powerful and if you have problems with their limitations or pricing, you can always install runners somewhere and use Gitlab just for scheduling and management. Even if you don't host your git repository at Gitlab, you can have Gitlab pull changes automatically from wherever you repo lives.

See more
Recommends
on
BuildkiteBuildkite

If you are considering Jenkins I would recommend at least checking out Buildkite. The agents are self-hosted (like Jenkins) but the interface is hosted for you. It meshes up some of the things I like about hosted services (pipeline definitions in YAML, managed interface and authentication) with things I like about Jenkins (local customizable agent images, secrets only on own instances, custom agent level scripts, sizing instances to your needs).

See more
Decisions about Argo and Jenkins

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.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Argo
Pros of Jenkins
  • 3
    Open Source
  • 2
    Autosinchronize the changes to deploy
  • 1
    Online service, no need to install anything
  • 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
  • 111
    Has support for build pipelines
  • 68
    Easy setup
  • 66
    It is open-source
  • 53
    Workflow plugin
  • 13
    Configuration as code
  • 12
    Very powerful tool
  • 11
    Many Plugins
  • 10
    Continuous Integration
  • 10
    Great flexibility
  • 9
    Git and Maven integration is better
  • 8
    100% free and open source
  • 7
    Slack Integration (plugin)
  • 7
    Github integration
  • 6
    Self-hosted GitLab Integration (plugin)
  • 6
    Easy customisation
  • 5
    Pipeline API
  • 5
    Docker support
  • 4
    Fast builds
  • 4
    Hosted Externally
  • 4
    Excellent docker integration
  • 4
    Platform idnependency
  • 3
    AWS Integration
  • 3
    JOBDSL
  • 3
    It's Everywhere
  • 3
    Customizable
  • 3
    Can be run as a Docker container
  • 3
    It`w worked
  • 2
    Loose Coupling
  • 2
    NodeJS Support
  • 2
    Build PR Branch Only
  • 2
    Easily extendable with seamless integration
  • 2
    PHP Support
  • 2
    Ruby/Rails Support
  • 2
    Universal controller

Sign up to add or upvote prosMake informed product decisions

Cons of Argo
Cons of Jenkins
    Be the first to leave a con
    • 13
      Workarounds needed for basic requirements
    • 10
      Groovy with cumbersome syntax
    • 8
      Plugins compatibility issues
    • 7
      Lack of support
    • 7
      Limited abilities with declarative pipelines
    • 5
      No YAML syntax
    • 4
      Too tied to plugins versions

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is Argo?

    Argo is an open source container-native workflow engine for getting work done on Kubernetes. Argo is implemented as a Kubernetes CRD (Custom Resource Definition).

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

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Argo?
    What companies use Jenkins?
    See which teams inside your own company are using Argo or Jenkins.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Argo?
    What tools integrate with Jenkins?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    Mar 24 2021 at 12:57PM

    Pinterest

    GitJenkinsKafka+7
    3
    2123
    GitJenkinsGroovy+4
    4
    2633
    PythonDockerKubernetes+14
    12
    2597
    Dec 4 2019 at 8:01PM

    Pinterest

    KubernetesJenkinsTensorFlow+4
    5
    3267
    GitHubGitPython+22
    17
    14199
    JavaScriptGitHubPython+42
    53
    21782
    What are some alternatives to Argo and Jenkins?
    Airflow
    Use Airflow to author workflows as directed acyclic graphs (DAGs) of tasks. The Airflow scheduler executes your tasks on an array of workers while following the specified dependencies. Rich command lines utilities makes performing complex surgeries on DAGs a snap. The rich user interface makes it easy to visualize pipelines running in production, monitor progress and troubleshoot issues when needed.
    Flux
    Flux is the application architecture that Facebook uses for building client-side web applications. It complements React's composable view components by utilizing a unidirectional data flow. It's more of a pattern rather than a formal framework, and you can start using Flux immediately without a lot of new code.
    Spinnaker
    Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers.
    Kubeflow
    The Kubeflow project is dedicated to making Machine Learning on Kubernetes easy, portable and scalable by providing a straightforward way for spinning up best of breed OSS solutions.
    Kubernetes
    Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
    See all alternatives