Deploy Jenkins

Jenkins is an open source, continuous integration and pipeline (CI/CD) software that helps automate the software development and deployment process.

Cautions

The service access address defaults to the IPV4 address. If you need to use IPV6 and the cluster network card supports IPV6, please modify the IPV4 address to the IPV6 address.

Prerequisites

Storage

Create a StorageClasses in storage management. The StorageClasses supported by this tool are CephFS File Storage and NFS.

Tip: After deleting the tool created by the function, the PVC bound to the tool will still remain.

On-premise deployment

1. In the left navigation bar, click DevOps Toolchain > Instances.

2. Click Create Instance.

3. On the Deploy and Integrate page, select Jenkins.

4. In the Location section, select the Clusters and Namespaces where you want to deploy the tool.

5. In the Resources section, select a CPU and memory allocation method and complete the configuration.

6. In the Storage section, select the storage method.

   Caution: After the instance is created, the storage configuration cannot be modified.

   Storage Method	Description
   Available PVCs	Select an existing PVC Name to request PVC as storage resources. Or click the Create PVC button on the right side of the selection box to create a new PVC in a new page. Tip: Storage classes only support CephFS File Storage and NFS; when selecting the access mode, it is recommended to use ReadWriteMany (RWX) mode.
   Node storage	Request storage resources on cluster nodes through the hostpath storage solution. NO StorageClasses is required. Caution: To avoid mounting failure, ensure that the path has not been used. When deploying the tool in a public cloud cluster, this solution is unavailable to avoid data loss because of node elasticty.

7. In the Networking section, configure the network for the tool to be deployed.

   Caution: If there are dual NIC nodes in the cluster where the tool is to be deployed, check whether the IP address of the load balancer or node IP address used by default in the service access address can provide external access to the cluster. Otherwise, the tool cannot be accessed normally after deployment, and the error message “check xx alive failed” will appear.

   Network Mode	Parameter Description
   Ingress
   	Domain Name	Select an existing domain name resource in the platform under Network > Domain Name. Alternatively, enter an existing domain name resource in the platform.
   	Protocol	Supports selection of HTTP and HTTPS protocols.
   	Certificate	When selecting the HTTPS protocol, select a certificate that matches the domain name in the certificate box. The source of the certificate can be platform allocation or import from secret dictionary. Platform allocation refers to creating a certificate in the management view of the container platform and assigning it to a specified project. Import from secret dictionary refers to creating a secret dictionary of type TLS in the container platform. Click Create Certificate and fill in the following form in the pop-up window to create a certificate. Name: Enter the name of the certificate. The certificate cannot be updated after it is created. Public Key: Click and select the certificate public key to import (binary files are not supported) in the pop-up window. After importing, the certificate public key (tls.crt) will be filled in the text box. Manual input is also supported. Private Key: Click and select the private key to import in the pop-up window (binary files are not supported). After importing, the private key (tls.key) will be filled in the text box. Manual input is also supported.
   Node Port	When selecting the Node Port network mode, you need to fill in the HTTP port, with an input range of `30000 - 32767`; at the same time, you need to fill in the SSH port, with an input range of `30000 - 32767`.
   Service Access Address	The service access address will be automatically generated based on the network mode you choose. When you choose the Ingress mode, the access address is generated according to the rule `http://{Ingress name}` or `https://{Ingress name}`. When you choose the Node Port mode, the access address is generated according to the rule `http://{cluster address:port}`. If you need to modify the service access address, click and fill in the service access address in the **Update Access URL** pop-up box. Note: Please be cautious when updating the service access address. After updating, external settings such as DNS resolution need to be configured to access the service normally. This update only applies to the current network setting state. When the network setting changes again, the service access address will be automatically replaced with the restricted value.

8. In the Accounts section, configure account-related information.

   Parameter	Description
   Name	Default value is admin and cannot be modified.
   Password	To ensure environment security, set a password in the credentials: click Create, fill in a recognizable name, and enter the password after jenkins-admin-password in Configuration. Note: If you need to modify the password later, please update the credential data information .

9. In the Integration area, enter an integration name that will help the project members to identify and select this tool in DevOps.

10. After the configuration is complete, click Deploy and Integrate.

    The instance integrates into the plaftform automatically.

Public cloud deployment

It is recommended to open a virtual machine and deploy a public cloud cluster before deploying DevOps tools, and use the same storage and network solution as the native cluster. In this way, the tools and capabilities supported for deployment are synchronized with the native cluster deployment tools.

Verification

Once the deployment status become Deployed, verify the tool’s accessibility by accessing the URL.

What’s next

Allocate tool resources to platform projects .