-
Notifications
You must be signed in to change notification settings - Fork 15
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
Containerize in memory engine #177
Conversation
Proof that the docker build and push works (names might differ a bit): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @remcowesterhoud 🐳
Generally looks good, but I have some questions.
engine/src/main/java/io/camunda/zeebe/process/test/engine/EngineFactory.java
Show resolved
Hide resolved
@korthout Thanks for you review 🙇 I've answered your questions and made some changes. Please check again when you have the time! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the quick changes 🎖️ LGTM
- Added a main class to make the engine executable - Switched to a static port for the grpc server, so we always know what port we need to send the traffic to. - Added a Dockerfile to make it possible to build a container.
Both the deploy workflow and the build/test workflow have to build and run the unit tests. By making the build/test workflow reusable we can call it in the deploy workflow.
Added a job to the deployment pipeline which will build a container from the engine, and push it to dockerhub. The container will default to the "latest" tag. If a new release is created in GitHub the name of the tag attached to this release will be used as the image tag, unless this release is a SNAPSHOT release.
One of the dependencies (zeebe-workflow-engine) requires this dependency. Running the engine without this will result in errors: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder". SLF4J: Defaulting to no-operation MDCAdapter implementation. SLF4J: See http://www.slf4j.org/codes.html#no_static_mdc_binder for further details. Adding this dependency resolves this issue and fixes the logging of the engine.
a63412c
to
9932fbe
Compare
Description
Related issues
closes #5
Next steps will be done in #7
Definition of Done
Not all items need to be done depending on the issue and the pull request.
Code changes:
Testing:
Documentation: