PO2 Imapcts on gitlab

Before PO2

After PO2

What will happen on Day 1

SCO developers account in current Gitlab.solvay.com will be suspended after Day 1
SCO developers account will be created in SCO Gitlab instance before Day 1
SCO projects code will be migrated to SCO Gitlab instance before Day 1
SCO projects code will be archived in current Gitlab instance Gitlab.solvay.com and eventually deleted from the system (after Day 1)
ECO developers account will remain unchanged in current Gitlab instance Gitlab.solvay.com
ECO projects (including TSA projects ) will be remain unchanged in current Gitlab instance

Your account will be created in SCO instance
Your group will be created in SCO instance
Your permission of the group will follow and setup in SCO instance
You will have to import the project from current ECO gitlab instance to SCO gitlab instance by the out of box feature provided by gitlab, the project import is almost instant
You will have to re-setup the project variables, CI/CD variables

No actions will be needed as you will continue to have access to existing ECO gitlab instance

Your account will be remain in ECO gitlab instance as you are from ECO
You will continue to use existing projects in ECO gitlab instance
You can create new sub group/project if you want to split your existing source code

Your account will be created in SCO instance as you are from SCO
Your group will be setup in SCO instance
You will have to import the project from current ECO gitlab instance to SCO gitlab instance by the out of box feature provied by gitlab, the project import is almost instant
You will have to re-setup the project variables, CI/CD variables
You can create new project in SCO instance and serve TSA to ECO

Gitlab SCO will continue to use solvay SSO login, no change required for login to SCO gitlab
However, if you have created personal token, SSH Key, you will be required to regenreate token , SSH key as it's new instance

Since the imported project from ECO to SCO is consider new project, you will have to reconfigure your project variables

If your project stay in ECO instance , no actions required
If your project moved to SCO instance, we have new docker image repo setup, you will have to build new imgae so that it can be used in SCO pipeline, detail repo inf will be shared soon

The SCO gitlab instance will be ready before DAY 1 (final date will be communicated / updated)

The best option to also migrate the historical records of Merge request , Pipeline jobs is to use the export/import feature from gitlab
Refer to the How-To link here to know more how to export and import project by gitlab export files
Items exported: https://docs.gitlab.com/ee/user/project/settings/import_export.html
items not exported: https://docs.gitlab.com/ee/user/project/settings/import_export.html