This minimal image adds just a TeamCity agent without any tools like VCS clients, etc. It is suitable for simple builds and can serve as a base for your custom images.
This image adds a TeamCity agent suitable for Java and .NET development.
- Ensure Docker installed.
- Clone this repository.
- Apply required changes in the directory configs.
- Generate docker and readme files by running the generate.sh or generate.cmd script. All generated artifacts will be placed into the directory context/generated.
- To check that image build is ok:
- Download the required TeamCity .tar.gz file. For instance
wget -c https://download.jetbrains.com/teamcity/TeamCity-2021.2.tar.gz -O - | tar -xz -C context
- Unpack this file into the directory context/TeamCity within the cloned repository.
- To add plugins to TeamCity agents run the context.sh or context.cmd script. This is optional as otherwise the TeamCity agents will load plugins by themselves on first launch.
- Build docker images using a corresponding .cmd or .sh script file in context/generated directory.
- Check the docker images by running
docker-compose up
in the directories like checks/windows-local or checks/linux-local.
- Download the required TeamCity .tar.gz file. For instance
- Push all repo changes.
- Please refer to the documentation regarding custom TeamCity Agent Images for more information.
To build Docker images that were not provided in docker repositories, you could generate them by yourself
- Ensure Docker installed.
- Clone this repository.
- Download the required TeamCity .tar.gz file. For instance
wget -c https://download.jetbrains.com/teamcity/TeamCity-2021.2.tar.gz -O - | tar -xz -C context
- Unpack this file into the directory context/TeamCity within the cloned repository.
- Generate an image using a corresponding .cmd or .sh script file in context/generated directory.
- TeamCity Docker Images - tools - tools used within the release process of Docker Images.
Please use these channels to give feedback on these images, thanks!
A few handy links to some of the communication channels mentioned:
- Technical question or idea — community forum, "New Post" action (public)
- Bug or feature request — issue tracker (public, with an option of private comments/attachments). Please, make sure to also check our Best Practices When Reporting Issues
- Documentation — Common Problems, Known Issues, Licensing Policy