Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Pros:

  • End to End CI / CD integration including pushing images to registry, artifacts to Nexus
  • Full integration with Github
  • Full integration with GitOps to create and manage environments
  • Support for preview environments for pull requests using Knative (Optional - Comes bundled with Jenkins X if required)
  • Can create and update helm charts after a build and and deploy and auto commit to repository
  • Internally translates all CI / CD pipelines to tekton pipelines
  • Conversion of our existing Jenkins pipelines to Jenkins X is a feature provided out of the box
  • A promising tool - Jenkins + Tekton with a highly active community backed by big organizations
  • Artifact promotion to various environments based on criterias set by us


Cons:

  • Very minimal UI - Unlike the traditional Jenkins
  • Command line based approach
  • Mainly intended for container build and deployment but can support othe types of artifacts with self customizations
  • Conversion of our current Jenkinsfiles to Jenkins X is not straight forward but can be done with moderate effort
  • Lots of tweaking and changes required in build and deployment strategy to make it work for our use case
  • Requires at least 3 nodes in cluster to handle the Jenkins master, other dependent components and worker pods


Jenkins X Typical Workflow


Jenkins X Typical Workflow - Detailed




Jenkins X Components





  • No labels