Gitlab account used to run tests against `gitlab.com` has been blocked

[yiannistri]

This is causing all tests that target gitlab.com to fail.

Test logs

=== RUN   TestCreatePullRequestInGitLab
    git_test.go:189: 
        	Error Trace:	git_test.go:189
        	Error:      	Received unexpected error:
        	            	GET https://gitlab.com/api/v4/projects: 403 {message: 403 Forbidden - Your account has been blocked.}
        	Test:       	TestCreatePullRequestInGitLab
    git_test.go:199: 
        	Error Trace:	git_test.go:199
        	Error:      	Received unexpected error:
        	            	POST https://gitlab.com/api/v4/projects: 403 {message: 403 Forbidden - Your account has been blocked.}
        	Test:       	TestCreatePullRequestInGitLab

In hindsight, it's probably a bad idea to hammer their servers as part of every test that needs a Git repo. A limited suite of smoke tests would be preferable to avoid such issues in the future.

[morancj]

Can we use https://gitlab.git.dev.weave.works instead?

[jpellizzari]

@mnowster @JamWils One solution that has been floated is standing up a GitLab instance of our own to test against. Are we ok to pursue that solution? cc @josecordaz

[josecordaz]

@foot @yiannistri @jpellizzari @mnowster I was able to fix the gitlab tests using the on-prem instance gitlab.git.dev.wkp.weave.works that is being used in other tests. Not sure if this would be of any help. On the other hand I'm facing a different issue now, that I'm not sure how to track down. As there is not information on where this is happening. This is what I see https://github.com/weaveworks/weave-gitops-enterprise/runs/5428418953?check_suite_focus=true#step:24:1032. My PR is here #531