I updated the config-ui-changes branch <https://github.com/jenkinsci/jenkins/commits/config-ui-changes> to now have the frontend-maven-plugin use an io.js executable instead of node.js for running gulp (for bundling JavaScript modules etc). This is really just in interim thing until node.js and io.js reunite/merge (whatever that will mean in reality).
The reason we are moving to io.js is to allow us use a newer version of a package called jsdom, which is really useful for testing JS code. The reason we want to use a newer version of that is because the newer versions do not require a package called contextify, which is a total pain for windows users. Moving the frontend-maven-plugin to use io.js was not as straightforward as one might expect. It required hacking the root pom so that it would handle the download and install of io.js and npm for the frontend-maven-plugin (Vs it doing it itself, which it couldn't do for io.js). Not pretty, but it allows us move forward and it's only an interim thing. I added pom sections to handle windows and linux but haven't tested them. I think they should work, but would be great if someone could try windows and linux. I know Gus is on vacation this week, so that rules him out. Regards, T. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/39dad78a-18c8-4402-87f2-c9632fa2564d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
