Creating a Cloud-V CI Pipeline file
What is a Cloud-V CI Pipeline file
A cloud-v-pipeline file is a Continuous Integration (CI) jenkins pipeline script which is written in Groovy. It describes various stages (and possibly steps) which are executed in the defined pattern. These stages can be written in bash or they can be written in Groovy itself.
Mainly there can be two types of Cloud-V pipeline files are of two types:
- Scripted: Only contains stages
- Declarative: Contains stages as well as steps (more feature-rich and recommended)
This documentation will cover how to create a cloud-v-pipeline file with bash script inside it and run it on various compute instances (which are known as Nodes in jenkins).
Jenkins Node
In jenkins, node represents a compute instance. In simple words, it is the platform on which our job build is going to run.
Jenkins Master
There is a jenkins Master node which is actually the compute instance on which Jenkins is installed. It is the node which schedules builds on runners. For security reason, no job is allowed to run on this node.
Jenkins Slave
Jenkins slave nodes are the compute instances on which our job builds run safely. They may be attached with jenkins master via hardware or they may be connected through remote SSH connection.
cloud-v-pipeline file written with bash
Simple Hello World cloud-v-pipeline file
In Cloud-V, all the platforms are running Linux operating system, so the cloud-v-pipeline should be written in bash.
Following script is an example of how can we run a bash script in scripted cloud-v-pipeline.
node{
stage('*** Phase 1 ***') {
//Using bash commands
sh '''#!/bin/bash
echo "Hello World !\n"
'''
}
}
The keyword sh is used to specify a shell script
As there is nothing mentioned with node, so the script will run job build on any available compute instance.
cloud-v-pipeline for a Specific Node
In previous script, the cloud-v-pipeline would run on any compute instances which are available. But in case if someone wants to run a job build on specific node, then a compute instance name must be specified with keyword node. The following script is an example of running above Hello World program on node named hifive_unleashed.
node('hifive_unleashed'){
stage('*** Phase 1 ***') {
//Using bash commands
sh '''#!/bin/bash
echo "Hello World !\n"
'''
}
}
cloud-v-pipeline for Cross-Platform Compilation and Execution
Cloud-V supports cross-compilation and execution on emulated RISC-V compute instances. Following tools help in cross compilation and cross-platfrom execution:
- RISC-V GNU Toolchain
- QEMU user mode (for running standalone binaries)
- QEMU System (for running application in Linux)
An example pipeline script is given below in scripted pipeline.
node('x86_runner2'){
checkout scm //Getting content of this repo
stage('*** Compilation Phase ***') { // for display purposes
//Compiling helloworld.c using bash commands
sh '''#!/bin/bash
gcc -g ./helloworld.c -o helloworld.out
riscv64-unknown-linux-gnu-gcc ./helloworld.c -o helloworld_riscv_compiled.out //Cross compiling for RISC-V
'''
}
stage (' *** Running Binaries ***'){
sh '''#!/bin/bash
./helloworld.out
qemu-riscv64 -L $RISCV_SYSROOT helloworld_riscv_compiled.out //Running executable on RISC-V emulated platform
'''
}
}
The equivalent declarative pipeline is as follows:
pipeline {
agent {label "x86_runner2"}
stages {
stage('Clone Repository') {
steps('delegate'){
checkout scm //Clones the repository on the local machine
}
}
stage ('Compilation Phase'){
steps{
sh '''#!/bin/bash
gcc -g ./helloworld.c -o helloworld.out
'''
sh '''#!/bin/bash
riscv64-unknown-linux-gnu-gcc ./helloworld.c -o helloworld_riscv_compiled.out
'''
}
}
stage ('Running Binaries'){
steps {
sh ''' #!/bin/bash
./helloworld.out
'''
sh'''#!/bin/bash
qemu-riscv64 -L $RISCV_SYSROOT helloworld_riscv_compiled.out
'''
}
}
}
}