Docker Continuous Integration using TeamCity

Is there a way that I could do CI using TeamCity and Docker? What I have so far is a Dockerfile that would install TeamCity and configure build agent on a base ubuntu image.

What I want is to have TeamCity call a DockerFile on every commit to SVN or GIT. This DockerFile would actually fetch the latest sources from SVN or GIT and run my integration Tests.

  • Application has different appearance when running through docker
  • Docker Swarm Service Networking
  • Gitlab CI hanging whilst using custom service image
  • Kubernetes Redis HA and exposing redis to things outside of the container
  • Docker: How to deal with restarted nodes?
  • Docker image for windows with oracle12
  • Additionally, how could I manage integration tests against trunk and branch? For example, I have a branch 1.0 and trunk. When I release a branch, I want to run the branch against all the integration tests. Now the integration tests might contain additional tests that actually require a trunk version. How do I handle this? Is there a way using Docker to acheive this?

  • do_compile error on building docker
  • webpack-dev-server hot loading not working with boot2docker
  • Docker for Windows Server 2016 requires update KB3176936
  • Why people create virtualenv in a docker container?
  • Why does Docker need a Union File System
  • Docker: How to use redirect (command >> file.txt) from CMD[]?
  • One Solution collect form web for “Docker Continuous Integration using TeamCity”

    You didn’t mention what build tool you’re using, but there are plugins for Gradle and maven that let you build images, start containers, and so on. They’ll at least give you the tools to build what you want.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.