用户无法修改 Hudson 创建的文件
我在 Tomcat 上部署了 Hudson。 Tomcat 作为 Windows 服务在用户 HUDSON_USER 下启动。 因此，只有 HUDSON_USER 可以完全访问从 Hudson 的某些作业创建的文件。 所有其他用户仅具有读取权限。 是否可以配置 Hudson 或 Tomcat 或 Windows，以便所有其他用户拥有对 Hudson 工件的写访问权限或完全访问权限？
I have a Hudson deployed on Tomcat.
Tomcat is started as Windows service under user HUDSON_USER.
As result only HUDSON_USER has full access to files created from some Hudson's job.
All other users have only read access.
Is it possible configure Hudson or Tomcat or Windows in order all other users have write access or full access to Hudson's artifacts?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
听起来您需要右键单击根文件夹以及 hudson 放置其构建工件的位置，然后单击属性，然后单击安全选项卡。添加所需用户的权限，确保还单击“高级”，然后选中“从父对象继承适用于子对象的权限条目...”和“替换所有子对象上的权限条目...”
或者，您可以在本地托管一个构建存储库以将工件上传到（因为 Hudson 可以选择上传到存储库），然后开发人员在运行本地 Maven 构建时就可以下载他们所需的版本。不过，第二个选项会得到我的投票...
例如： http://archiva.apache.org/
Sounds like you would need to right-click on the root folder and of where hudson is placing its build artifacts, then click properties, then click the security tab. Add the permissions of the users you require, make sure you also click advanced, and check "Inherit from parent the permissions entries that apply to child objects..." and "replace permission entries on all child objects...."
Alternatively, you could host a build repository locally to upload the artifacts to (as Hudson has an option to upload to a repository), and then developers would be able to download the versions they require when they run their local maven builds. The second option would get my vote though...
For instance: http://archiva.apache.org/
您可以通过 HTTP 访问工件，例如
http://hudson/job/my-project/lastSuccessfulBuild/artifact/*zip*/archive.zip我不确定您为什么要写无论如何，直接进入 Hudson 的工作空间；如果您想从构建中移动或检索文件，则只读访问是有意义的。
否则，如果您确实需要更改文件系统的权限，您可以告诉 Hudson
chmod您想要的任何文件。You can access the artifacts over HTTP, e.g.
http://hudson/job/my-project/lastSuccessfulBuild/artifact/*zip*/archive.zipI'm not sure why you would want to write directly into Hudson's workspace anyway; read-only access makes sense if you want to move or retrieve the files from a build.
Otherwise if you really do need to change permissions on the filesystem, you could tell Hudson to
chmodwhichever files you want.