Use SSH in Continuous Integration

Overview

Benefits

Scenarios

Introduction

Purchase Guide

Getting Started

Text Editor

Process Configuration Details

Graphical Editor

Compile Build Process

Trigger Rules

Environment Variables

Build Snapshots

Cache Directory

Configure Build Plan

Docker

Build Artifacts

Group Management

Build Plan Templates

Manage Build Plans

Error

Upload Generic Artifacts

System Plugins

Operation Guide

K8s Clusters

Docker Servers

COS Buckets

Automated Deployment

Use Docker in Continuous Integration

Practical Tutorial

Jenkinsfile Syntax

Build Execution Issues

Continuous Integration and Code Repositories

Continuous Integration and Artifact Repositories

Custom Build Nodes

FAQs

Privacy Policy

Data Processing And Security Agreement

coding-ci Policy

CODING Continuous Integration

This document describes how to use SSH in Continuous Integration.

Before configuring the CODING Continuous Integration (CODING-CI) build environment, you must activate the CODING DevOps service for your Tencent Cloud account.

Log in to the CODING Console and click the 

 in the upper-right corner to open the project list page and click a 

When executing a build in Continuous Integration, you may need to log in to a remote server with SSH protocol to execute the necessary script or command. Go to 

 > "Build Plan Settings" > "Process Configuration", use the text editor to enter the relevant command.

CODING-CI allows you to control a remote server using SSH commands.

sshCommand: Run a specific command on the remote server.

sshPut: Place files or directories of the current workspace in the remote server.

sshGet: Obtain files or directories from a remote server.

sshScript: Read the local shell script and run it on the remote server. If you run the script of the remote server, you will get the error: does not exist.

sshRemove: Remove a certain file or directory from a remote server.

The following example shows how to use an account and password to connect to a remote server and run SSH commands. An example of a Jenkinsfile configuration is as follows:

    withCredentials([usernamePassword(credentialsId: 'sshUserAcct', 

        passwordVariable: 'password', usernameVariable: 'userName')]) {

            writeFile file: 'test.sh', text: 'ls'

                command: 'for i in {1..5}; do echo -n \"Loop \$i \"; date ; sleep 1; done'

            sshScript remote: remote, script: 'test.sh'

            sshPut remote: remote, from: 'test.sh', into: '.'

            sshGet remote: remote, from: 'test.sh', into: 'test_new.sh', override: true

            sshRemove remote: remote, path: 'test.sh'

How to Use SSH to Connect to a Remote Service

Besides using an account and password to connect to a remote server, you can also use an SSH private key to connect to a remote service. An example of a Jenkinsfile configuration is as follows:

    withCredentials([sshUserPrivateKey(credentialsId: 'sshUser', keyFileVariable: 'identity')]) {

            writeFile file: 'abc.sh', text: 'ls'

            sshPut remote: remote, from: 'abc.sh', into: '.'

            sshGet remote: remote, from: 'abc.sh', into: 'bac.sh', override: true

            sshScript remote: remote, script: 'abc.sh'

            sshRemove remote: remote, path: 'abc.sh'

For more information on SSH commands in Jenkinsfile, see the 

https://jenkins.io/doc/pipeline/steps/ssh-steps/

For more information about Jenkins SSH plugins, see the plugin's 

tencent cloud