Description Mikaël Barbero 2015-09-01 10:02:48 EDT

We are in the process to deprecate the current Hudson shared instance at Eclipse (see bug 412933 for details). You have the following jobs on this instance:

* https://hudson.eclipse.org/hudson/job/mihini-nightly/

We offer two migration paths for these jobs:
* Use the new up to date Hudson shared instance at https://hudson.eclipse.org/shared/. It is a recent Hudson installation configured the same way as the old instance was to minimize migration work.
* Use a dedicated Hudson instance for each of these projects (what we call a HIPP, Hudson Instance Per Project). This way, you can create as many jobs as you want, install all the Hudson plugins you want, etc. This is the preferred path of migration as the shared instance (old or new) will be deprecated in the mid term. See https://wiki.eclipse.org/Hudson#HIPP for more details.

Whatever the path you choose, the plan is: 
* first to copy the job to the new instance (shared or HIPP). 
* make it work
* deactivate the job on the old shared instance
* after a while without issue and after validation from your side, remove the job from the old shared instance.

What is your preferred way? Is there any preferred time when I can do the migration? Is there any useless job that could be nuked?

Thanks.