I have set up

https://jenkins.ci.cloudbees.com/job/core/job/stapler/

to do CI of Stapler, which was sorely needed. Includes validated merge
support, and (untested) pull request builder support.

Proposal: remove the JRuby integration to a separate repository in the
@stapler org. It is not used from Jenkins core, only
ruby-runtime-plugin, which has not been touched in 2½ years.
stapler-jruby itself has seen little development since then. The tests
are very slow to run, more so than the rest of Stapler combined,
apparently due to inefficient code in JRuby; and seem to fail randomly
with inexplicable errors, so I am skipping them for now. Would seem to
make more sense for it to live in its own repo with a slower release
lifecycle.

(Also not sure who uses stapler-jsp, but at least its tests are quick.)

-- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to