Go back to the cluster page on GitLab, and go to the Details tab. Add
your Base domain. For this guide, use the domain .nip.io.
Click Save changes.
I think this option only showed up AFTER I installed the ingress.
As you suggested, having a build artifact to save the current commit SHA for the build would be ideal. Subsequent runs of the same workflow can download the artifact using the dawidd6/action-download-artifact action, which allows downloading artifacts generated from another workflow run.
Snippet for uploading artifact:
- name: Upload artifacts
A gitlab runner is a process that f.e. tests, compiles your project, pushes the artefact to you artefact store etc.
A Gitlab runner can be tagged inside Gitlab or via config.toml - so - you can assign runners via tags to Gitlab projects (shared).
Gitlab runner are not designed to run an application 24x7. So - you assign a project to a runner (or a tag or all)...
Answering my own question here. "Multi project pipeline" is not necessary here. You simply have a single project and mark jobs with different "tags". You can then register runners for these different tags, on different machines.
(Artifacts are transferred from one job to the next the same, regardless if the runners are run on the same ...
Yes, you can use the rules syntax. You can use this in combination with regex for commit message, ci_pipeline_source or any other available CI variables.
- do something on schedule only
- if: '"$CI_PIPELINE_SOURCE" == "schedule"'
- runs on Merge request pipeline
It was a simple mistake I made when I register gitlab-runner. I just used gitlab-runner register [options]
But when I register it with sudo, it was working properly.
sudo gitlab-runner register [option]
Runner is running in Ubuntu-18.04 server.
My solution to this problem was two fold.
First: As mentioned in the question, I was able to reduce the amount of concurrent Gitlab Instance runners to one, to avoid the usage of too many resource which was causing the shared runner freeze. To do this i moved all my integration tests into a single job. This didn't increase the time of the tests significantly ...