jenkinsci / jep Goto Github PK

JEP-237 states that

configuration of the JVM, platform etc. is out-of-scope, as is making every feature/plugin compliant

but does not describe which plugins are to be made compliant. In practice, Jenkins core is not usable in production scenarios without at least a few plugins, and its automated tests run with a small number of plugins installed. JEP-237 should clarify which plugins are in the project's scope.

Reproduction steps

See https://github.com/jenkinsci/jep/blob/master/jep/README.adoc#index-of-jenkins-enhancement-proposals

Expected Results

Emojis are displayed as emojis

Actual Results

Text

Anything else?

No response

Are you interested in contributing a fix?

No response

From the JEP template:

If some or all of the changes will require human interaction to verify them, explain why automated tests are considered impractical. Then, summarize what kinds of test cases might be required: user scenarios with action steps and expected outcomes.

JEP-237 asserts that

there would be no new testing introduced in a FIPS-140 compliant environment due to the complexity of maintaining this setup

but does not state the reason why maintaining an automated test setup would be impractical, nor does it summarize the "user scenarios with action steps and expected outcomes".