Issue:
Gitlab CI Multi Runner won't clone a repository correctly so I can't start my build process
gitlab-ci-multi-runner 1.3.2 (0323456)
Using Shell executor...
Running on tests-iMac.local...
Cloning repository for master with git depth set to 5...
Cloning into '/Users/test/builds/b16789d3/0/person/project'...
fatal: Remote branch master not found in upstream origin
ERROR: Build failed: exit status 1
How/Software?
Mac OS X El Capitan as the Runner/Builder (10.11)
gitlab-ci-multi-runner 1.3.2
Omnibus Gitlab CE 8.9.6 on Centos 6 (using external NGINX)
Git Depth set to 5 (can be bigger, but I wanted to make sure the default wasn't too shallow)
So, any thoughts on why this gitlab ci multi runner setup won't pull? I know its communicating between Gitlab and the Runner since we get build errors on Gitlab pipelines and I see the errors on the Mac. I've spent too much time on it and can't figure it out!
Related
I'm using a project on GITLab to store my DAGs and using BitNami's HELM to synchronize Kubernates with the GIT repository. This works perfectly, however I have to inform a branch. It turns out that in production we work with TAGs and I would like the synchronization between Helm and GitLab to be done by the last tag.
Could you help me on this issue?
How should Helm's configuration be done so that it synchronizes with the last existing tag for a branch (master)?
I enable the CI flow between Gitlab to Jenkins.
When I got to Gitlab Portal, only the branchs been created by me are listed there. But when I run the CI flow, from Jenkins console output, it will list extra hundreds branchs with name origin/merge-requests/xxx, xxx is the number from 1 to 156 in my case.
Any idea why and how can I delete these branches?
It is because Jenkins never clean local Git repo which carry a lot of stale remote branch info. These branches already been auto deleted from Git repo.
Inside Jenkins, after install Jenkins Git Plugin, we have two options to help us clean this legacy data:
Source Code Management ==> Additional Behaviors:
Wipe out repository & force clone
Prune stale remote-tracking branches
I have a job in Jenkins that runs on Linux. jenkins is running on a windows master and this job is on linux slave server (Unix slave, version 3.7), I want to use git in linux throw jenkins pipline job so I'm using:
git branch: '${my_branch}', url:......
but seems like it's trying to call git from windows so I'm getting this error:
Cloning repository http://....
C:\Program Files\Git\bin\git.exe init /home/jenkins/workspace/
ERROR: Error cloning remote repo 'origin'
/home/jenkins/workspace/compiler/llvm/atheel_driver_linux/MY_GIT # timeout=10
why its calling c:\ ? (instead of linux folders) Any help? I have run it on a node that tuns in linux:
node ('sdt-srv2-linux') { ... }
Please help
In absence of network, on-site we can commit to local git repo but can't have gitlab-ci to compile project and early trobuleshoot.
How to have a localized gitlab-ci and gitlab-runner which can compile commits offline (*or alternate means) ?
The gitlab runner has an exec command which allows you to run the gitlab runner on your local machine with your local .gitlab-ci.yml configuration file.
This command allows you to run builds locally, trying to replicate the CI
environment as much as possible. It doesn't need to connect to GitLab, instead
it reads the local .gitlab-ci.yml and creates a new build environment in
which all the build steps are executed.
Though if local network troubles are often you may consider installing the gitlab on premises and connect your own local gitlab runner to it so the work is automated.
I created a git project from a public github project and I would like to get github project new versions: is it possible from gitlab? is it possible from command line?
With command lines, go into you project folder. Type git remote -v : you should see a remote repo call origin with the address of you repository in gitlab.
Now you can try git remote add origin_github <url_of_github_project>. And then git pull origin_github master should update your repo from GitHub source to your own GitLab repo.