public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-24 20:18:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

updating configure repos

Browse Source
This commit is contained in:
MBishop17
2018-09-25 19:07:33 -07:00
committed by Mark Bishop
parent 0251750860
commit ebcd7f6219
2 changed files with 27 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/tools/pipelines/_index.md
+3 -3
View File
@@ -15,13 +15,13 @@ You can configure a pipeline to automate building, testing, and publishing for e
## Overview
Rancher Pipeline provides a simple CI/CD experience—use it to automatically checkout code, run builds, perform tests, publish docker images, and deploy Kubernetes resources to your clusters.
Rancher Pipeline provides a simple CI/CD experience-use it to automatically checkout code, run builds, perform tests, publish docker images, and deploy Kubernetes resources to your clusters.
You can configure a pipeline for each project in Rancher. Every project can have individual configurations and setup.
Pipelines are represented as pipeline files that are checked into source code repositories. Users can read and edit the pipeline configuration by either:
- Using the Rancher UI
- Using the Rancher UI.
- Updating the configuration in the repository, using tools like Git CLI to trigger a build with the latest CI definition.
>**Note:** Rancher Pipeline is not meant to replace enterprise-grade Jenkins or any other CI tool your team uses.
@@ -51,7 +51,7 @@ When you configure a pipeline in one of your projects, a namespace specifically
- **Docker Registry:**
Out-of-the-box, the default target for your builds in an internal Docker Registry. However, you can make configurations to push to a remote registry instead. Docker Registry is only accessible from cluster nodes and cannot be directly accessed by users.
Out-of-the-box, the default target for your builds is an internal Docker Registry. However, you can make configurations to push to a remote registry instead. Docker Registry is only accessible from cluster nodes and cannot be directly accessed by users.
<a id="minio"></a>
content/rancher/v2.x/en/tools/pipelines/quick-start-guide/_index.md
+24 -8
View File
@@ -3,27 +3,43 @@ title: Pipelines Quick Start Guide
weight: 500
---
Rancher ships with several example repositories that help you setup a pipeline quickly and easily. Before you use pipelines with your own repositories in a production environment, we recommend setting up the example repository that most resembles your environment. Use this example repository as a sandbox for repo configuration, build demonstration, etc. Rancher includes example repositories for:
- Go
- Maven
- php
## Configure Repositories
1. Go to the project you want to run a pipeline.
By default, the example pipeline repositories are disabled. Go enable one (or) more to test out the pipeline feature.
2. Select workloads from the top level Nav bar.
1. From the context menu, open the project for which you want to run a pipeline.
3. Select pipelines from the secondary Nav bar.
1. From the main menu, select **Workloads**. The select the **Pipelines** tab.
4. Click Configure Repositories button. If you haven't done authorization with your git account, you will see a list of example repositories. Otherwise, you will see a list of your repositories.
1. Click **Configure Repositories**.
5. Click the `Enable` button of an example repo, e.g., `https://github.com/rancher/pipeline-example-go.git`.
**Step Result:** A list of example repositories displays.
>**Note:** Example repositories only display if you haven't fetched your own repositories.
6. Click Done, you can see the repo under pipelines Nav bar.
1. Click **Enable** for one of the example repos (e.g., `https://github.com/rancher/pipeline-example-go.git`). Then click **Done**.
**Result:** A pipeline is configured for the example repository, and it's added to the **Pipeline** tab.
## Run Example Pipelines
1. Assuming you've enabled an example repository, go to pipelines Nav bar of the project.
2. Expand the action button of the enabled repository.
1. Expand the action button of the enabled repository.
3. Click Run.
1. Click Run.
>**Note:** When you are running a pipeline the first time, it will take a few minutes to pull relevant images and provision necessary pipeline components.
To understand what the example pipeline is doing, you can check the `.rancher-pipeline.yml` file in the example repositories, or click `Edit Config` action of the enabled repository to see it via UI wizard.
<<<<<<< HEAD
=======
For detail guides for pipeline configurations, please refer to the [configuration page](/rancher/v2.x/en/tools/pipelines/quick-start-guide/)
>>>>>>> ab68fa0e... updating configure repos