mirror of
https://ops.gitlab.net/gitlab-org/gitlab-build-images.git
synced 2025-12-09 10:02:56 +01:00
d87b0be061
Gitaly is using PgBouncer in its CI pipelines to verify that Praefect works alright with this proxy for Postgres. While it was initially using the PgBouncer binary directly, the project has since migrate to set up PgBouncer as a service via a separate image in 0e5953177 (ci: Tie in PgBouncer as a service, 2021-12-03). Since then the PgBouncer executable is not needed anymore in the image used by Gitaly. Stop installing PgBouncer and remove the architecture we have to build and install it.
66 lines
2 KiB
Bash
66 lines
2 KiB
Bash
# Note: Check out https://wiki.bash-hackers.org/syntax/pe for documentation on
|
|
# various variable operations used in this script.
|
|
|
|
PATH_TOOLS=(OS RUBY GOLANG NODE POSTGRESQL)
|
|
TAG_TOOLS=(BUNDLER RUBYGEMS GIT LFS CHROME YARN GRAPHICSMAGICK BAZELISK DOCKER BUILDX GCLOUD KUBECTL HELM)
|
|
|
|
# Generate the docker image path using the components that were specified via
|
|
# variables.
|
|
# For example, consider a CI job which specifies the following variables:
|
|
# OS: debian:bullseye
|
|
# RUBY: 2.7
|
|
# GOLANG: 1.16
|
|
# GIT: 2.33
|
|
# POSTGRESQL: 11
|
|
# With the above variables, this function will return
|
|
# `debian-bullseye-ruby-2.7-golang-1.16-postgresql-11`
|
|
function get_image_path() {
|
|
local path
|
|
path=""
|
|
for tool in "${PATH_TOOLS[@]}"; do
|
|
if [[ -n "${!tool}" ]]; then
|
|
if [[ "${tool}" == "OS" ]]; then
|
|
# The OS variable's value is following <distro>:<version>
|
|
# format. We split that string into individual components.
|
|
distro=${!tool%:*}
|
|
version=${!tool#*:}
|
|
path="${path}-${distro}-${version}"
|
|
else
|
|
# Convert the tool name into lowercase using `,,` operator
|
|
path="${path}-${tool,,}-${!tool}"
|
|
fi
|
|
fi
|
|
done
|
|
|
|
if [[ -n "$path" ]]; then
|
|
echo "$CI_REGISTRY_IMAGE/${path:1}"
|
|
else
|
|
echo "$CI_REGISTRY_IMAGE"
|
|
fi
|
|
}
|
|
|
|
# Generate the image tag using the components that were specified via variables.
|
|
# For example, consider a CI job which specifies the following variables:
|
|
# OS: debian:bullseye
|
|
# RUBY: 2.7
|
|
# GOLANG: 1.16
|
|
# GIT: 2.33
|
|
# POSTGRESQL: 11
|
|
# For that job, this function will return
|
|
# `git-2.33`
|
|
function get_image_tag() {
|
|
local tag
|
|
tag=""
|
|
for tool in "${TAG_TOOLS[@]}"; do
|
|
if [[ -n "${!tool}" ]]; then
|
|
# Convert the tool name into lowercase using `,,` operator
|
|
tag="${tag}-${tool,,}-${!tool}"
|
|
fi
|
|
done
|
|
|
|
if [[ -n "$tag" ]]; then
|
|
echo "${tag:1}"
|
|
else
|
|
echo "latest"
|
|
fi
|
|
}
|