Geoshapes will be extracted into a new standalone service. Once the repository is created it will need CI jobs for testing and Code Health checks.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Zuul: [mediawiki/services/geoshapes] Add typescript service CI | integration/config | master | +6 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | ssastry | T263854 [Maps] Modernize Vector Tile Infrastructure | |||
| Resolved | Jgiannelos | T275845 Cleanup deprecated codebase from kartotherian project | |||
| Resolved | MSantos | T274378 Extract geoshapes into a standalone service | |||
| Resolved | MSantos | T274380 Add CI jobs for geoshapes service |
Change 667227 had a related patch set uploaded (by MSantos; owner: MSantos):
[integration/config@master] geoshapes: enable CI for new service
@kostajh I have a dumb question about sonarcloud.io and the code-health pipeline: will it work out of the box once the CI jobs are enabled after https://gerrit.wikimedia.org/r/c/integration/config/+/667227?
Change 667227 merged by jenkins-bot:
[integration/config@master] Zuul: [mediawiki/services/geoshapes] Add typescript service CI
Mentioned in SAL (#wikimedia-releng) [2021-02-26T19:47:13Z] <James_F> Zuul: [mediawiki/services/geoshapes] Add typescript service CI T274380
Once you add the relevant config in .pipeline and sonar-project.properties (e.g. https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/services/push-notifications/+/refs/heads/master/sonar-project.properties) I think the only manual work you might have to do is create a new project in sonarcloud.io with the name of the project, so mediawiki-services-geoshapes. I've gone ahead and created that just now https://sonarcloud.io/project/configuration?id=mediawiki-services-geoshapes