Jenkins vs Selenium

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

Jenkins

57.3K
48.9K
+ 1
2.2K
Selenium

15.3K
12.3K
+ 1
525
Add tool

Jenkins vs Selenium: What are the differences?

Introduction

Jenkins and Selenium are widely used tools in the software industry. Both serve different purposes and have their own key differences. In this markdown, we will highlight the main differences between Jenkins and Selenium.

  1. Integration Jenkins is primarily a continuous integration and continuous delivery (CI/CD) tool. It helps automate the build, test, and deployment processes in a software development lifecycle. On the other hand, Selenium is a web application testing framework used for automating browser actions and validating web application functionality.

  2. Functionality Jenkins focuses on the automation of repetitive tasks in software development, such as building code, running tests, and deploying applications. It provides a platform for automating the entire development workflow. Selenium, on the other hand, is specifically designed for testing web applications by interacting with web elements, validating form inputs, and verifying the functionality of web pages.

  3. Scope Jenkins has a broader scope as it can be used for various development-related activities like building, testing, and deploying applications, managing version control, and integrating with other tools. Selenium, on the other hand, has a specific focus on web application testing and automation, providing capabilities for cross-browser testing and functional testing.

  4. Usage Jenkins is typically used by the entire development team for automating the continuous integration and continuous delivery processes, allowing for a seamless software development workflow. Selenium, on the other hand, is primarily used by quality assurance (QA) engineers and software testers to automate web application testing and ensure its functionality.

  5. Execution Environment Jenkins does not have any specific execution environment requirements as it can be run on various operating systems and supports different programming languages. Selenium, on the other hand, requires a specific execution environment with the Selenium WebDriver and the chosen browser driver installed. It supports different programming languages as well but requires the specific WebDriver for the chosen language.

  6. Direct Interaction In terms of direct user interaction, Jenkins mainly provides a web-based graphical user interface (GUI) and command-line interface (CLI) for managing builds and jobs. Selenium, on the other hand, provides a more direct interaction with web elements by simulating user actions like clicks, inputs, and verifications.

In summary, Jenkins is primarily a CI/CD automation tool used for managing the build, test, and deployment processes, while Selenium is a web application testing framework used for automating browser actions and validating web application functionality.

Advice on Jenkins and Selenium
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 · 488.2K 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 · 470.9K 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
JestJestSeleniumSelenium
and
WebdriverIOWebdriverIO
in

we are having one web application developed in Reacts.js. in the application, we have only 4 to 5 pages that we need to test. I am having experience in selenium with java. Please suggets which tool I should use. and why ............................ ............................ .............................

See more
Replies (1)
Prashanth Marappa
Senior Software Engineer at Mphasis · | 1 upvotes · 213.1K views
Recommends
on
SeleniumSelenium

with the help of selenium we can automate react js for functional testing

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 · 389.6K 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 · 540K 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 · 849.7K 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 Jenkins and Selenium

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 Jenkins
Pros of Selenium
  • 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
  • 175
    Automates browsers
  • 154
    Testing
  • 101
    Essential tool for running test automation
  • 24
    Record-Playback
  • 24
    Remote Control
  • 8
    Data crawling
  • 7
    Supports end to end testing
  • 6
    Easy set up
  • 6
    Functional testing
  • 4
    The Most flexible monitoring system
  • 3
    End to End Testing
  • 3
    Easy to integrate with build tools
  • 2
    Comparing the performance selenium is faster than jasm
  • 2
    Record and playback
  • 2
    Compatible with Python
  • 2
    Easy to scale
  • 2
    Integration Tests
  • 0
    Integrated into Selenium-Jupiter framework

Sign up to add or upvote prosMake informed product decisions

Cons of Jenkins
Cons of Selenium
  • 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
  • 8
    Flaky tests
  • 4
    Slow as needs to make browser (even with no gui)
  • 1
    Update browser drivers

Sign up to add or upvote consMake informed product decisions

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.

What is Selenium?

Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well.

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

Jobs that mention Jenkins and Selenium as a desired skillset
What companies use Jenkins?
What companies use Selenium?
See which teams inside your own company are using Jenkins or Selenium.
Sign up for StackShare EnterpriseLearn More

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

What tools integrate with Jenkins?
What tools integrate with Selenium?

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
2127
GitJenkinsGroovy+4
4
2636
Dec 4 2019 at 8:01PM

Pinterest

KubernetesJenkinsTensorFlow+4
5
3268
GitHubGitPython+22
17
14199
JavaScriptGitHubPython+42
53
21802
What are some alternatives to Jenkins and Selenium?
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.
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.
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.
Bamboo
Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.
Apache Maven
Maven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven, providing a uniform build system. Once you familiarize yourself with how one Maven project builds you automatically know how all Maven projects build saving you immense amounts of time when trying to navigate many projects.
See all alternatives