bete added a comment.
i wanted to bring this issue up over the meeting but i forgot.
why do we have different enviroments in prodcution (docker) and test
(non-docker). doesn't that defeat the purpose of using docker (even if its a
trivial issue)
also, when we were working on the CI tihng, I saw there is no CI for the test
env ? i.e. how about adding a all the deployment in the same deployment config
file and trigger different actions based on the branch.
here is a pseudo code for the config.yml
on master push:
build and run tests
create artifcats (in this case build deocker images and push to our docker
registry)
ssh into prod server and deploy (pull images from docker registry and run
them)
on feature push:
everything else stays the same expcept we do it on the toolforge server
do you think this is over-kill?
TASK DETAIL
https://phabricator.wikimedia.org/T263539
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Ladsgroup, bete
Cc: bete, Aklapper, Jakob_WMDE, Hazizibinmahdi, Akuckartz, darthmon_wmde,
Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, _jensen,
rosalieper, Scott_WUaS, Wikidata-bugs, aude, Mbch331
_______________________________________________
Wikidata-bugs mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
