Bug 476308 - Migrate or remove Hudson job on the shared instance
Summary: Migrate or remove Hudson job on the shared instance
Status: RESOLVED FIXED
Alias: None
Product: CBI
Classification: Technology
Component: CBI p2 Repository Aggregator (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: CBI Inbox CLA
QA Contact: David Williams CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 412933
  Show dependency tree
 
Reported: 2015-09-01 09:05 EDT by Mikaël Barbero CLA
Modified: 2016-09-16 16:07 EDT (History)
3 users (show)

See Also:


Attachments
Old configs (623 bytes, text/xml)
2015-12-23 06:26 EST, Mikaël Barbero CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mikaël Barbero CLA 2015-09-01 09:05:07 EDT
We are in the process to deprecate the current Hudson shared instance at Eclipse (see bug 412933 for details). You have the following job on this instance:

* https://hudson.eclipse.org/hudson/job/emft-b3-build/

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.
Comment 1 Mikaël Barbero CLA 2015-10-09 05:54:57 EDT
The removal of the old shared instance is planned for Dec 14th. Did you decide what to do with these jobs?
Comment 2 Thomas Hallgren CLA 2015-10-09 07:54:35 EDT
I think moving the job to the new shared hudson would will be best.
Comment 3 Mikaël Barbero CLA 2015-10-09 08:28:02 EDT
Thanks Thomas for the feedback. Henrik, as you are the project lead, is it ok for you?
Comment 4 Mikaël Barbero CLA 2015-11-25 05:29:24 EST
Thomas, do you know if Henrik is still active on the project? His email is still @cloudsmith but I think he is not working there anymore. Do you still have contact with him? With the approaching shutdown date, we really need to go forward with this issue.
Comment 5 Henrik Lindberg CLA 2015-11-25 07:47:57 EST
It is ok with me.

(I sort of still work for Cloudsmith; the company was acquired  by Puppet Labs; where I now work.)
Comment 6 Mikaël Barbero CLA 2015-11-25 08:44:24 EST
I've migrated your build to the new shared instance (https://hudson.eclipse.org/shared/job/emft-b3-build) and deactivated it from the old one (https://hudson.eclipse.org/hudson/job/emft-b3-build/). Please check that the build is working properly and tell me when I can remove the job from the old shared instance. Thanks.

Note that to log into the new shared instance, the login is now the email address associated with your Eclipse account (and not the user id you were using to connect to the old shared instance).
Comment 7 Mikaël Barbero CLA 2015-12-23 06:26:03 EST
Created attachment 258872 [details]
Old configs

The old shared instance has been shutdown. Please find the configuration of the job(s) as they were before the shutdown.
Comment 8 David Williams CLA 2016-02-08 20:36:01 EST
We can close this as "fixed". I have opened a new bug 487478 to track re-instantiating a build on a HIPP instance.
Comment 9 David Williams CLA 2016-09-16 16:07:47 EDT
[Bookkeeping change only. Moving bugs to the new "home" of aggregator, CBI.
This bug was previous part of "meta" component in EMFT.b3]