hudson svn 发布者插件不起作用
我正在尝试使用 SVN Publisher 插件提交一些工件我的构建，但我收到了一个无意义的错误：
workspace: /Users/builder/hudson/workspace/myproject/
Attempting to import to SVN: https://mysvnrepo.com/svn/myproject/_SNAPSHOT_
SVN Publisher: target: /Users/builder/hudson/workspace/myproject/myproject/_build
SVN Publisher: Error: target Directory not accessable: /Users/builder/hudson/workspace/myproject/myproject/_build
Hudson Slave 正在使用的用户可以读取此路径。
在查看 SVN Publisher 页面上的评论时，似乎有些人们遇到过这个问题，而其他人则没有。
我的问题是：对于那些已经让它发挥作用的人来说，你们做了什么？
I'm trying to use the SVN Publisher plugin to commit some artifacts of my build but I'm getting a non-sensical error:
workspace: /Users/builder/hudson/workspace/myproject/
Attempting to import to SVN: https://mysvnrepo.com/svn/myproject/_SNAPSHOT_
SVN Publisher: target: /Users/builder/hudson/workspace/myproject/myproject/_build
SVN Publisher: Error: target Directory not accessable: /Users/builder/hudson/workspace/myproject/myproject/_build
This path is readable by the user that the hudson slave is using.
In looking at the comments on the SVN Publisher page, it seems that some people have run across this problem while others have not.
My question is: for those of you that have gotten it to work, what did you do?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
即使构建使用从服务器，该插件似乎也在 Hudson 服务器上运行。这似乎是 SVN Publisher 插件中的一个错误。 :(
It seems that the plugin is running on the hudson server even though the build is using slaves. This seems to be a bug in the SVN Publisher plugin. :(
看起来您应该能够利用“将文件复制回主节点上的作业工作区”将这些文件返回到服务器（这部分对我有用）。它似乎发生在 SVN Publisher 运行后，但这没关系，只是意味着 SVN Publisher 应该提交（或导入）以前的版本。但可惜的是，SVN 发布者除了记录消息之外似乎没有做任何事情。
It looks like you should be able to utilize the "Copy files back to the job's workspace on the master node" to get these files back to the server (this part works for me). It appears to happen after SVN Publisher is run, but that would be OK and simply means that SVN publisher should be committing (or importing) the previous build. But alas, SVN publisher doesn't seem to be doing anything except logging a message.