gitlab-org--gitlab-foss/doc/README.md
Yorick Peterse 4dfe26cd8b
Rewrite the GitHub importer from scratch
Prior to this MR there were two GitHub related importers:

* Github::Import: the main importer used for GitHub projects
* Gitlab::GithubImport: importer that's somewhat confusingly used for
  importing Gitea projects (apparently they have a compatible API)

This MR renames the Gitea importer to Gitlab::LegacyGithubImport and
introduces a new GitHub importer in the Gitlab::GithubImport namespace.
This new GitHub importer uses Sidekiq for importing multiple resources
in parallel, though it also has the ability to import data sequentially
should this be necessary.

The new code is spread across the following directories:

* lib/gitlab/github_import: this directory contains most of the importer
  code such as the classes used for importing resources.
* app/workers/gitlab/github_import: this directory contains the Sidekiq
  workers, most of which simply use the code from the directory above.
* app/workers/concerns/gitlab/github_import: this directory provides a
  few modules that are included in every GitHub importer worker.

== Stages

The import work is divided into separate stages, with each stage
importing a specific set of data. Stages will schedule the work that
needs to be performed, followed by scheduling a job for the
"AdvanceStageWorker" worker. This worker will periodically check if all
work is completed and schedule the next stage if this is the case. If
work is not yet completed this worker will reschedule itself.

Using this approach we don't have to block threads by calling `sleep()`,
as doing so for large projects could block the thread from doing any
work for many hours.

== Retrying Work

Workers will reschedule themselves whenever necessary. For example,
hitting the GitHub API's rate limit will result in jobs rescheduling
themselves. These jobs are not processed until the rate limit has been
reset.

== User Lookups

Part of the importing process involves looking up user details in the
GitHub API so we can map them to GitLab users. The old importer used
an in-memory cache, but this obviously doesn't work when the work is
spread across different threads.

The new importer uses a Redis cache and makes sure we only perform
API/database calls if absolutely necessary.  Frequently used keys are
refreshed, and lookup misses are also cached; removing the need for
performing API/database calls if we know we don't have the data we're
looking for.

== Performance & Models

The new importer in various places uses raw INSERT statements (as
generated by `Gitlab::Database.bulk_insert`) instead of using Rails
models. This allows us to bypass any validations and callbacks,
drastically reducing the number of SQL queries and Gitaly RPC calls
necessary to import projects.

To ensure the code produces valid data the corresponding tests check if
the produced rows are valid according to the model validation rules.
2017-11-07 23:24:59 +01:00

14 KiB

toc comments
false false

GitLab Documentation

Welcome to GitLab, a Git-based fully featured platform for software development!

GitLab offers the most scalable Git-based fully integrated platform for software development, with flexible products and subscription plans:

  • GitLab Community Edition (CE) is an opensource product, self-hosted, free to use. Every feature available in GitLab CE is also available on GitLab Enterprise Edition (Starter and Premium) and GitLab.com.
  • GitLab Enterprise Edition (EE) is an opencore product, self-hosted, fully featured solution of GitLab, available under distinct subscriptions: GitLab Enterprise Edition Starter (EES) and GitLab Enterprise Edition Premium (EEP).
  • GitLab.com: SaaS GitLab solution, with free and paid subscriptions. GitLab.com is hosted by GitLab, Inc., and administrated by GitLab (users don't have access to admin settings).

GitLab EE contains all features available in GitLab CE, plus premium features available in each version: Enterprise Edition Starter (EES) and Enterprise Edition Premium (EEP). Everything available in EES is also available in EEP.


Shortcuts to GitLab's most visited docs:

GitLab CI/CD Other
Quick start guide API
Configuring .gitlab-ci.yml SSH authentication
Using Docker images GitLab Pages

Getting started with GitLab

User account

  • User account: Manage your account
    • Authentication: Account security with two-factor authentication, setup your ssh keys and deploy keys for secure access to your projects.
    • Profile settings: Manage your profile settings, two factor authentication and more.
  • User permissions: Learn what each role in a project (external/guest/reporter/developer/master/owner) can do.

Projects and groups

Repository

Manage your repositories from the UI (user interface):

Issues and Merge Requests (MRs)

Git and GitLab

  • Git: Getting started with Git, branching strategies, Git LFS, advanced use.
  • Git cheatsheet: Download a PDF describing the most used Git operations.
  • GitLab Flow: explore the best of Git with the GitLab Flow strategy.

Migrate and import your projects from other platforms

Continuous Integration, Delivery, and Deployment

  • GitLab CI: Explore the features and capabilities of Continuous Integration, Continuous Delivery, and Continuous Deployment with GitLab.
    • Auto Deploy: Configure GitLab CI for the deployment of your application.
    • Review Apps: Preview changes to your app right from a merge request.
  • GitLab Cycle Analytics: Cycle Analytics measures the time it takes to go from an idea to production for each project you have.
  • GitLab Container Registry: Learn how to use GitLab's built-in Container Registry.

Automation

  • API: Automate GitLab via a simple and powerful API.
  • GitLab Webhooks: Let GitLab notify you when new code has been pushed to your project.

Integrations

  • Project Services: Integrate a project with external services, such as CI and chat.
  • GitLab Integration: Integrate with multiple third-party services with GitLab to allow external issue trackers and external authentication.
  • Trello Power-Up: Integrate with GitLab's Trello Power-Up

Administrator documentation

Learn how to administer your GitLab instance. Regular users don't have access to GitLab administration tools and settings.

Install, update, upgrade, migrate

  • Install: Requirements, directory structures and installation from source.
  • Mattermost: Integrate Mattermost with your GitLab installation.
  • Migrate GitLab CI to CE/EE: If you have an old GitLab installation (older than 8.0), follow this guide to migrate your existing GitLab CI data to GitLab CE/EE.
  • Restart GitLab: Learn how to restart GitLab and its components.
  • Update: Update guides to upgrade your installation.

User permissions

Features

Integrations

  • Integrations: How to integrate with systems such as JIRA, Redmine, Twitter.
  • Mattermost: Set up GitLab with Mattermost.

Monitoring

Performance

Customization

Admin tools

  • Gitaly: Configuring Gitaly, GitLab's Git repository storage service
  • Raketasks: Backups, maintenance, automatic webhook setup and the importing of projects.
  • Reply by email: Allow users to comment on issues and merge requests by replying to notification emails.
  • Repository checks: Periodic Git repository checks.
  • Repository storage paths: Manage the paths used to store repositories.
  • Security: Learn what you can do to further secure your GitLab instance.
  • System hooks: Notifications when users, projects and keys are changed.

Troubleshooting

Contributor documentation