Bug 476323 - Migrate or remove Hudson jobs on the shared instance
Summary: Migrate or remove Hudson jobs on the shared instance
Status: CLOSED FIXED
Alias: None
Product: MMT.ATL
Classification: Modeling
Component: Engine (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: mmt-atl.toolkit-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 412933
  Show dependency tree
 
Reported: 2015-09-01 09:55 EDT by Mikaël Barbero CLA
Modified: 2015-09-03 06:09 EDT (History)
2 users (show)

See Also:


Attachments

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:55:06 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/m2m-atl-master/

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 William Piers CLA 2015-09-02 11:49:56 EDT
Hello Mikaël !

I tried to log in the new shared instance but failed to authenticate, despite using the same login/mdp (of my eclipse account) that in the old build.
Did I miss a step ? Thanks in advance
Comment 2 Mikaël Barbero CLA 2015-09-02 12:07:49 EDT
The new shared instance requires you to login with your email address rather than your unix account name. I'm afraid it won't help a lot to log into this new instance before you asked me to migrate the old ATL job ;)
Comment 3 William Piers CLA 2015-09-03 03:47:01 EDT
ok :-)

So, could you please migrate the old job to the shared instance ? Thanks in advance.
Comment 4 Mikaël Barbero CLA 2015-09-03 05:38:13 EDT
Job has been migrated to the new shared instance at https://hudson.eclipse.org/shared/job/mmt-atl-master. I started a nightly build to check everything is alright. I got a green one (https://hudson.eclipse.org/shared/job/mmt-atl-master/lastBuild/console) so it should be ok. Could you please check on your side?

Please tell me when I can remove the job on the old shared instance. Thanks.
Comment 5 William Piers CLA 2015-09-03 06:03:05 EDT
I can login & build, all is ok. Thanks
You can remove the old build.
Comment 6 Mikaël Barbero CLA 2015-09-03 06:09:59 EDT
Done. Thanks