Due to the way Jenkins performs remote class loading and allows plugins to implement callables, is is impractical to support Java 8 on agents without forcing Jenkins core and all commonly used plugins to run on 8 as well.
At worst, builds on exotic OSs with poor Java support can still be done by running the Jenkins agent on, say, Linux and having the actual build steps be run via SSH or some similar remote CLI (with support for file transfer like SCP where required). It would even be possible to write a plugin offering a Pipeline step to run commands on a specified host using SSH without requiring an executor slot (Scripted: no `node`; Declarative: `agent none`). You would not get access to rich publisher steps like `recordIssues` but it might be good enough most of the time, especially if you can cross-compile or whatever from Linux and the only things that truly must be done on the special OS are integration tests. At any rate, so far there is no strong push to drop 8 support so this remains discussion about an indefinite future. -- 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/CANfRfr1hJezjx0Ge99SA_nVF%3Dr98pCuxDhjWPA0XwDoqC%3Drs1A%40mail.gmail.com.
