Hudson/Jenkins--如何自定义build name

最新推荐文章于 2025-02-28 15:56:40 发布
原创 最新推荐文章于 2025-02-28 15:56:40 发布 · 6.4k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文介绍如何使用DescriptionSetterPlugin及BuildNameSetter插件为Jenkins的任务构建赋予更有意义的名称，提升构建流程的可读性。

Hudson/Jenkins的job的默认的build name一般都是基于时间格式的，如何在给出一个比时间更具有意义的build name呢，可以利用以下2个插件：


Description Setter Plugin

下载地址：https://wiki.jenkins-ci.org/display/JENKINS/Description+Setter+Plugin

该plugin利用正则匹配，从console log中选取相应的字符串作为build name，如下图所示



Build Name Setter

下载地址：https://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin

该plugin可以从job workspace的property file中读取对应的字段设置build name。因此，我们可以首先利用代码生成一个简单的property文件，其中定义好build version，然后做如下配置：


上图中，我们在job的第一步用代码生成一个build.txt的property文件，其中定义了一对key-value：buildversion=xxx；在Hudson/Jenkins中选择profile，文件名和要提取的property，但build结束时，该字段的值就会作为这个build的name。


43-Jenkins-修改当前构建名称和描述
小白的博客
11-30 1540
Jenkins-修改当前构建名称和描述
Jenkins实践(9):配置“构建历史的显示名称,加上包名等信息“
fen_fen的专栏
05-23 624
Jenkins实践(9):配置“构建历史的显示名称,加上包名等信息“
jenkins 可以使用自定义的pom名称构建项目
mrluoxj的专栏
09-15 788
但是如果两种方式的依赖和插件相差很大，这时候可能要在同一个maven项目中同时存在两个pom.xml文件。这时候构建docker镜像的pom.xml可以重命名为 pom_createImage.xml放在项目中。jenkin里面构建的pom名称直接填写pom_createImage.xml就行了。两种方式可以使用同一个pom.xml 使用 标签来做区分。比如可以构建为jar包的方式，还有直接构建docker镜像的方式。这样不影响maven项目直接使用默认pom.xml构建jar包。
Jenkins build 设定名字
huanlegu0426的专栏
01-11 4583
 Set a name for a Jenkins build. The name will be showing Build History like below: Configure-> Post Steps  -> check "User macro" -> set Build name macro templates as  #${BUILD_NUMBER}-...
jenkins插件学习之build-name-setter-plugin
马哥私房菜
04-25 1362
jenkins插件学习之BuildUserVars和BuildNameDescriptionSetter插件执行顺序 之前一直在使用 BuildUserVars 和 BuildNameDescriptionSetter 这2个插件, 通过 BuildUserVars 能够获取到是哪个人触发了构建.这个插件会设置个类似的环境变量 BUILD_USER. 然后 通过 BuildNameDescri...
Jenkins构建历史中的Build Name设置
weixin_43997319的博客
07-08 2110
在项目的构建历史中，只能看到项目的构建号和构建时间。 系统管理->插件管理->搜索框输入user build vars后点击安装user build vars 此插件用于设置用户构建变量：jenkins用户名和ID等。重启后生效 系统管理->插件管理->搜索框输入Build Name and Description Setter后点击安装Build Name and Description Setter 此插件用于修改构建的显示名称（修改之前为默认的#1,#2,#3…）安装后重启jenkins服务才能生效接
01:42:32 Started by user Admin 01:42:32 Running as SYSTEM 01:42:32 Building on the built-in node in workspace E:\Jenkins\workspace\UE\5.5.4\Echo_BuildForUGS_01 01:42:32 Executor number at runtime: 0 01:42:32 ... p4 login + 01:42:32 ... p4 login -s + 17:33:14 ... p4 client -o Jenkins-Build-Echo-UE-5.5.4 + 17:33:14 ... p4 info + 17:33:14 ... p4 info + 17:33:14 ... p4 client -o Jenkins-Build-Echo-UE-5.5.4 + 17:33:15 ... p4 client -i + 17:33:15 ... View: + 17:33:15 ... p4 counter change + 17:33:15 ... p4 changes -m1 -ssubmitted //Jenkins-Build-Echo-UE-5.5.4/...@650 + 17:33:16 P4: found 650 revision in //Jenkins-Build-Echo-UE-5.5.4/...@650 17:33:16 ... p4 changes -m1 -ssubmitted //Jenkins-Build-Echo-UE-5.5.4/...@1,650 + 17:33:19 P4: found 650 revision in //Jenkins-Build-Echo-UE-5.5.4/...@1,650 17:33:19 ... p4 repos -C + 17:33:19 P4: builds: 650 17:33:19 ... p4 login + 17:33:19 ... p4 login -s + 17:33:19 ... p4 client -o Jenkins-Build-Echo-UE-5.5.4 + 17:33:19 ... p4 info + 17:33:19 ... p4 info + 17:33:19 ... p4 client -o Jenkins-Build-Echo-UE-5.5.4 + 17:33:19 17:33:19 P4 Task: establishing connection. 17:33:19 ... server: ssl:192.168.2.4:1668 17:33:19 ... node: a849e4696f69 17:33:19 Building on Node: built-in 17:33:19 ... p4 login + 17:33:19 ... p4 login -s + 17:33:19 ... p4 client -o Jenkins-Build-Echo-UE-5.5.4 + 17:33:19 ... p4 info + 17:33:19 ... p4 info + 17:33:19 ... p4 client -o Jenkins-Build-Echo-UE-5.5.4 + 17:33:19 17:33:19 P4 Task: establishing connection. 17:33:19 ... server: ssl:192.168.2.4:1668 17:33:19 ... node: a849e4696f69 17:33:19 17:33:19 P4 Task: reverting all pending and shelved revisions. 17:33:19 ... p4 revert E:\Jenkins\workspace\UE\5.5.4\Echo_BuildForUGS_01/... + 17:33:19 P4 Task: attempt: 1 01:33:22 ERROR: P4: Task Exception: hudson.AbortException: P4JAVA: Error(s): 01:33:22 Path '/E:\Jenkins\workspace\UE\5.5.4\Echo_BuildForUGS_01/...' is not under client's root 'E:\Jenkins\workspace\UE\5.5.4\Echo_BuildForUGS_01'. 01:33:22 01:33:25 Finished:
03-26
Client name: jenkins-client-prod Root: /opt/jenkins/workspaces/p4_prod # 必须是绝对路径 ``` 2. **验证工作区视图映射** - 在 Perforce 客户端执行 `p4 client` 命令查看视图 - 确保映射规则不包含越界...
自定义 jenkins jnlp-slave 镜像
Man_In_The_Night的博客
12-23 2952
环境：centos7.6 、Docker version 19.03.5、Jenkins 2.263.1、jenkins url 172.28.31.214:8080 完整 github 项目 1、从 https://repo.jenkins-ci.org/public/org/jenkins-ci/main/remoting 下载对应版本的 remoting.jar，重命名为 slave.jar, 此处使用 https://repo.jenkins-ci.org/public/org/jenkins-c
Running as SYSTEM Building on the built-in node in workspace /var/jenkins_home/workspace/Tapo_test [Tapo_test] $ /bin/sh -xe /tmp/jenkins4030103379424762008.sh + env JENKINS_HOME=/var/jenkins_home JENKINS_UC_EXPERIMENTAL=https://updates.jenkins.io/experimental CI=true RUN_CHANGES_DISPLAY_URL=http://10.0.138.175/job/Tapo_test/7/display/redirect?page=changes HOSTNAME=45104600b3f3 NODE_LABELS=built-in SHLVL=0 HUDSON_URL=http://10.0.138.175/ HOME=/var/jenkins_home BUILD_URL=http://10.0.138.175/job/Tapo_test/7/ JENKINS_SERVER_COOKIE=b6155e08db5e2646 HUDSON_COOKIE=ea41a46d-1976-4e58-a6f7-581f13e8834d JENKINS_UC=https://updates.jenkins.io REF=/usr/share/jenkins/ref WORKSPACE=/var/jenkins_home/workspace/Tapo_test NODE_NAME=built-in RUN_ARTIFACTS_DISPLAY_URL=http://10.0.138.175/job/Tapo_test/7/display/redirect?page=artifacts DOCKERFILE_LOCATION=dockerfile/ EXECUTOR_NUMBER=0 BUILD_DISPLAY_NAME=#7 JENKINS_INCREMENTALS_REPO_MIRROR=https://repo.jenkins-ci.org/incrementals JENKINS_VERSION=2.516.3 RUN_TESTS_DISPLAY_URL=http://10.0.138.175/job/Tapo_test/7/display/redirect?page=tests HUDSON_HOME=/var/jenkins_home JOB_BASE_NAME=Tapo_test PATH=/opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin BUILD_ID=7 BUILD_TAG=jenkins-Tapo_test-7 LANG=C.UTF-8 JENKINS_URL=http://10.0.138.175/ JOB_URL=http://10.0.138.175/job/Tapo_test/ BUILD_NUMBER=7 JENKINS_SLAVE_AGENT_PORT=50000 RUN_DISPLAY_URL=http://10.0.138.175/job/Tapo_test/7/display/redirect HUDSON_SERVER_COOKIE=b6155e08db5e2646 JOB_DISPLAY_URL=http://10.0.138.175/job/Tapo_test/display/redirect JOB_NAME=Tapo_test COPY_REFERENCE_FILE_LOG=/var/jenkins_home/copy_reference_file.log JAVA_HOME=/opt/java/openjdk PWD=/var/jenkins_home/workspace/Tapo_test WORKSPACE_TMP=/var/jenkins_home/workspace/Tapo_test@tmp + BRANCH_NAME=Tapo/H500 + which python3 Build step 'Execute shell' marked build as failure Archiving artifacts Stopping all containers Finished: FAILURE
12-25
docker run -d --name jenkins-agent \ -v /var/jenkins_home:/home/jenkins/agent \ jenkins-agent-python3 ``` 确保 Jenkins 的节点配置中使用了这个新镜像。 --- ### ✅ 方法四：软链接 `python` 到 `python...
Started by user Yilun Wu Running as SYSTEM Building on the built-in node in workspace /var/jenkins_home/workspace/Tapo_test [Tapo_test] $ /bin/sh -xe /tmp/jenkins6431093081201892627.sh + env JENKINS_HOME=/var/jenkins_home JENKINS_UC_EXPERIMENTAL=https://updates.jenkins.io/experimental CI=true RUN_CHANGES_DISPLAY_URL=http://10.0.138.175/job/Tapo_test/5/display/redirect?page=changes HOSTNAME=45104600b3f3 NODE_LABELS=built-in SHLVL=0 HUDSON_URL=http://10.0.138.175/ HOME=/var/jenkins_home BUILD_URL=http://10.0.138.175/job/Tapo_test/5/ JENKINS_SERVER_COOKIE=b6155e08db5e2646 HUDSON_COOKIE=a4c855f7-07d4-4936-879f-ba66a76ca71d JENKINS_UC=https://updates.jenkins.io REF=/usr/share/jenkins/ref WORKSPACE=/var/jenkins_home/workspace/Tapo_test NODE_NAME=built-in RUN_ARTIFACTS_DISPLAY_URL=http://10.0.138.175/job/Tapo_test/5/display/redirect?page=artifacts DOCKERFILE_LOCATION=dockerfile/ EXECUTOR_NUMBER=0 BUILD_DISPLAY_NAME=#5 JENKINS_INCREMENTALS_REPO_MIRROR=https://repo.jenkins-ci.org/incrementals JENKINS_VERSION=2.516.3 RUN_TESTS_DISPLAY_URL=http://10.0.138.175/job/Tapo_test/5/display/redirect?page=tests HUDSON_HOME=/var/jenkins_home JOB_BASE_NAME=Tapo_test PATH=/opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin BUILD_ID=5 BUILD_TAG=jenkins-Tapo_test-5 LANG=C.UTF-8 JENKINS_URL=http://10.0.138.175/ JOB_URL=http://10.0.138.175/job/Tapo_test/ BUILD_NUMBER=5 JENKINS_SLAVE_AGENT_PORT=50000 RUN_DISPLAY_URL=http://10.0.138.175/job/Tapo_test/5/display/redirect HUDSON_SERVER_COOKIE=b6155e08db5e2646 JOB_DISPLAY_URL=http://10.0.138.175/job/Tapo_test/display/redirect JOB_NAME=Tapo_test COPY_REFERENCE_FILE_LOG=/var/jenkins_home/copy_reference_file.log JAVA_HOME=/opt/java/openjdk PWD=/var/jenkins_home/workspace/Tapo_test WORKSPACE_TMP=/var/jenkins_home/workspace/Tapo_test@tmp + BRANCH_NAME=Tapo/H500 + command -v repo + echo Installing repo tool from Google... Installing repo tool from Google... + mkdir -p /var/jenkins_home/.bin + export PATH=/var/jenkins_home/.bin:/opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin + curl https://storage.googleapis.com/git-repo-downloads/repo % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 44952 100 44952 0 0 297k 0 --:--:-- --:--:-- --:--:-- 296k + chmod a+rx /var/jenkins_home/.bin/repo + echo Repo tool installed successfully Repo tool installed successfully + [ ! -d .repo/repo ] + echo Repo not initialized or incomplete, setting up... Repo not initialized or incomplete, setting up... + rm -rf .repo CAMEOS#Remove Any dirs related to source code + NEED_INIT=true + git config --global user.name Jenkins CI + git config --global user.email jenkins@tp-link.com + git config --global color.ui false + export REPO_NO_SELF_UPDATE=1 + export GIT_TERMINAL_PROMPT=0 + export GIT_SSH_COMMAND=ssh -o BatchMode=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null + [ true = true ] + echo Running repo init (first time)... Running repo init (first time)... + repo init -u ssh://gerrit/manifests/CEE -b Tapo/H500 -m manifest.xml /usr/bin/env: ‘python3’: No such file or directory Build step 'Execute shell' marked build as failure Archiving artifacts Stopping all containers Finished: FAILURE
12-25
docker run -d --name jenkins-agent -v /var/jenkins_home:/home/jenkins/agent jenkins-agent-with-python ``` #### 4. **重启 Jenkins Agent** 更新完环境后，重启 Jenkins Agent 以确保新环境生效： - 可以在...
Started by user Yilun Wu Running as SYSTEM Building remotely on aws-test-agent in workspace /build/jenkins/workspace/Tapo_test [Tapo_test] $ /bin/sh -xe /tmp/jenkins7538228438322689453.sh + env JENKINS_HOME=/var/jenkins_home SSH_CLIENT=10.0.138.175 35804 22 USER=ubuntu CI=true RUN_CHANGES_DISPLAY_URL=http://10.0.138.175/job/Tapo_test/12/display/redirect?page=changes XDG_SESSION_TYPE=tty NODE_LABELS=aws-test-agent SHLVL=0 HUDSON_URL=http://10.0.138.175/ HOME=/home/ubuntu OLDPWD=/home/ubuntu BUILD_URL=http://10.0.138.175/job/Tapo_test/12/ JENKINS_SERVER_COOKIE=b6155e08db5e2646 HUDSON_COOKIE=85d8cc3c-c9e5-44dc-9f70-6bed703cd934 DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus WORKSPACE=/build/jenkins/workspace/Tapo_test LOGNAME=ubuntu NODE_NAME=aws-test-agent RUN_ARTIFACTS_DISPLAY_URL=http://10.0.138.175/job/Tapo_test/12/display/redirect?page=artifacts DOCKERFILE_LOCATION=dockerfile/ _=/usr/bin/java XDG_SESSION_CLASS=user EXECUTOR_NUMBER=3 XDG_SESSION_ID=78 BUILD_DISPLAY_NAME=#12 RUN_TESTS_DISPLAY_URL=http://10.0.138.175/job/Tapo_test/12/display/redirect?page=tests HUDSON_HOME=/var/jenkins_home JOB_BASE_NAME=Tapo_test PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin BUILD_ID=12 XDG_RUNTIME_DIR=/run/user/1000 BUILD_TAG=jenkins-Tapo_test-12 LANG=C.UTF-8 JENKINS_URL=http://10.0.138.175/ JOB_URL=http://10.0.138.175/job/Tapo_test/ BUILD_NUMBER=12 SHELL=/bin/bash RUN_DISPLAY_URL=http://10.0.138.175/job/Tapo_test/12/display/redirect HUDSON_SERVER_COOKIE=b6155e08db5e2646 JOB_DISPLAY_URL=http://10.0.138.175/job/Tapo_test/display/redirect JOB_NAME=Tapo_test PWD=/build/jenkins/workspace/Tapo_test SSH_CONNECTION=10.0.138.175 35804 10.0.131.164 22 WORKSPACE_TMP=/build/jenkins/workspace/Tapo_test@tmp + BRANCH_NAME=Tapo/H500 + exit 0 [Tapo_test] $ /bin/bash /tmp/jenkins3730405176305069181.sh [Tapo_test] $ /bin/sh -xe /tmp/jenkins17343858980407599494.sh + echo === Preparing artifacts for Jenkins Archive Plugin === === Preparing artifacts for Jenkins Archive Plugin === + mkdir -p /build/jenkins/workspace/Tapo_test/artifacts + rm -rf /build/jenkins/workspace/Tapo_test/artifacts/* + cd CAMEOS/image/H500 /tmp/jenkins17343858980407599494.sh: 9: cd: can't cd to CAMEOS/image/H500 Build step 'Execute shell' marked build as failure Archiving artifacts Stopping all containers Finished: FAILURE
最新发布
12-25
cd /build/jenkins/workspace/Tapo_test/CAMEOS/image/H500 ``` --- ### ✅ 示例修复后的脚本 ```bash echo "Current directory: $(pwd)" echo "Listing workspace contents:" ls -la # 检查目标目录是否存在 ...
【jenkins】第八篇：jenkins设置构建历史中得build_name
西原一点红的博客
08-21 441
jenkins设置构建历史中得build_name
Jenkins修改BuildName的2种方法
在服务器上挂载OSS_bucket
01-11 2074
方法一：常规项目->配置->构建环境->Set Build Name 修改配置 方法二：Pipeline项目->在stages里面加一个stage stages { stage('Initialization'){ steps{ buildName "${BUILD_NUMBER}-${BRANCH_NAME}" } } } 以上2种方法改完，显示的时候，可能会有字母换行的问题，还需要改一下CSS。 系统管理
[jenkins]-pipeline 修改build name 和 description
爷来辣的博客
06-13 4481
[jenkins]-pipeline 修改build name 和 description 效果如下 流水线脚本写的有点粗糙 哪里修改build name 和 description 均备注了 // Using git without checkout pipeline { agent any parameters { gitParameter branchFilter: 'origin/(.*)', defaultValue: 'master', name: 'Branch', sor
jenkins使用插件在Build History打印基本信息
qq_31292011的博客
02-28 782
$BUILD_USER</span><br> 构建分支：<span style="color:green;">提交信息：
Jenkins项目插件演示效果
madeByOurselves的博客
08-29 483
Jenkins项目插件演示效果
使用 Jenkins 搭建 iOS/Android 持续集成打包平台
DJ355的博客
07-30 811
在软件开发过程中，持续集成是一个非常重要的环节。而在持续集成过程中，使用 Jenkins 是一个非常实用的工具。Jenkins 是一个开源持续集成工具，可以用来自动化测试和构建软件。它提供了一些简单易用的方法来构建持续集成流程，并可以自动化构建应用程序。本文主要是对如何使用 Jenkins 搭建 iOS/Android 持续集成打包平台的基础概念和实施流程进行了介绍。
Jenkins Description Setter插件，用于改善连续交付的可见性
danpu0978的博客
04-16 936
在持续交付中，每个构建都可以交付 。 这个事实意味着，除其他外，要尽可能快地为您的组件分配无快照版本，以便您可以在所有过程中引用它们。 我建议创建一个发布分支，将版本分配给项目，然后启动典型的管道（编译，测试，代码质量……）步骤来发布分支。 如果您使用的是Jenkins ，那么您的构建作业屏幕将类似于： 请注意，我们已经发布了该项目很多次，但是没有一种快速的方法来确切地知道在版本号...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值