In order to make product verification possible, we want to have a test system showing the latest state of our Query Builder.
Acceptance criteria:
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?
@bete I'm not sure what you suggest can be easily incorporated into Toolforge infra, if we had our own VM, it would be a different story and if we use production pipeline, it would have its own pipeline (https://wikitech.wikimedia.org/wiki/Blubber)