StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Continuous Integration
  4. Continuous Integration
  5. Buildbot vs ESLint

Buildbot vs ESLint

OverviewDecisionsComparisonAlternatives

Overview

Buildbot
Buildbot
Stacks73
Followers128
Votes27
GitHub Stars5.4K
Forks1.7K
ESLint
ESLint
Stacks38.6K
Followers14.0K
Votes28
GitHub Stars26.6K
Forks4.8K

Buildbot vs ESLint: What are the differences?

Developers describe Buildbot as "Python-based continuous integration testing framework". BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure. On the other hand, ESLint is detailed as "The fully pluggable JavaScript code quality tool". A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.

Buildbot belongs to "Continuous Integration" category of the tech stack, while ESLint can be primarily classified under "Code Review".

"Highly configurable builds" is the top reason why over 8 developers like Buildbot, while over 2 developers mention "IDE Integration" as the leading cause for choosing ESLint.

Buildbot and ESLint are both open source tools. ESLint with 14.4K GitHub stars and 2.47K forks on GitHub appears to be more popular than Buildbot with 4K GitHub stars and 1.37K GitHub forks.

According to the StackShare community, ESLint has a broader approval, being mentioned in 543 company stacks & 592 developers stacks; compared to Buildbot, which is listed in 7 company stacks and 6 developer stacks.

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)
or
Manual

Advice on Buildbot, ESLint

Carlos
Carlos

Mar 14, 2020

Needs adviceonPrettierPrettierESLintESLintgulpgulp

Scenario: I want to integrate Prettier in our code base which is currently using ESLint (for .js and .scss both). The project is using gulp.

It doesn't feel quite right to me to use ESLint, I wonder if it would be better to use Stylelint or Sass Lint instead.

I completed integrating ESLint + Prettier, Planning to do the same with [ Stylelint || Sasslint || EsLint] + Prettier.

And have gulp 'fix' on file save (Watcher).

Any recommendation is appreciated.

465k views465k
Comments
Alex
Alex

Software Engineer

Aug 7, 2020

Review

you don't actually have to choose between these tools as they have vastly different purposes. i think its more a matter of understanding how to use them.

while eslint and stylelint are used to notify you about code quality issues, to guide you to write better code, prettier automatically handles code formatting (without notifying me). nothing else.

prettier and eslint both officially discourage using the eslint-plugin-prettier way, as these tools actually do very different things. autofixing with linters on watch isnt a great idea either. auto-fixing should only be done intentionally. you're not alone though, as a lot of devs set this up wrong.

i encourage you to think about what problem you're trying to solve and configure accordingly.

for my teams i set it up like this:

  • eslint, stylelint, prettier locally installed for cli use and ide support
  • eslint config prettier (code formatting rules are not eslints business, so dont warn me about it)
  • vscode workspace config: format on save
  • separate npm scripts for linting, and formatting
  • precommit hooks (husky)

so you can easily integrate with gulp. its just js after all ;)

159k views159k
Comments
Sri Srinivas
Sri Srinivas

Feb 11, 2020

Needs advice

I want to start automatic regressions for nightly builds and also continuous integration builds. The tests I ran are part of my regression suite. And I want to track the results of these tests.

I am able to do this with Jenkins using the Junit plugin. But, I am trying to do the same with Buildbot, and I am not able to get the report of the tests. So, I just want to know is it possible to get the reporting of tests through Buildbot. If yes, could anyone provide some examples

121k views121k
Comments

Detailed Comparison

Buildbot
Buildbot
ESLint
ESLint

BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure.

A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.

run builds on a variety of slave platforms;arbitrary build process: handles projects using C, Python, whatever;minimal host requirements: Python and Twisted;slaves can be behind a firewall if they can still do checkout;status delivery through web page, email, IRC, other protocols;track builds in progress, provide estimated completion time;flexible configuration by subclassing generic build process classes;debug tools to force a new build, submit fake Changes, query slave status;released under the GPL
-
Statistics
GitHub Stars
5.4K
GitHub Stars
26.6K
GitHub Forks
1.7K
GitHub Forks
4.8K
Stacks
73
Stacks
38.6K
Followers
128
Followers
14.0K
Votes
27
Votes
28
Pros & Cons
Pros
  • 9
    Highly configurable builds
  • 5
    Beautiful waterfall
  • 5
    Hosted internally
  • 4
    Free open source
  • 3
    Python
Pros
  • 8
    Consistent javascript - opinions don't matter anymore
  • 6
    IDE Integration
  • 6
    Free
  • 4
    Customizable
  • 2
    Broad ecosystem of support & users
Integrations
No integrations available
JavaScript
JavaScript

What are some alternatives to Buildbot, ESLint?

Jenkins

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.

Travis CI

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

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

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

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.

Code Climate

Code Climate

After each Git push, Code Climate analyzes your code for complexity, duplication, and common smells to determine changes in quality and surface technical debt hotspots.

Drone.io

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.

Codacy

Codacy

Codacy automates code reviews and monitors code quality on every commit and pull request on more than 40 programming languages reporting back the impact of every commit or PR, issues concerning code style, best practices and security.

wercker

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

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.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana