Jenkins SYSTEM用户删除自定义工作空间配置 [英] Jenkins SYSTEM user removes custom workspace configuration

问题描述

我有一个配置为使用customWorkspace D:\ builds \ build-dir \ Quick-Winx64-Trunk的NightlyTest-Winx64作业.

I have a job NightlyTest-Winx64 configured to use the customWorkspace D:\builds\build-dir\Quick-Winx64-Trunk.

Quick-Winx64-Trunk是Jenkins中的一项工作，它将签出源存储库，进行编译，归档一些工件，然后触发NightlyTest-Winx64任务.它会触发NightlyTest-Winx64在使用相同工作空间的同一节点上运行，因此我们无需检出并编译两次，而只需要运行测试即可.

Quick-Winx64-Trunk is a job in Jenkins that will checkout the source repository, compile, archive some artifacts and then trigger the NightlyTest-Winx64 job. It triggers NightlyTest-Winx64 to run on the same node using the same workspace so that we're not checking out and compiling twice and only need to run test.

在NightlyTest-Winx64的第一次运行中，customWorkspace存在并且按预期使用.但是，在首次运行期间，SYSTEM用户将从作业中删除customWorkspace配置.结果，所有后续的NightlyTest-Winx64构建都将在不正确的默认工作区中运行.

On the first run of the NightlyTest-Winx64 the customWorkspace exist and is used as expected. However during this first run the SYSTEM user removes the customWorkspace configuration from the job. As a result all subsequent builds of NightlyTest-Winx64 will run in the default workspace which is incorrect.

有人在以前遇到过此行为吗，为什么SYSTEM用户会更改我的作业配置?

Has anyone encountered this behavior before and why is the SYSTEM user changing my job configuration?

推荐答案

在使用Quick的工作区触发Nightly的两个插件之间发生冲突.

It was a conflict between two of the plugins I was using to trigger the Nightly using the workspace of the Quick.

以前的配置:

• 使用节点名称"作为参数从Quick触发参数化构建(参数化触发器插件) https://wiki.jenkins-ci.org/display/JENKINS/Parameterized + Trigger +插件
• 在每晚，期望一个参数节点并将customWorkspace设置为快速的节点
• 在构建环境"下，选择在与...相同的节点上运行"并共享相同的工作空间(Node Stalker插件) https://wiki.jenkins-ci.org/display/JENKINS/Node + Stalker +插件

• Trigger parameterized build from Quick with Node name as parameter (Parameterized Trigger Plugin) https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin
• On Nightly expect one parameter node and set customWorkspace to that of the quick
• Under Build Environment select Run on same node as.. and share same workspace (Node Stalker Plugin) https://wiki.jenkins-ci.org/display/JENKINS/Node+Stalker+Plugin

节点跟踪者正在充当SYSTEM用户并进行配置更改.使用上述两个插件都是多余的，因此导致了冲突.

Node stalker was acting as the SYSTEM user and making the configuration changes. Using both of the above plugins was redundant and as a result caused the conflict.

新配置:

• 无参数的快速触发构建(内置到Jenkins中)
• 使用Node跟踪跟踪器插件为Nightly获取正确的节点和工作区

这篇关于Jenkins SYSTEM用户删除自定义工作空间配置的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！