Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add InMemory Execution Engine #50

Open
1 of 5 tasks
michaelschnyder opened this issue Jun 2, 2017 · 0 comments
Open
1 of 5 tasks

Add InMemory Execution Engine #50

michaelschnyder opened this issue Jun 2, 2017 · 0 comments
Labels
Milestone

Comments

@michaelschnyder
Copy link
Member

michaelschnyder commented Jun 2, 2017

The initial jobbr server should come with an InMemory variant of the execution engine. The Core Engine is already refactored into a separate project in the ForkedExecution Projekt. But there are still a couple of tasks to do

  • move core execution to separate gh repo (+ build) and reference it as submodule from the forked execution
  • Increase Tests for core component because its now testable on its own. Check if tests are enough
  • Create an InProcess Execution Engine in a separate GH / build / NuGet (reference core rt again)
  • Improve errro message if no execution engine is installed and point to available execution egines on rtfd.io
  • Migrate to .NET 6
@michaelschnyder michaelschnyder added this to the 1.0 milestone Jun 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant