2019-07-16

OS

Execute sudo without password

在使用 Jenkins pipeline 的时候，在 Linux 需要用 root 来执行，我想通过 Jenkins pipeline 的语法来解决，但是只找到这种方式：SSH Pipeline Steps

2019-07-07

Hexo

Hexo 添加 Disqus 留言功能

在你的 Hexo 网站添加 Disqus

去 Disqus 创建一个账号，在这个过程中有需要选择一个 shortname，完成后，你可以在设置页码找到你的 shortname

https://YOURSHORTNAMEHERE.disqus.com/admin/settings/general

在你 Hexo 博客里打开 _config.yml, 然后输入 disqus_shortnameand: YOURSHORTNAMEHERE，像这样：

2019-07-07

Jenkins

Jenkinsfile example - 实现交互、clone 多个仓库以及 git push

这个pipeline里包含了如下几个技术：

如何使用其他机器，agent
如何使用环境变量，environment
如何在build前通过参数化输入，parameters
如何使用交互，input
如何同时clone多个repos
如何进行条件判断，anyOf

2019-07-07

Git

Git 管理

查找是否有遗漏提交

从一个分支找到所有的 commit 和 ticket 号，然后去另外一个分支去查找这些提交是否也在这个分支里。

2019-06-25

Jenkins

Multibranch Pipeline

Problems

Like database product, it runs on multi-platform, but for software enginner they may only works on one platform, how they could identify their code works on all platform? manually build the various platforms? NO!

Solution

Most people would know we can use Jenkins pipeline, they may create multi Jenkins job for different stuation.

How to do it in an elegant way, I would want to share how to use multibranch pipeline to achieve.

When create a pull request, auto parallel start simple build.
Reviewers can decide whether to merge base on build results.
After code merged, auto start full build.

2019-05-21

Coverage

A Code Coverage Tool - Squish Coco use examples

Preparation

You need to ask for a free trial license and install
- You will receive a mail with username/password to login for downloading
I test it on the Windows platform, so I download the Windows installer, then install Squish Coco and Add-in
Installed Visual Studio 2010 or higher, I used VS2017 Professional

2019-05-21

Coverage

Code Coverage tools of C/C++

Code Coverage is a measurement of how many lines, statements, or blocks of your code are tested using your suite of automated tests. It’s an essential metric to understand the quality of your QA efforts.

Code coverage shows you how much of your application is not covered by automated tests and is therefore vulnerable to defects. it is typically measured in percentage values – the closer to 100%, the better.

When you’re trying to demonstrate test coverage to your higher-ups, code coverage tools (and other tools of the trade, of course) come in quite useful.

List of Code Coverage Tools

2019-05-14

Jenkins

GitSCM clone code don't display branch

最近遇到一个 regression bug，是产品完成构建之后，build commit number 不对，显示的 HEAD 而不是常见的 97b34931ac HASH number,这是什么原因呢？
我检查了 build 脚本没有发现问题，branch 的输出是正确的，那我怀疑是引入 Jenkins 的原因，果然登录到远程的 agent 上去查看分支名称如下：

C:\workspace\blog>git branch
* (HEAD detached at 97b3493)

果然问题出在了 Jenkins 上。这个问题有简单办法解决，就是直接使用git命令来clone代码，而不使用Git插件

git clone --depth 1 -b u2opensrc https://username:"passwowrd"@git.github.com/scm/blog.git blog

这种方式固然简单，不会出错，但它是明码显示，我岂能容忍这种不堪的处理方式吗？肯定还是要在 Git 插件上找到解决办法的。
随后google一下，果然有遇到和我一样问题的人，问题链接这里。

他说他做了很多调查，还跟专业的 Jenkins 人士联系，试了很多次，最后找到这个办法

checkout([$class: 'GitSCM', branches: [[name: '*/feature/*']], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'LocalBranch', localBranch: "**"]], submoduleCfg: [], userRemoteConfigs: [[credentialsId: '99f978af-XXXX-XXXX-8147-2cf8f69ef864', url: 'http://TFS_SERVER:8080/tfs/DefaultCollection/Product/_git/Project']]])

主要是在 extensions:[] 中加入这句 [$class: ‘LocalBranch’, localBranch: “**”]

