[asterisk-bugs] [JIRA] (ASTERISK-26449) Add dockerfile to repo and official dockerhub repo

[Badalian Vyacheslav (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232601#comment-232601 ] 

Badalian Vyacheslav edited comment on ASTERISK-26449 at 10/9/16 6:29 PM:
-------------------------------------------------------------------------

The problem is that DockerHub Triger works only with changes GitHub repository (and the repository should contain Dockerfile for assembly) or from another DockerHub repository.

Therefore, the possibility of only one. I made Dockerfile in your repository (prepare a patch), and you add DockerHub repository based on your mirror at GitHub. Then when you add changes to the GitHub will automatically be rebuilt image DockerHub and others can use this information in their DockerHub repositories, including as a Triger to rebuild a new version.

My repository ( https://hub.docker.com/r/slavon/docker-asterisk-testsute-asan/ )does the following:
1. Asterisk is compiled with the use of Asan.
2. Run your full TestSute.
3. Check all Address and Leak errors and arranges all the logs on the folder "/ (address | leak) / TEST_ID /"

With the new version, I immediately check it for errors ASAN before implementing it on featuring production systems.

I also use the CentOS;) but Docker lets you quickly in a container to collect the desired configuration of the versions. Virtual machines longer to install.

Also a big plus that Docker "out of the box" is integrated into many CI system.


was (Author: slavon):
The problem is that DockerHub Triger works only with changes GitHub repository (and the repository should contain Dockerfile for assembly) or from another DockerHub repository.

Therefore, the possibility of only one. I made Dockerfile in your repository (prepare a patch), and you add DockerHub repository based on your mirror at GitHub. Then when you add changes to the GitHub will automatically be rebuilt image DockerHub and others can use this information in their DockerHub repositories, including as a Triger to rebuild a new version.

My repository does the following:
1. Asterisk is compiled with the use of Asan.
2. Run your full TestSute.
3. Check all Address and Leak errors and arranges all the logs on the folder "/ (address | leak) / TEST_ID /"

With the new version, I immediately check it for errors ASAN before implementing it on featuring production systems.

I also use the CentOS;) but Docker lets you quickly in a container to collect the desired configuration of the versions. Virtual machines longer to install.

Also a big plus that Docker "out of the box" is integrated into many CI system.

> Add dockerfile to repo and official dockerhub repo
> --------------------------------------------------
>
>                 Key: ASTERISK-26449
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26449
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>            Reporter: Badalian Vyacheslav
>            Assignee: Unassigned
>
> Please add dockerfile to repo and regiser official repo in dockerhub.
> Dockerhub can see pushes in github (https://github.com/asterisk/asterisk) and create autobuilds.
> It's need to track changes and do fresh autobuilds in childrens dockerhub repos!
> PS. Some time ago i was create asan autotest based on TestSute. Now i update versions....
> https://hub.docker.com/r/slavon/docker-asterisk-testsute-asan/



--
This message was sent by Atlassian JIRA
(v6.2#6252)