February 15, 2019: The GitLab replacement service went live for all campus users.
February 15 - May 15, 2019: You are asked to migrate your projects from BitBucket to GitLab. If you need assistance with this process, please email us at email@example.com.
May 15, 2019: All users should have migrated their data to GitLab and ceased using BitBucket.
May 31, 2019: BitBucket will be retired, and access will be shut off.
The recommended approach is to use GitLab's import feature that we link to, below. Beyond their documentation, please keep in mind the following considerations before proceeding:
- Please ensure that user access is established and that the destination GitLab groups and subgroups exist, first. It is somewhat more challenging to move things around after they have been imported.
- Other import methods. There are other ways to import a repository, but the feature, below, imports more than just the git-specific information like tags, branches, etc.
- For a large number of repositories, it is best to import one repository at a time to avoid time-out errors. It may even be a good opportunity to do some clean-up, normalization, or archiving.
- Be sure to select the appropriate group when importing a repository. You can move a repository after import, but it takes more work. Contact firstname.lastname@example.org if you need assistance.
- Paging issues. Paging with the import tool is buggy. You'll need to locate a repository by editing the URL with your best guess at where it is, and converging via binary search.
- After you have migrated your project from BitBucket, delete the project from BitBucket to signify to the service team that migration is complete.
Warning: Before deleting a repository from BitBucket, be sure you no longer need anything from the BitBucket project as recovery will not be possible.
If you are ready, please proceed to use GitLab's import feature.
I already have a deploy key
If you have a deploy key from Stash/BitBucket, you will need to convert it to OpenSSH format. The easiest way is to use an online converter such as UC Berkley's Converter. Be sure to paste only the public key, not the private one.
Alternatively, you can use PuttyGen to import and convert a key.
I need to create a deploy key
Please follow the GitLab instructions for creating an OpenSSH-formatted deploy key.
Yes, you can use an LDAP filter to specify your users. Warning: Please try this on a subgroup before applying it to a top-level group so you don't accidentally remove your own access! When you switch to LDAP membership management, existing members will be removed.
Yes, but note that ITS does not provide centralized support for CI/CD. You would need to set up your own runners per GitLab's documentation.
Unfortunately our license doesn't permit us access to this feature.
GitLab Academic is for research and education use, and GitLab Administrative is for UI Professional IT staff.