https://github.com/gtesei/patterns_for_continuous_integration_docker_travis_ci_1

https://github.com/gtesei/patterns_for_continuous_integration_docker_travis_ci_1

containers continuous-integration docker travis-ci

Last synced: 9 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/gtesei/patterns_for_continuous_integration_docker_travis_ci_1
• Owner: gtesei
• Created: 2018-10-05T21:02:13.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2018-10-23T17:20:08.000Z (over 7 years ago)
• Last Synced: 2025-02-28T23:42:52.518Z (over 1 year ago)
• Topics: containers, continuous-integration, docker, travis-ci
• Language: Dockerfile
• Size: 208 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

          
# Patterns for Continuous Integration with Docker using Travis CI 1 

__Full story:__ [Patterns of Continuous Integration for Data Science Python Projects](https://medium.com/@gtesei/the-ci-arsenal-that-any-open-source-machine-learning-python-project-should-consider-e34759dd66c4)

__Full story:__ [Patterns of Continuous Integration for Data Science Python Projects](https://medium.com/@gtesei/the-ci-arsenal-that-any-open-source-machine-learning-python-project-should-consider-e34759dd66c4)

[![Build Status](https://api.travis-ci.org/gtesei/Patterns_for_Continuous_Integration_Docker_Travis_CI_1.svg?branch=master)](https://travis-ci.org/gtesei/Patterns_for_Continuous_Integration_Docker_Travis_CI_1)

![Conceptual Schema](./img/part_1.png)

__GOAL__: for each commit on the _master branch_ we want to build a Docker image according to a given Dockerfile and push it on Docker Hub (or different Docker Registry) using Travis CI.

## Dockerfile 

```docker

FROM debian

RUN apt-get update \

    && apt-get install -y --no-install-recommends cowsay \

    && rm -rf /var/lib/apt/lists/*

ENV PATH "$PATH:/usr/games"

ENTRYPOINT ["cowsay"]

CMD ["Hello, World!"]

```

## .travis.yml  

```yml

sudo: required

services:

- docker

env:

  global:

  - REGISTRY_USER=gtesei

  - secret: ""

  - secure: W8cjk1MzKPXbs+u1PVlP1WPyKOKon0PEeVSf790tV6VtOlExRAK3NPEyFzZ3jjkTsenB/sspBawIJlqjPBQAqeeGz2I7vwWRj1UxawbmHaxaodoclMx3APbg8iW/+qH4bm0M2uyb9F6JWY8azD/j7GKIW8otyIb8s+9qu+wFR9HMuxFuvy8MPABgTk3r6/qflSwWd0QZkia3UqAauFAHCtxTZSwBWz0kL4XBgBEcArVU+1tu6rhOPWsm+CEcxf3WwjCYHdemp5MffC1hWvzgffVWuuFb7Y7ICCCVjaNQ8jgbtJ4HzoFW3vpocRJk7nJiWzTNwXbzqLfreApPEI5ADQqpBczJw23oDG42MiFTurdIXKghzgHo79tDG6ezGRWCkiutcWPu7mgYbWX6og966IboMAOh7aO4zBJY77xkDNYT1YWcrKF3P6Chk7roaGEUJGtZsz/osKzT+XSVdmgOKeQt2fawFlEd7DWAnoDrJwcOWq4NGobR46llQ8YJHHjObS5wzr/ktLvoURDNzTi3RjE4N3nQZvOu57GDcrQ7bkz4if+KNShnkvKg+4DAryB6sSvFaIAtkZmDN1Jf3EgO9eVAKmgGm3AVLzzKsI5NWVIbYqs4Ixp6tFeQ6WF5ad9oeyTVWlov7cDvQclgq0ineO7vgpS5VfqgJQZ6cb92kBg=

before_script:

- docker pull myorg/myimage || true

script:

- docker build --pull --cache-from gtesei/hello_travis --tag gtesei/hello_travis .

- docker run gtesei/hello_travis

after_script:

- docker images

before_deploy:

- docker login -u "$REGISTRY_USER" -p "$REGISTRY_PASS"

deploy:

  provider: script

  script: docker push gtesei/hello_travis

  on:

    branch: master

```

### How to encrypt password of Docker Hub on .travis.yml 

![Howto Encrypt Password](./img/pwd_enc.PNG)

## For each commit on master branch Travis CI builds a new Docker image ...   

![Travis CI](./img/trav_1.PNG)

![Travis CI](./img/trav_2.PNG)

## ... and pushes it on Docker Hub (or different Docker Registry)

![Docker Hub](./img/dock_1.PNG)

## Useful links  

[Ruby Installer for Windows](https://rubyinstaller.org/downloads/)

__To install Travis__ 

```ruby 

gem install travis

```

## Credits 

[Coding Tips: Patterns for Continuous Integration with Docker on Travis CI](https://medium.com/mobileforgood/coding-tips-patterns-for-continuous-integration-with-docker-on-travis-ci-9cedb8348a62)

[Defining encrypted variables in .travis.yml](https://docs.travis-ci.com/user/environment-variables/#defining-encrypted-variables-in-travisyml)

[Google Cloud | Continuous Delivery with Travis CI](https://cloud.google.com/solutions/continuous-delivery-with-travis-ci)

[Continuous Integration. CircleCI vs Travis CI vs Jenkins](https://hackernoon.com/continuous-integration-circleci-vs-travis-ci-vs-jenkins-41a1c2bd95f5)

[Continuous Integration with Jenkins and Docker](https://code-maze.com/ci-jenkins-docker/) 

+/