Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 543319 - Migrate PolarSys Project Builds to Eclipse CBI
Summary: Migrate PolarSys Project Builds to Eclipse CBI
Status: CLOSED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: CI-Jenkins (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mikaël Barbero CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 541051
  Show dependency tree
 
Reported: 2019-01-09 14:41 EST by Wayne Beaton CLA
Modified: 2020-01-07 03:30 EST (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wayne Beaton CLA 2019-01-09 14:41:14 EST
As part of the process of merging the PolarSys Forge into the Eclipse Forge, we'll need to move the builds off of the PolarSys infrastructure to the Eclipse CBI.

CBI Team: please coordinate with the PolarSys team via the PMC (I've added the PMC Lead in CC).
Comment 1 Frederic Gurr CLA 2019-01-15 07:32:57 EST
Here is a list of things to do:

* fix ServerHost in ProjectServicesDB (hippX.polarsys.org => hippX.eclipse.org)
* fix ProjectID in ProjectServicesDB (polarsys.polarsys.foobar => polarsys.foobar)
* fix Jenkins URL in the Jenkins main config (https://ci.polarsys.org/xxx => https://ci.eclipse.org/xxx)
* make download.polarsys.org available on all hipp machines
* merge download.polarsys.org into download.eclipse.org and keep a (temporary) symlink from download.polarsys.org to download.eclipse.org
* Create a redirection from http(s)://download.polarsys.org/(.*) -> http(s)://download.eclipse.org/(.*)
- create two redirections:
  - hudson.polarsys.org/(.*) -> hudson.eclipse.org/\1 (we might want to consider redirecting to ci.eclipse.org directly?)
  - ci.polarsys.org/(.*) -> ci.eclipse.org/\1

Some of it was just blatantly copied from bug 528043 comment 1. :)

@Mikael: anything I'm missing?
Comment 2 Frederic Gurr CLA 2019-01-15 07:38:54 EST
The CI related merge should take only a few hours, a full day tops.

According to bug 541051 comment 2, there is a Capella release planned for mid/end of January. So I guess we are aiming for the beginning of February to do the merge.
@Benoit: does that sound reasonable?
Comment 3 Frederic Gurr CLA 2019-05-23 10:40:45 EDT
We're planning to do the move on Monday, June 17th, 2019. Please let us know if you have any concerns.
I will sent a separate email to the PMC and project leads.
Comment 4 Frederic Gurr CLA 2019-06-17 08:12:54 EDT
Migration is in progress...
Comment 5 Frederic Gurr CLA 2019-06-18 16:03:01 EDT
The Polarsys JIPP instances are now reachable here:

https://ci.eclipse.org/3p/
https://ci.eclipse.org/capella/
https://ci.eclipse.org/chess/
https://ci.eclipse.org/esf/
https://ci.eclipse.org/kitalpha/
https://ci.eclipse.org/libims/
https://ci.eclipse.org/opencert/
https://ci.eclipse.org/reqcycle/
https://ci.eclipse.org/time4sys/

We are still working on the migration of download.polarsys.org to download.eclipse.org and archive.polarsys.org to archive.eclipse.org.
Comment 6 Frederic Gurr CLA 2019-07-08 14:13:34 EDT
The following redirects are in place:
* hudson.polarsys.org     => ci.eclipse.org
* ci.polarsys.org         => ci.eclipse.org
* download.polarsys.org   => download.eclipse.org
* archive.polarsys.org    => archive.eclipse.org

Please let us know if anything is not working as expected.
Comment 7 Benoit Langlois CLA 2020-01-07 03:15:00 EST
Hello. Have you checked that all projects are migrated on Jiro?
Comment 8 Mikaël Barbero CLA 2020-01-07 03:30:18 EST
No, not all projects are running on JIRO yet, that's a different thing with a different timeline. Projects are getting notified individually when it happens (or happened).