Merge pull request #1729 from rodmiromind/release-3.0

Some content changes for SEO
This commit is contained in:
KubeSphere CI Bot 2021-06-16 23:12:47 +08:00 committed by GitHub
commit a64da180fa
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 9 additions and 9 deletions

View File

@ -1,6 +1,6 @@
---
title: The Kubernetes Container Platform | KubeSphere
description: KubeSphere is a distributed operating system managing cloud native applications with Kubernetes as its kernel, and provides plug-and-play architecture for the seamless integration of third-party applications to boost its ecosystem.
title: Open-Source Kubernetes Container Platform For Enterprise | KubeSphere
description: An open-source Kubernetes Platform to manage enterprise-grade Kubernetes across hybrid cloud, multi-cloud and edge.
css: scss/index.scss
@ -16,7 +16,7 @@ section1:
section2:
title: One Kubernetes Platform for Full Stack Solutions
content: KubeSphere is also a multi-tenant enterprise-grade Kubernetes container platform with full-stack automated IT operation and streamlined DevOps workflows. It provides developer-friendly wizard web UI, helping enterprises to build out a more robust and feature-rich platform, which includes the most common functionalities needed for enterprise Kubernetes strategies.
content: KubeSphere is also a multi-tenant enterprise-grade open-source Kubernetes container platform with full-stack automated IT operation and streamlined DevOps workflows. It provides developer-friendly wizard web UI, helping enterprises to build out a more robust and feature-rich Kubernetes platform, which includes the most common functionalities needed for enterprise Kubernetes strategies.
children:
- name: Open Source
icon: /images/home/open-source.svg
@ -136,7 +136,7 @@ section4:
color: orange
section5:
title: KubeSphere with its Cloud Native Architecture
title: KubeSphere Container Platform with its Cloud Native Architecture
frontEnd:
title: Front End
project: KubeSphere Console
@ -190,7 +190,7 @@ section6:
btnLink: case/
link: mailto:kubesphere@gmail.com
linkContent: Want to join our user community and showcase your logo? Just send an email to kubesphere@gmail.com
joinTitle: Join the Revolution, Partner with KubeSphere
joinTitle: Join the Revolution, Partner with KubeSphere Container Platform
joinContent: We look forward to your joining KubeSphere partner program to improve both ecosystems and grow your business.
joinLink: partner/
image: /images/home/certification.jpg

View File

@ -1,5 +1,5 @@
---
title: "Create a Pipeline Using a Jenkinsfile"
title: "Create a Jenkins Pipeline Using a Jenkinsfile"
keywords: 'KubeSphere, Kubernetes, docker, spring boot, Jenkins, devops, ci/cd, pipeline'
description: "Learn how to create and run a pipeline by using an example Jenkinsfile."
linkTitle: "Create a Pipeline Using a Jenkinsfile"
@ -8,11 +8,11 @@ weight: 11210
A Jenkinsfile is a text file that contains the definition of a Jenkins pipeline and is checked into source control. As it stores the entire workflow as code, it underpins the code review and iteration process of a pipeline. For more information, see [the official documentation of Jenkins](https://www.jenkins.io/doc/book/pipeline/jenkinsfile/).
This tutorial demonstrates how to create a pipeline based on a Jenkinsfile from a GitHub repository. Using the pipeline, you deploy an example application to a development environment and a production environment respectively, which is accessible externally.
This tutorial demonstrates how to create a pipeline based on a Jenkinsfile from a GitHub repository. Using the Jenkins pipeline, you deploy an example application to a development environment and a production environment respectively, which is accessible externally.
{{< notice note >}}
Two types of pipelines can be created in KubeSphere: Pipelines created based on a Jenkinsfile in SCM, which is introduced in this tutorial, and [pipelines created through the graphical editing panel](../create-a-pipeline-using-graphical-editing-panel/). The Jenkinsfile in SCM requires an internal Jenkinsfile in Source Control Management (SCM). In other words, the Jenkfinsfile serves as part of SCM. The KubeSphere DevOps system automatically builds a CI/CD pipeline based on the existing Jenkinsfile of the code repository. You can define workflows such as `stage` and `step`.
Two types of pipelines can be created in KubeSphere: Pipelines created based on a Jenkinsfile in SCM, which is introduced in this tutorial, and [pipelines created through the graphical editing panel](../create-a-pipeline-using-graphical-editing-panel/). The Jenkinsfile in SCM requires an internal Jenkinsfile in Source Control Management (SCM). In other words, the Jenkfinsfile serves as part of SCM. The KubeSphere DevOps system automatically builds a CI/CD Jenkins pipeline based on the existing Jenkinsfile of the code repository. You can define workflows such as `stage` and `step`.
{{</ notice >}}
@ -24,7 +24,7 @@ Two types of pipelines can be created in KubeSphere: Pipelines created based on
- You need to set a CI dedicated node for running pipelines. Refer to [Set a CI Node for Dependency Caching](../../how-to-use/set-ci-node/).
- You need to install and configure SonarQube. Refer to [Integrate SonarQube into Pipeline](../../../devops-user-guide/how-to-integrate/sonarqube/). If you skip this part, there is no **SonarQube Analysis** below.
## Pipeline Overview
## Jenkins Pipeline Overview
There are eight stages as shown below in this example pipeline.