更新Hudson和插件 [英] Updating Hudson and plugins

问题描述

我想知道升级hudson和插件的最佳步骤是什么.

我目前正在运行1.347.我曾经尝试进行更新，但由于某些插件不兼容而导致混乱.

我也想删除一些插件，仅删除hpi文件是否合适?很高兴知道其他人如何执行此步骤以及以什么顺序进行.
我应该先升级hudson，然后逐个插件进行升级吗?
而且，如果某个插件再次降级了，该怎么办?似乎需要做很多工作. 还是有任何简单的方法?
保存所有xml配置文件是否足够，以防万一我可以恢复?

谢谢.

解决方案

我的解决方案过高了，但是我被烧了两次(一次是由于Hudson错误，另一次是由于插件不兼容)，并吸取了教训.

我已将Hudson安装在具有与生产实例相同的插件和几个简单构建的VM上.当我觉得是时候进行升级了，或者想查看最新版本时，我在VM上升级了Hudson，并验证了它是否可以启动并可以进行构建.在升级测试系统之后，我才升级所有开发人员使用的生产系统.我通常不会在测试系统上进行详尽的测试；确保已升级的Hudson和插件的组合正确启动就足够了.

在升级VM或主系统时，我将升级所有插件，然后再升级Hudson本身并重新启动. (因为我有一个测试系统，所以我并不特别担心一步一步地做事.)

在哈德森引入降级支持之前，我想出了自己的流程.我仍然使用此过程，因为对我来说重要的是要确信升级不会破坏其他开发人员使用的系统.此设置还使我可以进行实验设置，该设置与主要的Hudson系统是分开的，我认为它很有用.

I was wondering which steps are the best to upgrade hudson and the plugins.

I'm running 1.347 at the moment. I once tried to update which resulted into a mess because some plugins were incompatible.

Also i want to delete some plugins is it appropriate to just delete the hpi file? It would be nice to know how other people do this step and in which order.
Should i first upgrade hudson and then plugin by plugin?
And if a plugin breaks something downgrade it again? It seems to be a lot of work. Or is there any easy way?
Also is it enough to save all the xml configuration files in case something breaks that i can recover?

Thanks in advance.

解决方案

My solution is overkill, but I was burned twice (once by a Hudson bug and once by plugin incompatibilities) and learned my lesson.

I have Hudson installed on a VM with the same plugins as my production instance and a couple of simple builds. When I feel it's time to upgrade, or want to check out the latest release, I upgrade Hudson on the VM and verify that it starts up and can do builds. I only upgrade the production system that all of our developers use after I've upgraded my test system. I generally don't do exhaustive tests on my test system; it's enough to make sure the combination of upgraded Hudson and plugins starts up properly.

When upgrading either the VM or the main system, I upgrade all the plugins, then upgrade Hudson itself and restart. (Since I have a test system, I'm not particularly worried about doing things step by step.)

I came up with my process before Hudson introduced downgrade support. I still use this process because it's important to me to have confidence that an upgrade is not going to break the system that other developers use. This setup also allows me to have an experimental setup that's separate from the main Hudson system, which I find useful.

这篇关于更新Hudson和插件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！