Geek Answers Handbook

Continuous docker integration workflow

Here is my setup, this conclusion was taken from docker-machine ls. Using a docker to provide a swarm.

NAME             ACTIVE      DRIVER         STATE     URL                          SWARM                     DOCKER    ERRORS
cluster-master   * (swarm)   digitalocean   Running   tcp://REDACTED:2376   cluster-master (master)   v1.11.1   
kv-store         -           digitalocean   Running   tcp://REDACTED:2376                              v1.11.1   
node-1           -           digitalocean   Running   tcp://REDACTED:2376   cluster-master            v1.11.1   
node-2           -           digitalocean   Running   tcp://REDACTED:2376   cluster-master            v1.11.1

Now I’m looking for a way to customize the CI / CD workflow. Here is my initial idea:

  • Create an automatic assembly on the docker hub (bitpack)
  • After the changes are pushed, the trigger will build dockers on the hub
  • Testing will be conducted on the docker hub (test on npm)
  • Create a web host on the docker hub when the build is successful.
  • Webhook will point to my own application, which will then make changes to the swarm.

Questions:

  • Can I run testing on a docker hub, or should I rely on another service?
  • If I rely on another service, what is your recommended service?
  • , . - ?
+4
1

. , , .

-,    ?

, , .

amazon , amazon.

, . - ?

, . multi- node, , , .

, , .

, :

  • .

, . , . . , Amazon ecs

+1

More articles:


All Articles