Hello all,
we are planning to migrate the Eclipse SW360 project to the new European based Gitlab instance of the Eclipse Foundation.
Main reasons for the move are:
- A project in Gitlab allows to have multiple repositories, this allows us to structure the codebase better and to get rid of the separation of the Eclipse project
and the stuff managed in the sw360 organization on GitHub.
- The Gitlab instance is European based and therefore we have less risk concerning data protection issues between Europe and the US.
- Gitlab has an integrated CI mechanism which is currently not available in the EF instance but will be the solution on the long run, integrating code hosting and
CI is a promising approach to keep things together and to have a long term solution, e.g., the current issues with Travis are not a risk anymore.
In order to get this managed together with the Eclipse Foundation, I have raised an issue in the EF Bugzilla:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=568687
The current situation is, that not many projects have done the migration, as a consequence we have to make some first-hand experiences on the way. That results in a cautious migration path which ensures minimal disturbance
for the normal project development. As a first step, we have organized for a project area on the Gitlab instance which can be found here:
https://gitlab.eclipse.org/eclipse/sw360
In the Monday weekly meeting we will discuss the next steps. A good candidate I see is the migration of the build onto the EF Jenkins Infrastructure, since we need to get a solution because of the latest business model
changes of Travis.ci. Another step could be the migration of the webpage to Gitlab to have a first experience on how things can be moved onto Gitlab.
More to come after Monday,
Best regards,
Lars