What I used to with Travis was, first build my

Question

What I used to with Travis was, first build my

docker images on the CI server and then push it to docker hub or github private registery

deploy:
provider: script
script: deploy-script.sh
on:
branch: master

The deploy script would basically pull the docker image, create a fresh compose file and then would run

docker stack -c compose.yml project

But creating a fresh compose file is a complicated process, there are no checks for conflicting rules or something like that which can't actually be done in bash script (well technically we can but it would be a mess).
That's the whole reason I was trying to build it, to improve the flow and provide some additional features like automatic ssl certificates generation and renewals, UI for swarm (which portainer does way better than I can do btw), etc. .

Do you guys think it's just hassle for no reason and bash scripts are the way to go?

0

05.05.2020

1 ответов

11 просмотров

Satyakam Goswami · Accepted Answer

Satyakam Goswami

lets take this discussion offline for all the folks who are interested

0

05.05.2020

Похожие чаты

What I used to with Travis was, first build my

1 ответов

Похожие вопросы