Skip to content

Commit

Permalink
jenkins has proper CI-as-code
Browse files Browse the repository at this point in the history
  • Loading branch information
Daniel Jones committed Jan 12, 2022
1 parent 08ea260 commit 1504647
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/blog/ci-shootout-conclusion.md
Original file line number Diff line number Diff line change
Expand Up @@ -223,7 +223,7 @@ Let's discuss each in more detail.

Jenkins is old and dated. It lacks isolation (shared workspace, workloads aren't containerised by default), and the plugin system almost guarantees surprise incompatibilities.

Jenkins allows users to make snowflake servers and builds. Yes, you can get it to persist config to source control, but it allows a workflow that is considered an anti-pattern in a cloud native, GitOps world.
Jenkins allows users to make snowflake servers and builds. Yes, you can get it to persist config to source control, but it allows a workflow that is considered an anti-pattern in a cloud native, GitOps world. That said, it is the only system reviewed that offers CI-as-_code_, and not CI-as-YAML.

It is job-oriented by default, although newer plugins provide a pipeline view. Much like Tekton and Argo Workflows, Jenkins does not offer a 'single pane of glass' view on the current state of a pipeline.

Expand Down

0 comments on commit 1504647

Please sign in to comment.