In T192006 we (WMDE) want to move the wdqs UI to using blubber and the build pipeline (even if we don't use the resulting image for WMF production deployment).
In order to use blubber and the pipeline we need an nginx base image to serve the content of the wdqs.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | thcipriani | T216039 jenkins / zuul backing up due to jenkins slaves down | |||
| Open | None | T216244 Don't hardcode castor url in castor docker container | |||
| Open | Lucas_Werkmeister_WMDE | T210286 Create docker based CI job to build the wikidata-query-gui | |||
| Declined | None | T192006 wdqs-frontend docker image should (BLUBBER) rebuild automatically when a new patch is pushed to master | |||
| Declined | None | T209292 Create a wmf production ready nginx image |
Event Timeline
Comment Actions
I wonder if there is a way to get some rough timeline for this from SRE or Release-Engineering-Team ?
Or outline of the process that needs to happen to get this done.
The parent task has already been blocked for 1 month and I would hate for this ticket to get forgotten about.
Comment Actions
I don't think anyone from releng is looking into it.
The base images are build with docker-pkg (just like the CI one) using the recipes in operations/docker-images/production-images.git. I guess we can get a nginx image there?
Comment Actions
I would be in favor of not using nginx and turning WDQS gui to a proper nodejs application so we can have real deployment pipeline (right now you need to build the deployment assets and other things) it sorta defies the point of having containers here.
Comment Actions
I also kind of agree with this, especially if we want to go in this direction T209392
Comment Actions
This was for serviceops!
But I decline the task based on @Ladsgroup comment which it would be better to have the application to use NodeJS / service-runner like most of the other MediaWiki services.