Can we get hooked up to the node.js CI infrastructure?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3.4k
- Forks
- 531
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
As @bnoordhuis mentioned, it might be possible to get us hooked up to the node.js CI infrastructure.
In general, this could be very nice.
From a personal point of view, my main concerns are with ease of use and speed.
- Will it be at least as fast as Travis, given queues and whatnot?
- Is it possible to hook the CI infrastructure into the GitHub API?
Are CI builds done automatically or manually in node.js?
If they are started manually, the second point above is less important. We could then rely on the current setup for everyday use and do occasional manual checks on a big-endian machine before publishing new versions or merging PRs which might run into endianness problems.
I guess a manual build setup would be easier for the node.js infrastructure team to pull off and would produce less overhead and noise.
/cc @rvagg
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the discussion in issue #507 and reviewing the repository's current Travis setup. Compare the node.js CI infrastructure's automation, queueing, GitHub API integration, and big-endian support with the existing workflow. Done means a decided integration or manual-build plan with agreed operating steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- ci-cd, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100