Shulou(Shulou.com)06/03 Report--

This article mainly introduces "how to convert a free-style project into a pipeline project CI/CD". In daily operation, I believe many people have doubts about how to convert a free-style project into a pipeline project CI/CD. The editor consulted all kinds of materials and sorted out simple and easy-to-use methods of operation. I hope it will be helpful to answer the doubts of "how to convert a free-style project into a pipeline project CI/CD". Next, please follow the editor to study!

Today, many companies use Jenkins to complete their continuous integration, testing, and continuous deployment. Most of them use freestyle as the default project type, but this has its own limitations. I recently started migrating all Freestyle to Pipeline projects as needed. So when will these jobs be triggered? After the developer / owner pushes / submits the update repository, the jenkins job will trigger these jobs-a binary file will be generated, and another unit test will be run to check code coverage. Because code coverage unit tests take a lot of time to complete, the need to split the two tasks into two tasks increases. Whenever there is an update in the repository, the job is triggered and code is checked in on the computer that restricts the running and execution of pre-build and post-build steps.

Free style project

Global configuration

GitHub repository configuration

Enable webhook configuration

Construction steps based on Shell

Publish-build tasks based on the results

Triggers an email notification to notify the project owner after the build is executed

The same job type was created for the unit test job, with few changes in Build shell, and some unit test code was added.

Why convert to a Pipeline project?

One of the main problems with Freestyle is that it does not allow SCM to poll webhook triggers for more than 1 repository. This is our main concern and paves the way for the relocation of pipelines. The above snapshot covers nearly seven tasks, while the number of tasks for unit tests is about 10. Then we can use pipelined code to perform all tasks. The following is a conversion from the Freestyle above

WSPACE ='/ var/jenkins/workspace/Directory_Name/' BRWSPACE ='/ var/jenkins/workspace/' pipeline {agent {node {label 'Node_Name' customWorkspace "${WSPACE}"}} / / empty the build directory stages {stage (' Cleaning up the previous directory') {steps { Echo 'Deleteing the directory' sh "rm-rf / var/jenkins/workspace/Directory_Name/*"}} / / download the code and rely on stage (' Checking out build repo and its dependencies') {steps {dir ("${WSPACE} / RepoName") {git branch: 'master' CredentialsId: 'UserName', url:' https://github.com/path/repo.git'} dir ("${WSPACE} / dir") {git branch: 'master', credentialsId:' UserName' Url: 'https://github.com/path/repo1.git'} dir ("${WSPACE} / dir3") {git branch:' master', credentialsId: 'UserName2' Url: 'https://github.com/path/repo4.git'} / / execute build stage (' Versioning and executing the build') {steps {dir ("${WSPACE} / repo1") {script { Sh label:'' Script:''/ usr/bin/env cd / var/jenkins/workspace/ original= `cat patch_ info` MAJOR= `cat patch_info | cut-d "."-f1`cat patch_info | cut-d "."-f2`cat `cat patch_info | cut-d "."-f3`cat `expr $PATCH + 1`cat-I "s/$original/$New_Version/g" Patch_info echo "$New_Version" cd / var/jenkins/workspace/path/repo4/ echo "Starting the Unit Testing" export GOPATH=$HOME/go export PATH=$PATH:/usr/local/go/bin:$GOPATH/bin make format make clean build if make unit-test Then cd / var/jenkins/workspace/path/repo1/dir else cd / var/jenkins/workspace/path/repo2/dir2 fi if make unit-test Then echo "unit testing completed" fi''}} / / publish HTML report stage ('Publish HTML Report') {steps {dir ("/ jenkins/workspace/") {script {sh label:'' Script:''/ usr/bin/env perl / jenkins/generate_build_meta_data.pl-jr http://gitlab.com:8080-bNum ${BUILD_NUMBER}-bName ${JOB_NAME}-o / tmp-t / jenkins/template.html export GOPATH=$HOME/go export PATH=$PATH:/usr/local/go/bin:$GOPATH/bin cd / var / jenkins/workspace/path/repo1/service/ go tool cover-html=c.out-o coverage.html cd / var/jenkins/workspace/path/repo2/dir3 go tool cover-html=c.out-o output.html''publishHTML ([allowMissing: false AlwaysLinkToLastBuild: false, keepAll: false, reportDir:'/ tmp/$ {JOB_NAME} / ${BUILD_NUMBER}', reportFiles:'${JOB_NAME}-${BUILD_NUMBER}-manifest.html', reportName: 'Email Output Subject' ReportTitles:''])}} / / send email stage ('Send Email') {steps {dir ("${WSPACE} / repo4") {emailext attachmentsPattern:' * / coverage.html,**/dir4.html', body:'${FILE Path= "/ tmp/$ {JOB_NAME} / ${BUILD_NUMBER} / ${JOB_NAME}-${BUILD_NUMBER}-manifest.html"}', subject: 'Unit testing Email Output ${BUILD_NUMBER} Successful', to: "EmailID@Domain2.com, EmailID2@Domain3.com"}

The above code provides us with the space for editing and its cohesion. An important feature of piping operations is that the output of the phase is presented in an attractive way, which I find easy to understand what is going on.

At this point, the study on "how to convert a free-style project into a pipeline project CI/CD" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.