Consider running teapot part in local executor #83
Labels
No Label
bug
component
executor
component
framework
component
parser
component
UI
duplicate
enhancement
help wanted
invalid
priority
p0
priority
p1
priority
p2
priority
p3
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: JOJ/JOJ3#83
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
To keep the consistency of all steps.
Only env vars are not currently supported. We can pass env vars from joj3 to joint-teapot and let teapot read from env var to run itself.
We need to consider how to force the teapot stage to run when previous stages force quit-ed. Also, this teapot stage needs to run after the result file is generated.
A possible solution: define pre-stages, stages, post-stages. Each group of stages must run even previous groups of stages force quit-ed.(Done in454df2c6fc
)Also, in repo health check,
joj3-check
should also accept env vars, so that we can completely remove teapot part from conf file.The above is done. The only TODO: keep joj3 summary log format, with a new log parser and output similar results in teapot, as joj3 summary log needs info from both joj3 itself and teapot result.
We use env var in local executor to pass info from joj3 to the program in the executor.