I have plenty of experience when it comes to deploying web-based applications using GitLab environments. I’m at a new job now where we are testing a suite of binaries and want to deploy these binaries to some servers we have setup for the explicit case of testing a deployment.

I have plenty of experience when it comes to deploying web-based applications using GitLab environments. I’m at a new job now where we are testing a suite of binaries and want to deploy these binaries to some servers we have setup for the explicit case of testing a deployment.

I am quite new in gitlab environment and working on how to reuse code as possible in our pipelines. I was trying to use !reference in the following scenario:

Add a gitlab-ci.yml file with test, build, review, and deploy stages.

Itry to use this tutorial
https://docs.gitlab.com/ee/topics/offline/quick_start_guide.html
There is the domain name
Can I use gitlab the domain localhost for my local instance of gitlub ce?

I upgrade Gitlab CE from 16.9.2 to 17.3.0 via 16.11.8 according to Gitlab CE upgrade path (sudo; Ubuntu 22.04.4 LTS):

I created my GitLab account about a month ago. Create my SSH keys, uploaded them and was using repositories without any problems. Had webhook integrations and deploy keys, no problems too.

I am planning to set up another GitLab instance with the same hostname within the same Kubernetes cluster. There is already a GitLab instance with Helm version 5.10.5 that has been set up, and now I am trying to deploy another GitLab instance with Helm version 7.11.7 in a different namespace within the same cluster. However, I encountered the following error:

I am struggling to determine the version of sidkiq GitLab Omnibus uses within its corresponding installation.
Preferrably, I could derive that information from the source code, to be able to see which version is being used now and in future versions to come.
As always, any help is higly appreciated.

I added some automated commit quality checks to our gitlab CI, which essentially walks through all the commits that are in the merge request one-by-one. I essentially loop through the result of a git rev-list origin/main..