为什么 Jenkins 中的一些指纹文件被定义为“Jenkins 外部”？
我有几个 Jenkins 作业系列，它们与指纹文件绑定在一起。当对文件进行指纹识别时，Jenkins 将指示哪个作业源自指纹，并将其用作绑定（即升级）的基础。
但我有一项工作可以构建可识别指纹的文件（与其他工作没有什么不同）并将该文件标记为可识别指纹。但是，当 Jenkins 显示此作业的指纹时，列出的文件来源为“Jenkins 外部”。
该文件肯定是首先在 Jenkins 中进行指纹识别的。进行第一个指纹识别的作业/构建尚未被删除。这项工作在功能、插件使用和脚本方面与其他工作得很好的工作几乎相同。
有谁知道为什么会发生这种情况？
I have several series of Jenkins jobs that are bound together along fingerprinted files. When a file is fingerprinted, Jenkins will indicate which job originated the fingerprint, and that is used as a basis for the bindings, namely promotions.
But I've got one job that builds a fingerprintable file (nothing different from other jobs) and flags the file to be fingerprinted. But when Jenkins shows the fingerprints for this job, the file is listed with an orign of "outside Jenkins".
The file was definitely first fingerprinted in Jenkins. The job/build that did the first fingerprinting has not been deleted. And this job is pretty much identical in function, plugin usage, and scripts to other jobs that work just fine.
Does anyone know why this happens?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论