-
Notifications
You must be signed in to change notification settings - Fork 204
Gitlab.com Migration
This document describes expected changes and checkout procedures following the Gitlab.com migration.
The FINOS instance of Legend hosted at legend.finos.org has now been switched to use the public gitlab.com instance instead of the FINOS hosted gitlab.legend.finos.org instance. This provides many benefits including the reducing the infrastructure maintenance overhead of the FINOS Legend instance.
The FINOS projects are organized as follows :
FINOS Project | Modeling Initiative | Gitlab.com Group/Project |
---|---|---|
Financial Objects | CDM | https://gitlab.com/finosfoundation/legend/financial-objects/cdm |
Financial Objects | CML Reference Data Project | https://gitlab.com/finosfoundation/legend/financial-objects/commodrefdata |
Financial Objects | Product Control Common Template | https://gitlab.com/finosfoundation/legend/financial-objects/product-control-common-template |
Security Reference Data | Currency Reference Data | https://gitlab.com/finosfoundation/legend/security-reference-data/currencyrefdata |
Users of the FINOS Legend instance should follow these instructions to verify they are able to continue using the Legend Studio projects.
-
Clear cookies for the legend.finos.org domain. See https://support.google.com/chrome/answer/95647?hl=en&co=GENIE.Platform%3DDesktop#zippy=%2Cdelete-cookies-from-a-site
-
Navigate to legend.finos.org/studio and accept the consent prompt
-
Open the project, create or re-use an existing workspace, make a minor change and sync the workspace
-
Please contact [email protected] in case you run into any errors/issues.
The following changes are expected as part of this migration :
-
When navigating to legend.finos.org/studio, users are presented with a Gitlab consent prompt asking them to authorize Legend to connect to Gitlab.com on their behalf. This is expected and users should provide consent.
-
Issues created in gitlab.legend.finos.org have been re-imported into the gitlab.com project. However, the import feature does not preserve issue labels.
-
Model changes that were merged to the master branch in gitlab.legend.finos.org have been preserved and are available in the gitlab.com project.
-
Model changes that were synced to a workspace in gitlab.legend.finos.org might be visible in the gitlab.com project.
If you have the same user id on gitlab.com and gitlab.legend.finos.org, workspaces created on gitlab.legend.finos.org will be automatically visible in the gitlab.com project.
If you do not have the same user id, they will not be visible. Contact [email protected] for assistance.
- Only the projects listed above have been migrated. Other projects such as personal/scratch projects have not been migrated.
The projects that were previously hosted on gitlab.legend.finos.org have been archived.
This means that they are now in read-only mode and users cannot push commits to them. They are also not visible in the project navigation screens at gitlab.legend.finos.org.
FINOS Project | Modeling Initiative | gitlab.legend.finos.org Group/Project |
---|---|---|
Financial Objects | CDM | https://gitlab.legend.finos.org/legend-pilot/cdm |
Financial Objects | CML Reference Data Project | https://gitlab.legend.finos.org/legend-pilot/commodrefdata |
Financial Objects | Product Control Common Template | https://gitlab.legend.finos.org/financial-objects/product-control-common-template |
Security Reference Data | Currency Reference Data | https://gitlab.legend.finos.org/legend-pilot/currencyrefdata |
- The FINOS insights dashboard does not index gitlab.com as yet. https://insights.lfx.linuxfoundation.org/projects/finos-f/dashboard;subTab=technical
- For Legend Users
- For Legend Maintainers