这是 Jenkins 的 Bug 吗？带着这个疑问随后通过 Pipeline Syntax，找到 checkout: Check out from version control，在 Additional Behaviours 里有 Check out to specific local branch 这个配置项

If given, checkout the revision to build as HEAD on this branch.
If selected, and its value is an empty string or “**”, then the branch name is computed from the remote branch without the origin. In that case, a remote branch origin/master will be checked out to a local branch named master, and a remote branch origin/develop/new-feature will be checked out to a local branch named develop/newfeature.

看介绍原来 Jenkins 自带这个设置，只是它不是默认选项，所以才遇到刚才那个问题。随后选择这个设置，然后填入”**”，然后生成 Pipeline 脚本，就跟上面的脚本一样了。

2019-05-13

Automation

通过参数化上传文件到 FTP 服务器

实现 CI/CD 过程中，常常需要将构建好的 build 上传到一个公共的服务器，供测试、开发来获取最新的 build。如何上传 build 成果物到 FTP server，又不想把 FTP server登录的用户名和密码存在脚本里，想做这样的参数化如何实现呢？

upload_to_ftp.bat [hostname] [username] [password] [local_path] [remote_pat]

2019-05-12

Jenkins

Automatically commit code by Jenkins

When we need to release a product, we should change copyright, build version, release month, release note…
How to modify multiple files automatically?
I used a Jenkins pipeline project, the project is parameterized(string parameter) and regular expressions to implement.

Here is the string parameter for copyright:

Name: copyright
Default Value: 1995—2019

stage('change copyrigh') {
    steps {
        sh label: '', script: 'sed -i -E "s/(1995—[0-9]{4})/${copyright}/" 1033/AutoRun.ini'
    }
}

Here is the string parameter for build version:

Name: build_version
Default Value: 1.2.2.1002

Description: build version format: 1.2.2.1002

stage('change build version') {
    steps {
        sh label: '', script: 'sed -i -E "s/([0-9].[0-9].[0-9].[0-9]{4})/${build_version}/" 1033/AutoRun.ini'
    }
}

Here is the string parameter for build version:

Name: release_month
Default Value: May 2019

Description: release month format: May 2019

stage('change release month') {
    steps {
        sh label: '', script: '''
        sed -i -E "s/([a-z]* 20[0-9]{2})/${release_month}/" 1033/AutoRun.ini
        sed -i -E "s/([a-z]* 20[0-9]{2})/${release_month}/" 1033/MainMenu.ini
        '''
    }
}

push change to Git

stage('git push to Git') {
    steps {
        sshagent(['8dd766ba-ac0f-4302-afa8-bee59c726dee']) {
            sh("git add 1033/AutoRun.ini")
            sh("git add 1033/MainMenu.ini")
            sh("git commit -m 'Bld # ${build_version}'")
            sh("git push -u origin master")
        }
    }
}

Whole Jenkins Pipeline looks like:

pipeline {
    agent {
        label 'master'
    }

    stages{
        stage('git clone') {
            steps{
                git branch: 'master',
                credentialsId: '8dd766ba-ac0f-4302-afa8-bee59c726dee',
                url: 'git@github.com:shenxianpeng/blog.git'
            }
        }

        stage('change copyrigh') {
        steps {
            sh label: '', script: 'sed -i -E "s/(1995—[0-9]{4})/${copyright}/" 1033/AutoRun.ini'
        }
        }

        stage('change release month') {
        steps {
            sh label: '', script: '''
            sed -i -E "s/([a-z]* 20[0-9]{2})/${release_month}/" 1033/AutoRun.ini
            sed -i -E "s/([a-z]* 20[0-9]{2})/${release_month}/" 1033/MainMenu.ini
            '''
        }
        }

        stage('change build version') {
        steps {
            sh label: '', script: 'sed -i -E "s/([0-9].[0-9].[0-9].[0-9]{4})/${build_version}/" 1033/AutoRun.ini'
        }
        }

        stage('git push to Git') {
            steps {
                sshagent(['8dd766ba-ac0f-4302-afa8-bee59c726dee']) {
                    sh("git add 1033/AutoRun.ini")
                    sh("git add 1033/MainMenu.ini")
                    sh("git commit -m 'Bld # ${build_version}'")
                    sh("git push -u origin master")
                }
            }
        }
    }
}