noosfero | Docker Hub Image Deploy (!1674)

[Arthur Diniz]

New Merge Request !1674

https://gitlab.com/noosfero/noosfero/merge_requests/1674

Project:Branches: lappis-unb/projects/fga/portal/noosfero:docker-hub-deploy to noosfero/noosfero:master
Author:    Arthur Diniz
Assignee:  


Feature to push to docker hub when tag is created and deployed

The final stage before the test and quality is the push with `login into a registry`, `build image` and `push it`.

# Test on our fork

### A new tag was created manually 
![image](/uploads/4e2e8e551d41223545e5bfd4df254486/image.png)

### The pipeline was stated and the image was pushed to our community on [Docker Hub]()
![image](/uploads/42b8fb25a5960157692508f01bc497be/image.png)

### Public view
![image](/uploads/6077e18c4e690b577cdd559d8cc45c3f/image.png)


# Necessary Configuration GitLab

On `/settings/ci_cd` expand `Environment variables` and set it lake above:
![image](/uploads/dd79c854bcfc477edfeddade90460e0c/image.png)

### Variables
`$CI_REGISTRY` is the value found in ```docker info|grep -i registry:```, here being [https://index.docker.io/v1/]().
`CI_REGISTRY` usually you can take on this [link]

`CI_REGISTRY_IMAGE`is the `organisation/repository` on docker hub, in my case i have used `lappis/noosfero`

`CI_REGISTRY_USER` and `CI_REGISTRY_PASSWORD` have to be from one user who has permission to white on the organisation or repository

 Now thats all set just deploy a new tag and wait for your image to be publish on [docker hub]()

-- 
Reply to this email directly or view it on GitLab: https://gitlab.com/noosfero/noosfero/merge_requests/1674
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listas.softwarelivre.org/pipermail/noosfero-dev/attachments/20190213/e82b8d6a/attachment.html>