Absolutely feasible! You can easily set up an automatic sync from gitrepo1 to gitrepo2 whenever gitrepo1 gets updated—this will trigger gitrepo2's existing Drone CI pipeline exactly as you want. Let's walk through two reliable approaches:

方法1：用Webhook触发服务器端同步脚本 #

This works if you have a server (or a small cloud function) to host a simple sync script:

• First, generate an SSH key pair. Add the public key as a deploy key with write access to gitrepo2 (in GitLab's project settings > Repository > Deploy Keys). Store the private key securely on your server.
• Create a bash script to mirror the repo (save it as sync-repos.sh):

#!/bin/bash
# Clean up any previous temp files
rm -rf temp-mirror
# Clone gitrepo1 as a mirror (captures all branches/tags)
git clone --mirror git@gitlab-server1:your-username/gitrepo1.git temp-mirror
cd temp-mirror
# Push the mirrored content to gitrepo2
git push --mirror git@gitlab-server2:your-username/gitrepo2.git
cd ..
rm -rf temp-mirror

• Make the script executable with chmod +x sync-repos.sh.
• Set up a simple web endpoint (e.g., using Flask or Node.js) on your server that runs this script when it receives a POST request.
• In gitrepo1's GitLab settings > Webhooks, add your server's endpoint URL. Check "Push events" as the trigger, and save. Now every push to gitrepo1 will fire the webhook, run the sync, and trigger gitrepo2's CI.

方法2：用GitLab CI/CD直接在gitrepo1执行同步（最省心） #

Even if gitrepo1 didn't have CI before, GitLab's built-in CI/CD is perfect for this quick sync job:

• Create a .gitlab-ci.yml file in gitrepo1's root directory:

sync-to-gitrepo2:
  stage: deploy
  only:
    - main  # Adjust this to your primary branch (e.g., master)
  script:
    # Install dependencies
    - apt-get update && apt-get install -y git openssh-client
    # Set up SSH for git access
    - eval $(ssh-agent -s)
    - echo "$SSH_PRIVATE_KEY" | tr -d '\r' | ssh-add -
    - mkdir -p ~/.ssh
    - chmod 700 ~/.ssh
    # Configure SSH to trust gitrepo2's server
    - echo "Host gitlab-server2" >> ~/.ssh/config
    - echo "  HostName your-gitlab-server2-url.com" >> ~/.ssh/config
    - echo "  User git" >> ~/.ssh/config
    - echo "  IdentityFile ~/.ssh/id_rsa" >> ~/.ssh/config
    - chmod 600 ~/.ssh/config
    # Mirror and push the repo
    - git clone --mirror $CI_REPOSITORY_URL temp-mirror
    - cd temp-mirror
    - git push --mirror git@gitlab-server2:your-username/gitrepo2.git

• In gitrepo1's GitLab settings > CI/CD > Variables, add a variable named SSH_PRIVATE_KEY with the private key you generated earlier (the one paired with gitrepo2's deploy key). Make sure to mark it as "Protected" if needed.
• Now every push to gitrepo1's main branch will trigger GitLab CI to run the sync job, pushing changes to gitrepo2 and kicking off its Drone pipeline.

关键注意事项 #

• Ensure gitrepo2's deploy key has write permissions—without this, the sync will fail.
• If you don't want to sync all branches/tags, replace --mirror with cloning a specific branch and pushing it to gitrepo2's corresponding branch (e.g., git clone -b main git@gitlab-server1:your-username/gitrepo1.git temp-repo then git push git@gitlab-server2:your-username/gitrepo2.git main).
• Double-check that Drone.io is configured to listen for push events on gitrepo2's target branches—this should already be set up if it triggers on updates, but it's worth verifying.

内容的提问来源于stack exchange，提问作者kosta