Gradle Plugin for projects that use docker. It add Tasks to handle multiple containers with one task. It will be used to start depending containers transitive.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


Gradle Plugin for projects that use docker. It adds Tasks to handle multiple containers with one task. It will be used for ecosystem to start depending containers transitive.

##Default tasks from devbliss We have to separate groups of docker tasks. The first group handles only the project container itself and the second one is for multiple containers.

###Project docker service tasks Task to pull the docker image of the current service from the devbliss registry.

./gradlew pullDockerImage

Task to push the local docker image to the devbliss registry.

./gradlew pushDockerImage

Stop the running service container of the current service. The name of the running container will be the project name.

./gradlew stopDockerContainer

Start a non-running service container. The service container will be the project service. If no container with this name exists it will fail.

./gradlew startDockerContainer

Run a service container. The container name will be the project name and the start command will default that is defined in the Dockerfile.

./gradlew runDockerContainer

Remove the project service container. Will fail if the container is still running.

./gradlew removeDockerContainer

Builds the current project as a docker image and push it to the devbliss registry.

./gradlew buildAndPushDockerImage

###Docker tasks for multiple containers

Starts all containers the service depends on. The depending services are defined over the devblissDocker extension which is explained later.

./gradlew startDependencies

Stops all running docker containers.

./gradlew stopAllRunningContainers

##Configuration In most cases the names are self explaining and for more information the docker api itself can be used. For example what an image name or a version tag is and how they are handled in docker.

###dockerHost Address or socketfile where the docker daemon is running. All containers are running on this machine. All actions are executed there.

###authConfigPlain Contains the information for docker to find the registry where the images are retrieved from. Can contain the authentication information if necessary.

###imageName Name of the docker image. At the ecosystem we use the name of the service to identify images.

###versionTag Version of the docker image.

###registryName Name of the registry where the docker images are saved.

###repositoryName Name of the docker repository. For ecosystem images it's always ecosystem. All depending containers are automatically set with this repository name.

###buildContextDirectory Directory of the Dockerfile or the Dockerfile itself.

###dependingContainers Service containers the project depends on. They will be started with startDependenciesand can contain additional information.

The normal pattern to set them is {name}#{port},{name2}#{port2} Name is the name of the image and container at the same time. The port will be mapped 1:1. The services are seperated by commas.

For additional configuration it's possible to set custom names or portmappings with {name}_{customName}#{portFrom}-{portTo}

nameis the name of the service image. customName is name of the container. portFrom is the accessible port from outside. portTo is the port in the container the portFrom is redirected to.

###Example configuration




devblissDocker {
  dockerHost = dockerDaemonHost
  authConfigPlain = ["serveraddress": "http://${dockerRegistry}/v1"]
  buildContextDirectory = file('./')
  registryName = dockerRegistry
  repositoryName = dockerRepository
  dependingContainers = dependingEcosystemServices
  imageName = dockerImage
  versionTag = dockerTag

##Additional docs In the doc folder there is additional documentation.