Skip to content

Article tekton argocd#139

Open
ErdelyiLivi wants to merge 9 commits intoZuehlke:mainfrom
ErdelyiLivi:article-tekton-argocd
Open

Article tekton argocd#139
ErdelyiLivi wants to merge 9 commits intoZuehlke:mainfrom
ErdelyiLivi:article-tekton-argocd

Conversation

@ErdelyiLivi
Copy link
Copy Markdown
Collaborator

No description provided.


Let’s take a short look at the still commonly used Jenkins CI/CD Pipeline that many teams and companies consider outdated, in order to see why the use of a more modern solution is inevitable.

#### **What is Jenkins?**
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#### **What is Jenkins?**
#### **What is Jenkins?**

tags:
- Tekton
- ArgoCD
- CI / CD
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- CI / CD
- CI/CD

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally, no space is used around a forward slash when connecting single words or simple alternatives.

Delivering software quickly, safely, and consistently has become a defining challenge for modern development teams.
As applications evolve into distributed, containerized services, continuous integration and continuous delivery (CI/CD) pipelines must also evolve — becoming more cloud-native, scalable, and declarative.

To overcome these challenges, modern tools are essential. If the topic is CI / CD, the most commonly used tools are GitHub Actions, GitLab CI / CD, Jenkins, CircleCI, Tekton & ArgoCD.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To overcome these challenges, modern tools are essential. If the topic is CI / CD, the most commonly used tools are GitHub Actions, GitLab CI / CD, Jenkins, CircleCI, Tekton & ArgoCD.
To overcome these challenges, modern tools are essential. If the topic is CI/CD, the most commonly used tools are GitHub Actions, GitLab CI/CD, Jenkins, CircleCI, Tekton & ArgoCD.


Both tools support multi-cluster deployments, allowing centralized pipeline orchestration and GitOps-driven delivery across many OpenShift clusters.

### **Benefits of Using Tekton and Argo CD on OpenShift**
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### **Benefits of Using Tekton and Argo CD on OpenShift**
### **Benefits of Using Tekton and Argo CD on OpenShift**


GitOps Automation: Argo CD’s GitOps approach promotes infrastructure as code and operational consistency, reducing manual intervention and deployment errors.

### **Final Thoughts**
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### **Final Thoughts**
### **Final Thoughts**

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants