We would like to have a toolchain that is building, testing and deploying the application.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Add a build task to the Gruntfile | wikidata/query/gui | master | +125 -5 | |
| Introduces QUnit test for rdf hint | wikidata/query/gui | master | +518 -331 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T115995 [Story] Clean setup for WDQS GUI component | |||
| Resolved | None | T118596 [Story] Create CI toolchain for query service GUI | |||
| Resolved | None | T115996 [Task] Use package manager | |||
| Resolved | None | T137623 Automatically build GUI when new commit is merged in master |
Event Timeline
Comment Actions
Change 273780 had a related patch set uploaded (by Jonas Kress (WMDE)):
Add a build task to the Gruntfile
Comment Actions
Change 273522 had a related patch set uploaded (by Jonas Kress (WMDE)):
Introduces QUnit test for rdf hint
Comment Actions
The deploy process right now uses "production" branch from gui repo, which is cherry-picked from master. However, production branch does not have grunt, npm etc files since it is deployed directly to webserver. So we need to find a mechanism that would allow merging changes into production branch without breaking this - or change deployment model to be compatible.
Comment Actions
Change 284709 had a related patch set uploaded (by Jonas Kress (WMDE)):
Grunt build script
Comment Actions
Now we have separate deployment repo - wikidata/query/gui-deploy - so we need some way to make the CI to run the grunt build after merging and put the result into production branch of that repo.