I've tried to compile jenkinsci on my 32 bit Debian 9 server, and it failed because it can't build a link to download the correct node version. Indeed, there is no entry for Linux 32 bits.

The error :

[WARNING] Could not get content
java.lang.IllegalArgumentException: Illegal character in path at index 32: https://nodejs.org/dist/v4.0.0/${node.download.file}
...
[ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.1:wget (get-node) on project jenkins-war: IO Error: Could not get content -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.1:wget (get-node) on project jenkins-war: IO Error

You can find the full log here : http://dufour.tk/~quentin/logs/mvnlogs4.log

I previously had the same problem for blueocean-plugin, as discussed in this conversion on the mailing list and was solved by a pull request on the plugin-pom repository.

I've read in the contributing guide, pull requests should be linked with an issue ID, which is why I'm creating this issue. You can find the pull request on the github repository.

As suggested by andresrc, it's also the opportunity to discuss about which architectures and OS should be supported by jenkins during compilation. I'm thinking to arm for example. And maybe document that architecture limitation somewhere.

I've also spotted 2 more files which are containing a dependency on node.js which should be updated if this pull request is accepted :

• https://github.com/jenkinsci/js-builder/blob/master/res/sample_extract_pom.xml
• https://github.com/jenkinsci/js-libs/blob/master/js-module-base/pom.xml