Scope of this project

[orangemocha]

Is the goal of this project to replace Jenkins for use by the Node.js team itself, or by a broader audience?

I'd like to point out a couple of things:

1. Building something like Jenkins from scratch is a major undertaking
2. Trying to appeal to other projects outside of Node - and trying to include other collaborators - might be the only way to succeed in such an endeavor.

[jasnell]

Specifically by Node.js. If it ends up being more generally useful, awesome, but that should not be one of the primary goals

[Fishrock123]

The focus would be our use case but it should be usable by others with that use-case, if we were to build one.

I don't think we actually would need to re-build Jenkins but rather what we need Jenkins to actually technically do.

[yorkie]

I prefer do think this project also can be an open source reliable solution with modern UX for common Node.js project which wanna set own CI servers.

Actually I'm always sucked by other CI services like CircleCI and TravisCI in my past projects and current one, however I could not find a reliable implementation in Node.js and Jenkins is too complicated.

So assuming there is the user like me after we achieved this project, he would think:

• should as well as use this project in user-land project if Node.js core is using.
• it's written in Node.js, thus I could easily read and patch it.
• having an available machine to host it.

Hence, this is that meaningful for those startups based Node.js stack like mine, this is my thoughts about me and my team, but as @jasnell stated, this is for Node.js itself at first specifically.

[targos]

I think we also need to be able to build and test V8 (and perhaps libuv ?)

[yorkie]

+1 on libuv, but I think v8 seems not to be the thing that we should do for now :-(

[jbergstroem]

@yorkie work is already being done by the build group to achieve this (nodejs/build#199).