Comparison Table

Description

The comparison table component displays a reponsive and rendered table, based on a yaml data file. Few options are passed to this component, and all copy is drawn from the yaml file. To view a sample structure of this data, see "src/_data/pages/jenkins-circleci-comparison.yml"

Sample Comparison Table

Rendered


CIRCLECI
JENKINS

Setup

  • VCS authentication directly from the UI
  • Import repositories as projects*
  • Install Jenkins on CI machines and plugins for VCS integration, UI, and any additional functionality
  • Troubleshoot plugins for cross-functionality

Security

  • Application-level security + runtime isolation
  • Additional security layers protect source code, environment variables, and outputs
  • Single layer of security surrounding CI fleet
  • Any additional security is created manually
  • Security of OSS plugins varies

Permissions

  • Add users via VCS authentication
  • Automatically adopt permissions from VCS
  • All users given full access by default, permissions need to be set manually

Configuration

  • Declarative YAML configuration for all features, defined in a single config.yml file
  • String together functionality from plugins with varying syntax and best practices

Performance

  • Allocate more CPUs + RAM to complex jobs
  • Cache dependencies, Docker layers, and more
  • No slow-downs from individual features
  • Dependent on efficiency of plugins
  • Manually tweak plugins or upgrade machines to increase Jenkins performance

Maintenance

  • Use new features as soon as they are released
  • Maintain machines and individual plugins with varying release cycles and support

Sample Comparison Table

Code


{% assign data = site.data.en.pages.jenkins-circleci-comparison %} {% include components/comparison-table.html data=data %}

Rendered


CIRCLECI
JENKINS

Setup

  • VCS authentication directly from the UI
  • Import repositories as projects*
  • Install Jenkins on CI machines and plugins for VCS integration, UI, and any additional functionality
  • Troubleshoot plugins for cross-functionality

Security

  • Application-level security + runtime isolation
  • Additional security layers protect source code, environment variables, and outputs
  • Single layer of security surrounding CI fleet
  • Any additional security is created manually
  • Security of OSS plugins varies

Permissions

  • Add users via VCS authentication
  • Automatically adopt permissions from VCS
  • All users given full access by default, permissions need to be set manually

Configuration

  • Declarative YAML configuration for all features, defined in a single config.yml file
  • String together functionality from plugins with varying syntax and best practices

Performance

  • Allocate more CPUs + RAM to complex jobs
  • Cache dependencies, Docker layers, and more
  • No slow-downs from individual features
  • Dependent on efficiency of plugins
  • Manually tweak plugins or upgrade machines to increase Jenkins performance

Maintenance

  • Use new features as soon as they are released
  • Maintain machines and individual plugins with varying release cycles and support