8000 Register new components as plug-ins without impact on testbed operations · Issue #16 · srdc/gitb · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Register new components as plug-ins without impact on testbed operations #16

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.

Sign up for GitHub

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

Jump to bottom
Open
costas80 opened this issue Jul 10, 2015 · 0 comments
Open

Register new components as plug-ins without impact on testbed operations #16

costas80 opened this issue Jul 10, 2015 · 0 comments
Labels
enhancement

Comments

@costas80
Copy link
Collaborator

Currently test components (messaging handlers and validators) are implemented within the source code of the testbed itself. This means that adding new components requires a new build and deployment of the testbed as a whole. Test components should ideally be packaged as plugins that can be implemented and deployed in isolation, and be usable by the testbed without restarts.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@costas80
0