Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
FIY695
jenkins
提交
95c6693e
J
jenkins
项目概览
FIY695
/
jenkins
与 Fork 源项目一致
从无法访问的项目Fork
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
J
jenkins
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
95c6693e
编写于
3月 18, 2015
作者:
S
Stephen Connolly
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Augment help text to explain when relative paths are OK
上级
98759f53
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
25 addition
and
4 deletion
+25
-4
core/src/main/resources/hudson/model/Slave/help-remoteFS.html
.../src/main/resources/hudson/model/Slave/help-remoteFS.html
+25
-4
未找到文件。
core/src/main/resources/hudson/model/Slave/help-remoteFS.html
浏览文件 @
95c6693e
<div>
<p>
A slave needs to have a directory dedicated to Jenkins. Specify
the
absolute path of this work directory on the slave, such as
'/var/jenkins' or 'c:\jenkins'. This should be a path local to the slave
machine. There's no need for this path to be visible from the master,
under normal circumstances.
the
path of this work directory on the slave. It is best to use
an absolute path, such as '/var/jenkins' or 'c:\jenkins'. This
should be a path local to the slave machine. There's no need for
this path to be visible from the master,
under normal circumstances.
<p>
Slaves do not maintain important data (other than active workspaces
of projects last built on it), so you can possibly set the slave
workspace to a temporary directory. The only downside of doing this
is that you may lose the up-to-date workspace if the slave is turned off.
<p>
If you use a relative path, such as './jenkins-slave', the path will
be relative to the current working directory that the launcher provides.
<ul>
<li>
For launchers where Jenkins controls starting the slave process, such
as SSH, the current working directory will typically be consistent,
i.e. the user's home directory. This means that Jenkins will be able to
rely on the caching of tool installations and workspaces from previous
builds.
</li>
<li>
For launchers where Jenkins has no control over starting the slave
process, such as JNLP, the current working directory may change between
launches of the slave and use of a relative path may prove problematic.
The principle issue encountered when using relative paths with launchers
like JNLP is the proliferation of stale workspaces and tool installation
on the slave machine. This can cause disk space issues.
<i>
Note: there are some cloud providers that specifically use relative
paths with the JNLP launcher to allow for dynamically provisioned pools
of semi-heterogeneous slaves.
</i></li>
</ul>
</div>
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录