You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After our code refactory, only workflow mode is officially supported. This makes the developing and debugging more complicated. The complication comes from ways:
Many docker images (dev, ci, server, step...) are involved, building images always costs time.
Workflow will run in a k8s cluster, the internal status of the program is not easy to expose.
Modify code and re-deploy need many steps, which takes a lot of time.
Not enough guide for develop/debug/ci/customize model/build runnable.
After some discussion with other developers, I conclude the following refinement todo, most of them are doc modifications:
Developer guide
Local developing environment deploy guide
How to build relative images
How to do unit-test in our ci image
How to do e2e test in local playground, (like how to sharing code with VM, how to submit a test program to the cluster)
How to re-deploy component in local playground
How to release a version
Update model contribution doc
Write runnable building doc
Speed up docker image pulling
Refine our image Dockerfile, make re-build faster
The text was updated successfully, but these errors were encountered:
lhw362950217
changed the title
Make develop/debug/test more efficient for developer
Make developing/debugging/testing more efficient for developer
Sep 24, 2020
After our code refactory, only workflow mode is officially supported. This makes the developing and debugging more complicated. The complication comes from ways:
After some discussion with other developers, I conclude the following refinement todo, most of them are doc modifications:
ci image
Dockerfile
, make re-build fasterThe text was updated successfully, but these errors were encountered: