Version Control on your Server. Visit https://gitlab.com/gitlab-org/gitlab-ce for more information
Hi guys! I posted a question in SO without no clear response on what's wrong with the postgres service in gitlab-runner: https://stackoverflow.com/questions/58952919/postgresql-background-worker-logical-replication-launcher-exited-with-exit-co
The service somehow timeouts and postgres restarts, but I cannot connect into the DB afterwards. I haven't changed my giltab-ci.yml
in a while so it may have been due to a recent update. Using versions 12.5 now in both Gitlab & gitlab-runner. Didn't want to create noise with a new issue so I hope this is the right place to ask
RELEASE
file is which is referenced from the Dockerfile
for gitlab-ce? (see here: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/docker/Dockerfile) ... I also looked at a few other branches and the file is nowhere to be found (at least I came up empty-handed). Unfortunately the documentation also makes no mention of it. The reason I am trying this is because I wanted to build my own image using buildah with slight modifications.
assets/setup
appears to make use of this file by sourcing it as shell script snippet, but I'm not sure what it's supposed to contain. My guess (from looking at this setup
script) is that it's supposed to contain DOWNLOAD_URL
and TRIGGER_PRIVATE_TOKEN
but that still doesn't give me any clues what the content of these variables is supposed to be ...
Never mind, I found the answer I was looking for. I used podman pull
to pull gitlab/gitlab-ce:latest
and then looked at RELEASE
:
# cat RELEASE
RELEASE_PACKAGE=gitlab-ce
RELEASE_VERSION=12.5.2-ce.0
DOWNLOAD_URL=https://downloads-packages.s3.amazonaws.com/ubuntu-xenial/gitlab-ce_12.5.2-ce.0_amd64.deb
oddly enough that's a hardcoded URL right there. I had worked under the assumption that this uses the same approach as is formalized inside https://packages.gitlab.com/install/repositories/gitlab/gitlab-ee/script.deb.sh ... (which one is supposed to use when setting up Gitlab, including CE, on Ubuntu ...)
Hi all.
I have a repository on a self-hosted gitlab instance. It mirrors a public github repository.
Now, I would like to run a custom pipeline automatically whenever a tag is pulled from the mirrored ("upstream") repository.
Of course, the tags from upstream wouldn't include any .gitlab-ci.yml
that I create. Is it possible to run a pipeline based on a .gitlab-ci.yml
from a different source than the tag that is pulled?