volcano
volcano copied to clipboard
add jobflow code generation template yaml,deploy yaml
add jobflow code generation template yaml,deploy yaml,update makefile
@zhoumingcheng: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
In response to this:
/retest
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/retest
@zhoumingcheng: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
In response to this:
/retest
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/assign @Thor-wl @shinytang6 @william-wang
/retest
@zhoumingcheng: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
In response to this:
/retest
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign shinytang6
You can assign the PR to them by writing /assign @shinytang6
in a comment when ready.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment
/ok-to-test
/retest
@zhoumingcheng What's the overall progress of jobflow feature? The jobflow will be deployed in cluster after this PR is merged. I think this PR the last step to complete jobflow. Maybe we can sync this on the weekly meeting.
@zhoumingcheng What's the overall progress of jobflow feature? The jobflow will be deployed in cluster after this PR is merged. I think this PR the last step to complete jobflow. Maybe we can sync this on the weekly meeting.
The basic functions of the current jobflow have been completed. Here, the pr of the entire jobflow is divided into multiple small prs according to the previous batch submission requirements. The first part is the pr of the design document, which is the code generation template yaml and deploy yaml of jobflow submitted in the second part. The code part is done. It is also possible to submit the pr-first merge of the code section. Here to ask you for your opinion.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.