mirrors/ceph-csi
1
0
Fork 0
mirror of https://github.com/ceph/ceph-csi.git synced 2024-12-02 03:00:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: correct links in ci/centos README.md

Browse Source 
Reported-by: Madhu Rajanna <madhupr007@gmail.com>
Signed-off-by: Niels de Vos <ndevos@redhat.com>
This commit is contained in:
Niels de Vos 2020-05-27 13:37:16 +02:00
parent 650d749d28
commit 7a7d45cd67
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -1,7 +1,7 @@
# Continuous Integration Jobs for the CentOS CI # Continuous Integration Jobs for the CentOS CI
- [dedicated Jenkins instance](ceph_csi_ci) for Ceph-CSI - [dedicated Jenkins instance][ceph_csi_ci] for Ceph-CSI
- Jenkins is hosted on [OpenShift in the CentOS CI](app_ci_centos_org) - Jenkins is hosted on [OpenShift in the CentOS CI][app_ci_centos_org]
- scripts and Jenkins jobs are hosted in the Ceph-CSI repository (ci/centos - scripts and Jenkins jobs are hosted in the Ceph-CSI repository (ci/centos
branch) branch)
- a Jenkins Pipeline is used to reserve bare metal system(s), and run jobs on - a Jenkins Pipeline is used to reserve bare metal system(s), and run jobs on
@ -16,13 +16,13 @@ projects branches.
As an example, the `containerized-tests` Jenkins job consists out of the As an example, the `containerized-tests` Jenkins job consists out of the
following files: following files:
- `jobs/containerized-tests.yaml` is a [Jenkins Job Builder](jjb) configuration - `jobs/containerized-tests.yaml` is a [Jenkins Job Builder][jjb] configuration
that describes the events when the job should get run and fetches the that describes the events when the job should get run and fetches the
`.groovy` file from the git repository/branch `.groovy` file from the git repository/branch
- `containerized-tests.groovy` is the [Jenkins Pipeline](pipeline) that - `containerized-tests.groovy` is the [Jenkins Pipeline][pipeline] that
contains the stages for the Jenkins Job itself. In order to work with [the contains the stages for the Jenkins Job itself. In order to work with [the
bare-metal machines from the CentOS CI](centos_ci), it executes the following bare-metal machines from the CentOS CI][centos_ci_hw], it executes the
stages: following stages:
1. dynamically allocate a Jenkins Slave (`node('cico-workspace')`) with tools 1. dynamically allocate a Jenkins Slave (`node('cico-workspace')`) with tools
and configuration to request a bare-metal machine and configuration to request a bare-metal machine