Merge request failure on git-clone step (Gitlab Private Repo)

Question & Answer Builds
,
1

NOTE: This is the same issue reported here:

  1. Gitlab merge request failure on git-clone step (if PR is sent from a private fork) but it is now closed.
  2. Git-clone fails when PR is sent from private fork (Github)

–

all GITLAB PR trigger fails on git-clone step

Where did the issue happen?

git "init"
Initialized empty Git repository in /bitrise/src/.git/
git "remote" "add" "origin" "git@gitlab.com:xxxxxx/xxxxx-harmonia/xxxxx-plus.git"
git "fetch" "origin" "bitrise"
Warning: Permanently added 'gitlab.com,xxx.xx.xxx.xx' (ECDSA) to the list of known hosts.
From gitlab.com:xxxxxx/xxxxx--harmonia/xxxxx-plus
 * branch            bitrise    -> FETCH_HEAD
 * [new branch]      bitrise    -> origin/bitrise
ERROR: auto merge, error: there is no Pull Request branch and can't download diff file
|                                                                              |
+---+---------------------------------------------------------------+----------+
| x | git-clone@4 (exit code: 1)                                    | 9.55 sec |
+---+---------------------------------------------------------------+----------+
| Issue tracker: https://github.com/bitrise-io/steps-git-clone/issues          |
| Source: https://github.com/bitrise-io/steps-git-clone                        |
+---+---------------------------------------------------------------+----------+

Description of the issue

Sent a Merge Request from a private repo to a private repo (GITLAB)

Environment:

Where did the issue happen?

on Android & Docker, on Ubuntu 16.04

Which build Step causes the issue and which version of the step?

Git Clone v4.0.18

Reproducibility

  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • Does the issue happen sporadically, or every time? : YES
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? : Well everytime I file a merge request

:grinning:

2

is there any alternative solution this issue?

3

I face similar issue here.
but my case is forked repo merge to upstream repo. (self-hosted GitLab)
all repo’s Project visibility are Internal.

4

Sorry to hear about the issues! Can you guys please include build URLs with your report? It would really help if we could access the logs completely. Thanks!

5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.