- CI should automatically run the npm tests in the trending-edits source repo and vote based on the results.
- After code review +2 and verification succeeded, a patch should be merged.
The setup can be similar to the mobileapps repo.
The setup can be similar to the mobileapps repo.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T140102 [EPIC] As a user, I want to see see a list of currently trending articles | |||
| Resolved | pmiazga | T145662 Setup: Create trending-edits git repo | |||
| Resolved | • mobrovac | T149601 Add CI to trending-edits repo |
Change 320366 had a related patch set uploaded (by Jdlrobson):
Add CI to trending-edits repo
did a recheck on the last merged change https://gerrit.wikimedia.org/r/#/c/318507/3 but the npm test command fails with:
Error: ENOENT: no such file or directory, open '/home/jenkins/workspace/npm-node-4/test/utils/../../config.yaml'
@bearND @mobrovac Jenkins is currently complaining with:
fs.js:549 12:00:02 return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode); 12:00:02 ^ 12:00:02 12:00:02 Error: ENOENT: no such file or directory, open '/home/jenkins/workspace/npm-node-4/test/utils/../../config.yaml' 12:00:02 at Error (native) 12:00:02 at Object.fs.openSync (fs.js:549:18)
I don't get this error locally...
The file is there so I can only assume that there's something wrong with the CI setup @hashar
(note it doesn't seem to appear in https://phabricator.wikimedia.org/diffusion/query/all/)
The root of the repository has:
config.dev.yaml config.prod.yaml
I have no idea how that is handled by other service though :(
ah... i see what's happening here. I have one but .gitignore is hiding it.
@mobrovac what's the correct action here? Should one be added or does it need to be setup elsewhere?
This is indeed strange, the CI job should create that file. I will take a look at it when I get a small window of time.
Change 320766 had a related patch set uploaded (by Mobrovac):
Add config.yaml as symlink to config.dev.yaml