Skip to content

Latest commit

 

History

History
38 lines (23 loc) · 1006 Bytes

0014-jenkins-for-continuous-integration.md

File metadata and controls

38 lines (23 loc) · 1006 Bytes

Jenkins for Continuous Integration

  • Status: accepted
  • Deciders: @jam01
  • Date: 2020-09

Context and Problem Statement

We'll be using Flux for continuous deployment, leaving us to choose a component for continuous delivery, i.e.: building and running tests against artifacts before deploying.

Decision Drivers

  • Existing proficiency and pipelines
  • Simplicity

Considered Options

  • Jenkins
  • Jenkins X
  • Tekton

Decision Outcome

We'll use Jenkins as our CI component. Since we're using Flux for deployment we don't need too Kubernetes specific features like Jenkins X has, and Jenkins can support for complex pipelines than Tekton.

Positive Consequences

  • Can re-use existing pipelines with little modification

Negative Consequences

  • Less 'modern' than other options

Links