These examples can be much simplified too. "SERVER_URL= - "AWS_DEFAULT_REGION=ap-southeast-1" "/opt/share/.composer:/home/buildagent/.composer:rw" "/var/run/docker.sock:/var/run/docker.sock" TEAMCITY_SERVER_MEM_OPTS: -Xmx1g -XX:ReservedCodeCacheSize=350m # Build images: DOCKER_GROUP_ID=$(getent group docker | cut -d: -f3) USER_ID=$(id -u) docker-compose build It allows to run a docker container in the agent docker container, known as "docker in docker". Git config -global user.name "Teamcity Bot" & \ĭocker-compose makes it much easer to run. RUN gpg -allow-secret-key-import -import /var/tmp/.gpg # Pass OS user's id and export it to use in subcontainers
When running a build, TeamCity will execute each step only if all its preconditions, configured by you, are satisfied in the current run. # Access and signature for github repositories What's New in TeamCity 2020.1 Edit page Last modified: 27 April 2023 Conditional build steps Now, you get granular control over build steps with the new execution conditions. Rsync openssh-client vim python python-dev \ RUN apt-get -y -no-install-recommends install \ RUN echo "deb $(lsb_release -cs) stable" > /etc/apt//docker.list
# Custom DockerfileįROM jetbrains/teamcity-minimal-agent:2019.2Īpt-get -y -no-install-recommends install \ In addition, it runs steps to sync an OS user id and buildagent user id, used to run an agent. Dockerized Teamcity agents, most probably, would require to extend basic image and use appropriate package manages.įor instance, we use teamcity-minimal-agent image, based on Ubuntu OS.īelow is an example of extended Dockerfile that contains installation instructions of some basic tools and extra packages our software needs as well as docker client to run "docker in docker".
0 kommentar(er)
