Pull mirroring

To configure repository mirroring, on the project page, go to “Settings” → “Repository” → “Mirroring repositories”.

If the repository is empty, import it first. All hooks are triggered during mirroring, and pulling a large repository may significantly impact system performance.

Configuring pull mirroring of a repository

To configure pull mirroring of a repository, follow these steps:

1. Go to the project page:

   • Open your project in the Deckhouse Code interface.
   • In the left-hand menu, select “Settings” → “Repository”.
   • Scroll down to the “Mirroring repositories” section.

2. Specify the repository URL. Credentials in the URL are ignored. Use the fields in the “Authentication method” block below for authorization.

3. Configure authentication:

   • If using HTTP(S) access, in the “Authentication method” field, select “Username and password” and enter:
     • “Username”: Your username.
     • “Password”: Your password or access token.
   • If using SSH mirroring, specify the username (typically git). After saving the configuration, Deckhouse Code will generate an SSH key to be used for access.

Scheduling and error handling

• Pull mirroring tasks are scheduled once per hour (Projects::PullMirrorScheduleWorker).
• Each mirror is updated no more than once every 6 hours.
• If a mirroring task fails, the next attempt will be during the next run of Projects::PullMirrorScheduleWorker. The maximum number of retry attempts is 5. Clicking “Update now” resets the failure counter.
• If a Sidekiq task terminates unexpectedly (for example, due to a Sidekiq restart), its status is updated after 3 hours, and a new synchronization attempt is scheduled.

LFS (Large File Storage) specifics

When using pull mirroring, LFS objects are fetched only if LFS is enabled in the target Deckhouse Code project.