Description
When Create an entity to represent a tasks Triggeration · Issue #824 · merico-dev/lake done, POST /task behave differently. config-ui need a new design for task management to work properly
The coming pipeline api design is much more like gitlabs. In gitlab, a pipeline contains a set of job; in devlake, a pipeline contains a set of task, job/task share the same execution manner as following screenshot
And users can manage them both pipeline and task based on what they need:
Describe the solution you'd like
Design our pipeline and task management similar to pipeline and job from gitlab. no need to be as complete as gitlab but share the same idea to fulfill our need at the moment.
And I would like the tasks layout to be arranged accordingly to our json body as following:
Additional context
This depends on issue #824
@e2corporation let me know if you need more context
Description
When Create an entity to represent a tasks Triggeration · Issue #824 · merico-dev/lake done,
POST /taskbehave differently.config-uineed a new design for task management to work properlyThe coming pipeline api design is much more like gitlabs. In gitlab, a
pipelinecontains a set ofjob; in devlake, apipelinecontains a set oftask,job/taskshare the same execution manner as following screenshotAnd users can manage them both
pipelineandtaskbased on what they need:Describe the solution you'd like
Design our
pipelineandtaskmanagement similar topipelineandjobfrom gitlab. no need to be as complete asgitlabbut share the same idea to fulfill our need at the moment.And I would like the
taskslayout to be arranged accordingly to our json body as following:Additional context
This depends on issue #824
@e2corporation let me know if you need more context