Cool! It seems like task-cluster has been running on node 4.2.2 for a while.
I’ve a local WIP patch which is able to run Gaia default build (just “make” without any parameters) and it works well on node 4+. Thus, I think it would be not so hard to move to node-based build system. > On Nov 25, 2015, at 1:32 PM, Eli Perelman <[email protected]> wrote: > > [...] node may depend on different node versions. Thus, CI servers should be > able to switch node versions for each case. > > Hmm, I actually don't think that's the case. Aus can correct me if I'm wrong, > but I believe Gaia's CI runs a particular Docker container which comes > prebundled with Node 4.2. Since it appears that all of our existing tools > outside of build have already moved to Node 4.2, there should be no reason to > switch Node versions inside of the container. As long as the tools track with > LTS, and the Docker container does as well, it should be somewhat simple to > keep everything in working order on that front. If build can also target LTS, > that would be very helpful. > > Eli Perelman > > > On Tue, Nov 24, 2015 at 11:26 PM, Ricky Chien <[email protected] > <mailto:[email protected]>> wrote: > There has been a node refactoring plan [1], and we’ve migrated almost a half > of build scripts to support compatibilities with node platform. > > I didn’t see any significant issues if we run build system on node instead of > xpcshell. Some resolvable issues I know such as finding an alternative > DOMParser for node since l20n scripts doing DOM modifications a lot. I’ve > submitted a patch for jsdom to support template.content [2] so that we are > able to embrace jsdom for our DOMParser on node. Gaia has several > node-executor (raptor, marionettejs, build system...) base on node may depend > on different node versions. Thus, CI servers should be able to switch node > versions for each case. > > [1] https://wiki.mozilla.org/Gaia/Build/RefactoringToNodejs > <https://wiki.mozilla.org/Gaia/Build/RefactoringToNodejs> > [2] > https://github.com/tmpvar/jsdom/commit/86ef3543de49deb21d75e07179baf5a45a56c7c3 > > <https://github.com/tmpvar/jsdom/commit/86ef3543de49deb21d75e07179baf5a45a56c7c3> > > >> On Nov 25, 2015, at 11:45 AM, Fred Lin <[email protected] >> <mailto:[email protected]>> wrote: >> >> I've discussed with Ricky, if CI integration works with Node, we could >> identify issues and move to node-based build system during 2.6 time frame. >> At least make per app build script run with node, so gaia apps could use >> tools you want. >> >> More concrete plan could be discussed during Orlando. >> >> >> regards >> -- >> Fred >> >> On Tue, Nov 24, 2015 at 11:02 PM, Michael Henretty <[email protected] >> <mailto:[email protected]>> wrote: >> >> On Mon, Nov 23, 2015 at 4:27 PM, Fred Lin <[email protected] >> <mailto:[email protected]>> wrote: >> 3. is it a significant effort to switch from xpcshell to node? >> >> From the discussion so far, it sounds like this ^^ is the real question. >> Also, who is going to drive the work? From a philosophical standpoint >> though, the switch seems to be a no-brainer. >> >> >> _______________________________________________ >> dev-fxos mailing list >> [email protected] <mailto:[email protected]> >> https://lists.mozilla.org/listinfo/dev-fxos >> <https://lists.mozilla.org/listinfo/dev-fxos> > > > _______________________________________________ > dev-fxos mailing list > [email protected] <mailto:[email protected]> > https://lists.mozilla.org/listinfo/dev-fxos > <https://lists.mozilla.org/listinfo/dev-fxos> > >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
