i noticed the same issue when trying to push from another repository with --mirror ā¦
Maybe a new version of gitlab has been deployed and we need to configure something ?
can anyone help us to re-activate this functionality ?
Iāve same issue. Problem started at 07-Sep-2017 15:00:00 (UTC+3). One of my repositories wasnāt mirrored. Script logs:
07-Sep-2017 15:01:39 Cloning into bare repository ārepo.gitāā¦
07-Sep-2017 15:02:21 remote: GitLab: API is not accessible
07-Sep-2017 15:02:21 To git@gitlab.com:org/repo.git
07-Sep-2017 15:02:21 ! [remote rejected] master ā master (pre-receive hook declined)
07-Sep-2017 15:02:21 ! [remote rejected] refs/pull/2322/head ā refs/pull/2322/head (pre-receive hook declined)
07-Sep-2017 15:02:21 ! [remote rejected] refs/pull/2322/merge ā refs/pull/2322/merge (pre-receive hook declined)
07-Sep-2017 15:02:21 ! [remote rejected] refs/pull/2324/merge (pre-receive hook declined)
07-Sep-2017 15:02:21 ! [remote rejected] refs/pull/2326/merge ā refs/pull/2326/merge (pre-receive hook declined)
07-Sep-2017 15:02:21 error: failed to push some refs to āgit@gitlab.com:org/repo.gitā
Next script starts fails if Iāve any changes in my repository. Same time my script also registered deploy message:
07-Sep-2017 15:31:10 remote: ========================================================================
07-Sep-2017 15:31:10 remote:
07-Sep-2017 15:31:10 remote: We are currently deploying GitLab EE 9.5.4
07-Sep-2017 15:31:10 remote:
07-Sep-2017 15:31:10 remote: ========================================================================
I can push any my branch, push each of my brances one-by-one, create new branches and delete any branches, but I canāt use --mirror flag. Also I canāt use command git push git@gitlab.com:org/repo.git '*:*' - itās fails too.
I also have the same problem with git push --mirror. I get the following message:
remote: GitLab: API is not accessible
To https://larkbuildmachine:xxx@gitlab.com/LarkTechnologies/goldfinch.git
! [remote rejected] master -> master (pre-receive hook declined)
...
error: failed to push some refs to 'https://larkbuildmachine:xxx@gitlab.com/LarkTechnologies/goldfinch.git'
This was working for me for months but is broken since a week ago or so. I have checked my project and there are no protected branches set up. I donāt know how I can further help debug this.
I think it may have something to do with rebasing. The push does work for other repos I have that are less complicated, and the error messages I see could possibly be only for branches that were rebased and then force pushed.
Iām having the same trouble. Seems to have started recently (within the past week or so?) for me too. Seems to be happening for my more ācomplicatedā repoās too. However, Iām not sure where to begin to look for more useful information.
In case itās useful in establishing a pattern, the only things ācomplicatedā I can think of with my two repos (out of about 15-20) that are failing with āgit push --mirrorā is that both have had some rebasing of branches and cherry-picking of commits.
Not sure if it is a coincident ā¦ but it works now.
Iāve just lāve just connect the social-sign int by going to:
User Settings>Account>Social-Sign in>Connect to GitHub as the upstream repository is hosted in GitHub!
Iāve tried disconnecting again the GitHub service, but it is still working fine and was able to push to Gitlab (origin repository) using the git push --mirror command without any error message. (i.e. remote: GitLab: API is not accessible).
Please try at your end to confirm.
Note: This has been tested on the GitLab hosted/cloud account, not enterprise server.