[SERVER-1121] Extract JRuby library Created: 2016/02/02  Updated: 2016/08/10  Resolved: 2016/07/27

Status: Closed
Project: Puppet Server
Component/s: None
Affects Version/s: None
Fix Version/s: SERVER 2.5.0

Type: Epic Priority: Normal
Reporter: Chris Price Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relates to TK-378 jruby-utils: Move CLI clj files into ... Accepted
relates to TK-380 jruby-utils: Add a stop lifecycle fun... Closed
Epic Name: Extract JRuby library
Sub-team: Emerald, emerald
Epic Status: Done
Release Notes: Not Needed
QA Contact: Erik Dasher


This epic would entail extracting the JRuby instance / pool logic from Puppet Server and into its own git repo.

This would need to be usable by Code Manager, and probably should not include any of the puppet-specific logic. Just the code for managing the configuration of JRuby ScriptingContainers, the pool logic, etc.

In addition to making the code re-usable by Code Manager, it would also break up our tests into smaller chunks, so that devs working on puppet-server don't need to run all of the very expensive JRuby tests. It'll also give as an easier place to work on a branch for upgrading to JRuby9k.

Comment by Chris Price [ 2016/02/02 ]

This epic may overlap a bit with PE-13768.

Comment by Erik Dasher [ 2016/04/20 ]

Discussed in Emerald sprint planning. We don't believe any of the changes in this epic will produce changes that would be testable by QA. I'm setting QA Reviewed on this ticket and the member tickets for this sprint. QA does not plan to validate any of the tickets in this sprint.

Generated at Tue Jul 14 03:50:05 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.