是否可以将 Hudson 配置为在失败时继续其余的构建步骤？
我不希望这在我的日常工作流程中有用，但是当最初为 hudson 配置项目时，有时我希望我可以让它尝试所有构建步骤 - 而不仅仅是在第一次失败后停止。
再次强调，我并不提倡将其用于日常使用 - 只是用于构建的配置。 （我的一个项目大约需要一个小时左右，我不想独立地迭代修复每个构建步骤 - 我想并行修复每个构建步骤。
那么，有没有办法告诉 hudson 继续失败时构建步骤？
I don't expect this to be useful in my day-to-day workflow, but when initially configuring projects for hudson there are times when I wish I could get it to try all the build steps - not just stop after the first failure.
Again, I am not advocating this for everyday use - just for configuration of the builds. (One of my projects takes about an hour or so and I'd rather not have to iterate through fixing each build step independently - I would like to fix each of them in parallel.
So, is there a way to tell hudson to continue the build steps when one fails?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
目前最好的解决方案是修改每个构建步骤，以确保它们无条件返回成功，而不是错误代码。
有一个开放的增强请求可以在 HUDSON-4819 中完全执行您想要的操作
The best solution right now is to modify each of your build steps to make sure they unconditionally return success, instead of an error code.
There is an open enhancement request to do exactly what you want in HUDSON-4819
这实际上在日常工作流程中非常有用。我们使用 Zed Builds And Bugs，它具有此功能。对于每个构建步骤，您只需切换是否希望构建步骤在失败时使构建失败。默认情况下它是打开的（明智的）。
派上用场的是诸如可选步骤之类的事情 - 例如将最终的二进制文件复制到其他分发服务器。有时这些服务器会启动，有时则不会。如果这个特定步骤失败并不重要，但当它失败时，我不希望整个构建失败。
This actually can be quite useful in a day to day workflow. We use Zed Builds And Bugs and it has this feature. For each build step, you simply toggle whether you want the build step to fail the build if it fails. By default it is turned on (sensible).
Where this has come in handy are things like optional steps - e.g. copying final binaries to other distribution servers. Sometimes these servers are up and sometimes not. It doesn't really matter if this particular step fails, but when it does fail, I don't want the whole build to fail.