Docker integration plugin now available for 2017.1.x

Greetings everyone!

As you might already know, TeamCity 2017.2 EAP builds provide new Docker integration features. They are provided by the Docker Support plugin, which is bundled with TeamCity 2017.2 EAP by default.

Today we are making this plugin available to users of TeamCity 2017.1.x as well. If you are already on 2017.1.x and use Docker, we believe the Docker Support plugin will make your life simpler, and here is why:

  • The “Docker Build” runner helps create your own Docker images.
  • The “Docker Compose” runner allows starting services using Docker Compose during your build process. The TeamCity agent will stop these services automatically when the build finishes.
  • The Command Line, Gradle, and Maven runners are also extended with the ability to execute inside a Docker container. Check this blog post for a usage example.
  • Finally, the “Docker Support” build feature provides more convenience features like:
    • automatic login to a Docker registry before the build starts;
    • the “Docker Info” build tab with information about images published to the Docker registry during the build;
    • the option for automatic deletion of the associated images from the registry when the build is deleted during the TeamCity cleanup procedure.

For details, take a look at the integration documentation.

If you wish to try this plugin, there’s nothing to stop you:

Oh, wait, there is one more option. You can actually TestDrive it in the cloud!

Happy building!
The TeamCity Team


This entry was posted in Uncategorized. Bookmark the permalink.

7 Responses to Docker integration plugin now available for 2017.1.x

  1. Zohar Shay says:

    Support for Amazon ECR (Elastic Container Registry) would be great.
    This has mostly to do with support for an alternate repository docker login:

  2. Evgeniy Koshkin says:

    Zohar, I’ve created an issue
    Feel free to watch / comment it.

  3. Morten H Andersen says:

    When using a connection to a Azure Container Registry, the UI show that it can authenticate when testing. But having turned on ‘Log in to the Docker registry before the build’, I still get “authentication failed”. Using ‘docker login’ manually on the agent works fine.

  4. Sergey Pak says:

    Morten, created a ticket to address the issue:

  5. Kunal says:

    Is there a docker publish build step as well,
    basically publish the image to global or private docker registry

Comments are closed.