glib/.gitlab-ci/run-docker.sh

#!/bin/bash

set -e

TAG="registry.gitlab.gnome.org/gnome/glib/2-58:v1"

docker build --build-arg HOST_USER_ID="$UID" --tag "${TAG}" \
    --file "Dockerfile" .

if [ "$1" = "--push" ]; then
  docker login registry.gitlab.gnome.org
  docker push $TAG
else
  docker run --rm \
      --volume "$(pwd)/..:/home/user/app" --workdir "/home/user/app" \
      --tty --interactive "${TAG}" bash
fi
ci: Add GitLab CI description file We're mostly interested into building and testing everything that gets pushed to the repository — including merge requests. When pushing tags, though, we should assume we're spinning a release, so let's run the dist target, and store the tarball, and the generated documentation while we're at it, as artifacts on GitLab. The Dockerfile for the image used for the build is included in tree, and published on Docker Hub. Using a custom image allows us to avoid the costly "download and install build dependencies" phase, as well as controlling the environment a little bit better. https://bugzilla.gnome.org/show_bug.cgi?id=793635 2018-02-18 14:59:29 +00:00			`#!/bin/bash`

			`set -e`

ci: Use a docker image for stable branch The master docker image will eventually use a new meson version, but we want to ensure stable branch still works on old version. 2018-09-24 10:05:15 -04:00			`TAG="registry.gitlab.gnome.org/gnome/glib/2-58:v1"`
ci: update meson Rebuild the fedora docker image to get the newest meson release and use pip to install the newest version for MSYS2. https://bugzilla.gnome.org/show_bug.cgi?id=795711 2018-05-01 08:55:29 +02:00
ci: Add "--push" argument to run-docker.sh help script Also there is no need to run docker as root, the user just needs to be in the "docker" group. 2018-06-22 11:24:24 -04:00			`docker build --build-arg HOST_USER_ID="$UID" --tag "${TAG}" \`
ci: Add GitLab CI description file We're mostly interested into building and testing everything that gets pushed to the repository — including merge requests. When pushing tags, though, we should assume we're spinning a release, so let's run the dist target, and store the tarball, and the generated documentation while we're at it, as artifacts on GitLab. The Dockerfile for the image used for the build is included in tree, and published on Docker Hub. Using a custom image allows us to avoid the costly "download and install build dependencies" phase, as well as controlling the environment a little bit better. https://bugzilla.gnome.org/show_bug.cgi?id=793635 2018-02-18 14:59:29 +00:00			`--file "Dockerfile" .`
ci: Add "--push" argument to run-docker.sh help script Also there is no need to run docker as root, the user just needs to be in the "docker" group. 2018-06-22 11:24:24 -04:00
			`if [ "$1" = "--push" ]; then`
			`docker login registry.gitlab.gnome.org`
			`docker push $TAG`
			`else`
			`docker run --rm \`
			`--volume "$(pwd)/..:/home/user/app" --workdir "/home/user/app" \`
			`--tty --interactive "${TAG}" bash`
			`fi`