Scope?
Currently, all the customer repositories (the ones having “-logic” as a suffix) are hosted in Bitbucket. We started to use Gitlab recently for a number of good reasons over Bitbucket for all engineering repositories. Bitbucket as a code repository environment hence is sort of deprecated and is likely be closed one day and all the repositories will have to be migrated to GitLab. The new repositories will only be created in GitLab.
What’s the process?
In the first phase we migrate active projects that do not use a Jenkins job.
| Drawio | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
When to migrate?
ASAP, the sooner the better. The goal is to close your Bitbucket accounts during June so we don’t pay 2 licenses for each user.
Who will migrate the repository?
GIT admins are responsible for that.
Who is affected?
Configuration Engineers, customers and 3rd parties – everybody who contributes to the Bitbucket repositories. Please make sure that you communicate this to everybody involved.
What is .gitlab-ci.yml?
It is script that describes which CI (= Continuous Integration) jobs should be run. They should be designed in a way that they can merged into any branch.
See https://docs.gitlab.com/ee/ci/yaml/
Next steps:
| Child pages (Children Display) |
|---|