Confirmed users
478
edits
Gaia/Build/RefactoringToNodejs: Difference between revisions
Jump to navigation
Jump to search
Gaia/Build/RefactoringToNodejs (view source)
Revision as of 07:49, 3 February 2015
, 3 February 2015→In M2, buildbot should pre-install proper command tools (node.js, gulp) if we decide to use gulp.js, right?: fix
| Line 134: | Line 134: | ||
It should continue to work if we keep hosting our gaia-node-modules mirror to solve such situation. Replacing the make-shift gaia-node-modules mirror is not the scope of this work, but we are looking forward to find a way to do that. | It should continue to work if we keep hosting our gaia-node-modules mirror to solve such situation. Replacing the make-shift gaia-node-modules mirror is not the scope of this work, but we are looking forward to find a way to do that. | ||
== In M2, buildbot should pre-install proper command tools (node.js, gulp) if we decide to use gulp | == In M2, buildbot should pre-install proper command tools (node.js, gulp) if we decide to use gulp, right? == | ||
Buildbot has already installed node environment except gulp. | Buildbot has already installed node environment except gulp. For gulp, we can pre-install gulp -g in buildbot, or download gulp while first time build then launch it by relative path. | ||
== Would the new build system slower than we have right now? == | == Would the new build system slower than we have right now? == | ||
Although we believe that M1 & M3 won't effect obviously on performance, it probably happen on M2. So we should ensure that we take full advantage of multi-core systems to speed up our workflow in Node.js environment (with gulp). | Although we believe that M1 & M3 won't effect obviously on performance, it probably happen on M2. So we should ensure that we take full advantage of multi-core systems to speed up our workflow in Node.js environment (with gulp). | ||