Page MenuHomePhabricator

maps/kartotherian and maps/tilerator repos do not have Jenkins jobs
Closed, DuplicatePublic

Description

None of the git repositories for Maps (Kartotherian) or Maps (Tilerator) have any CI jobs:

maps/tilerator
maps/tilerator/deploy
maps/kartotherian
maps/kartotherian/deploy

Lack of CI is an issue on its own and developers have to manually +2/+2 & submit.

Event Timeline

Added noop job which is always a success with 6b38faa08e662a4a923574666fcf81c827beb69e

Would be nice to align it with how it is done for Graphoid or Mathoid.

hashar triaged this task as Medium priority.Sep 3 2016, 12:22 PM
hashar moved this task from Backlog to Repo setup on the Continuous-Integration-Config board.
hashar renamed this task from maps/kartotherian/deploy does not go via jenkins to maps/kartotherian/deploy and maps/tilerator/deploy do not have Jenkins jobs.Oct 11 2016, 10:27 AM
hashar added a project: Maps (Kartotherian).
hashar updated the task description. (Show Details)
hashar added a project: Maps (Tilerator).
hashar renamed this task from maps/kartotherian/deploy and maps/tilerator/deploy do not have Jenkins jobs to maps/kartotherian and maps/tilerator repos do not have Jenkins jobs.Oct 11 2016, 10:31 AM
hashar updated the task description. (Show Details)

Change 315230 had a related patch set uploaded (by Hashar):
Experimental jobs for Tilerator and Kartotherian

https://gerrit.wikimedia.org/r/315230

Change 315230 merged by jenkins-bot:
Experimental jobs for Tilerator and Kartotherian

https://gerrit.wikimedia.org/r/315230

On each of the four repos, you will be able to comment in Gerrit 'check experimental' which will trigger the job. The all fails due to the test suite referencing test/utils/../../config.yaml which does not exist.

For Tilerator:

> mocha

fs.js:549
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open '/home/hashar/tilerator/test/utils/../../config.yaml'

Would need to find a way for the testsuite to detects it is running under Jenkins (I recommend checking whether the environment variable JENKINS_URL is set) and craft a config file suitable for CI.

Will be addressed by migrating it to kubernetes / pipeline, just like other services. T198901