1
I’m creating some Dockerfile + configuration files for my images, currently I push to Github, later Travis-ci picks up the files and generates a build, ending makes the push to the Docker Hub.
In this approach I have to enter Docker Hub user and password there in the Travis-ci settings, not that this is exactly a problem, however, it is annoying. Some more efficient and practical approach?
What would be the most appropriate flow for this process?
I currently deploy to the Docker Hub via Travis-ci: https://github.com/docker-sources/php-apache-nodejs/blob/master/.travis.yml
In gitlab-ci, I can define some secret variables that will be used in order to be consumed in the yml that manages the build. These variables are grafted as environment variables and are normally used. Since gitlab-ci has come to be the competitor of Travis-ci, I believe there must be an analogous mechanism
– Jefferson Quesado
I just took a quick look, is this feature paid for? In the case of Travis-ci I am not having cost because the project is open source, so the tool ends up charging nothing for its use.
– Fábio Jânio
The intention was to draw a parallel with Travis-ci, not to suggest. But in my understanding it is freely and limitlessly available for open-source public projects. It’s like the gitlab Travis-ci
– Jefferson Quesado