这个pipeline里包含了如下几个技术:
- 如何使用其他机器,agent
- 如何使用环境变量,environment
- 如何在build前通过参数化输入,parameters
- 如何使用交互,input
- 如何同时clone多个repos
- 如何进行条件判断,anyOf
这个pipeline里包含了如下几个技术:
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!
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.
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
| Tools | Support Language | Cost | Partners |
|—|—|—|—|—|
| Squish Coco | C, C++, C#, SystemC, Tcl and QML | Not disclosed |Botom of this page Selected Clients|
| BullseyeCoverage | C, C++ |$800 for 1-year license and up | |
| Testwell| C, C++, C#, Java| Not disclosed| |
| Parasoft C/C++test |C, C++ | Not disclosed | partners |
| VECTOR Code Coverage | C, C++ | Not disclosed (free trial available)| partners |
|JaCoCo| Java | Open Source| Most famous code coverage tool in Java area |
最近遇到一个 regression bug,是产品完成构建之后,build commit number 不对,显示的 HEAD 而不是常见的 97b34931ac HASH number,这是什么原因呢?
我检查了 build 脚本没有发现问题,branch 的输出是正确的,那我怀疑是引入 Jenkins 的原因,果然登录到远程的 agent 上去查看分支名称如下:
C:\workspace\blog>git branch |
果然问题出在了 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 脚本,就跟上面的脚本一样了。
实现 CI/CD 过程中,常常需要将构建好的 build 上传到一个公共的服务器,供测试、开发来获取最新的 build。如何上传 build 成果物到 FTP server,又不想把 FTP server登录的用户名和密码存在脚本里,想做这样的参数化如何实现呢?
upload_to_ftp.bat [hostname] [username] [password] [local_path] [remote_pat] |
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
Description: Copyright format:1995—2019
stage('change copyrigh') { |
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') { |
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') { |
push change to Git
stage('git push to Git') { |
Whole Jenkins Pipeline looks like:
pipeline { |
$ java -version |
Items | Settings |
---|---|
Name | Linux-build-machine |
Description | used for Linux build |
of executors | 1 |
Remote root directory | /home/agent |
Labels | Linux, build |
Usage | Use this node as much as possible |
Launch method | Launch agent agents via SSH |
Host | 192.168.1.112 |
Credentials | username/password |
Host Key Verification Strategy | Manually trusted key Verification Strategy |
Availability | Keep this agent online as much as paossible |
credentials | configuration |
---|---|
Domain | Global credentials (unrestricted) |
Kind | Username with password |
Scope | Global(Jenkins, nodes, items, all child items, etc) |
Username | root |
Password | mypassword |
Description | Linux agent username & password |
Remoting version: 3.29 |
Problem | how to fix |
---|---|
[04/22/19 23:15:07] [SSH] WARNING: No entry currently exists in the Known Hosts file for this host. Connections will be denied until this new host and its associated key is added to the Known Hosts file. | ssh-keyscan HOSTNAME >> known_hosts |
/var/lib/jenkins/.ssh/known_hosts [SSH] No Known Hosts file was found at /var/lib/jenkins/.ssh/known_hosts. | changing the Host key verification strategy in LAUNCH METHOD from “Known Hosts file verification strategy” to “Manually trusted key verification strategy” |
JAVA_HOME=C:\Program Files\Java\jdk1.8.0_201 |
Items | Settings |
---|---|
Name | window-build-machine |
Description | used for windows build |
of executors | 1 |
Remote root directory | C:\agent |
Labels | windows, build |
Usage | Use this node as much as possible |
Launch method | Let Jenkins control this Windows slave as a Windows service |
Administrator user name | .\Administrator |
Password | mypassword |
Host | 192.168.1.111 |
Run service as | Use Administrator account given above |
Availability | Keep this agent online as much as paossible |
[2019-05-11 01:32:50] [windows-slaves] Connecting to 192.168.1.111 |
The following issues I met and how I fixed them.
You need need to install JDK, and config JAVA environment variable.
Ref to JENKINS-16418.
Fixed permission for the following registry keys
Steps to fix it
Repeat the above steps to fix permission for HKEY_CLASSES_ROOT\CLSID{76A64158-CB41-11D1-8B02-00600806D9B6}
Finally, Restart Remote Registry Service (Administrative Tools / Services).
This is probably a bug in Jenkins.
jenkinsslave-C__agent
Slave under domain account, If your slave is running under a domain account and you get an error code 0x800703FA, change a group policy:
Need to enable SMB1
You’ll be asked to restart your computer as part of this process.
Need to upgrade your .NET Framework. Here is a link for update .NET Framework.
Please refer to this link https://github.com/jenkinsci/windows-slaves-plugin/blob/master/docs/troubleshooting.adoc