-
Notifications
You must be signed in to change notification settings - Fork 383
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
[Improvement] Setting the workflow depends #768
Labels
good first issue
Good for newcomers
help wanted
Extra attention is needed
improvement
Improvements on everything
Milestone
Comments
As I know, integrate tests runs serially, we could make it parallelly. |
Besides, I think the performance of the CI machine is too bad, not sure if we can set up a CI by our own, using AWS EC2 or others to build a CI machine, I'm not sure if the price is lower or higher than the github CI. |
xunliu
added a commit
to xunliu/gravitino
that referenced
this issue
Dec 20, 2023
xunliu
added a commit
to xunliu/gravitino
that referenced
this issue
Dec 20, 2023
[apache#768] improvement(CI): Setting the workflow execution order
xunliu
added a commit
to xunliu/gravitino
that referenced
this issue
Dec 20, 2023
xunliu
added a commit
to xunliu/gravitino
that referenced
this issue
Dec 20, 2023
xunliu
added a commit
to xunliu/gravitino
that referenced
this issue
Dec 21, 2023
xunliu
added a commit
to xunliu/gravitino
that referenced
this issue
Dec 21, 2023
xunliu
added a commit
to xunliu/gravitino
that referenced
this issue
Dec 21, 2023
xunliu
changed the title
[Improvement] Optimize CI execution time in GitHub Action
[Improvement] Setting the workflow depends
Dec 21, 2023
qqqttt123
added
good first issue
Good for newcomers
help wanted
Extra attention is needed
labels
Jan 5, 2024
qqqttt123
pushed a commit
to qqqttt123/gravitino
that referenced
this issue
Jan 15, 2024
qqqttt123
pushed a commit
to qqqttt123/gravitino
that referenced
this issue
Jan 15, 2024
qqqttt123
pushed a commit
to qqqttt123/gravitino
that referenced
this issue
Jan 15, 2024
qqqttt123
pushed a commit
to qqqttt123/gravitino
that referenced
this issue
Jan 15, 2024
qqqttt123
pushed a commit
to qqqttt123/gravitino
that referenced
this issue
Jan 15, 2024
qqqttt123
pushed a commit
to qqqttt123/gravitino
that referenced
this issue
Jan 15, 2024
qqqttt123
pushed a commit
to qqqttt123/gravitino
that referenced
this issue
Jan 15, 2024
qqqttt123
pushed a commit
to qqqttt123/gravitino
that referenced
this issue
Jan 15, 2024
qqqttt123
pushed a commit
to qqqttt123/gravitino
that referenced
this issue
Jan 15, 2024
qqqttt123
pushed a commit
to qqqttt123/gravitino
that referenced
this issue
Jan 15, 2024
qqqttt123
pushed a commit
to qqqttt123/gravitino
that referenced
this issue
Jan 15, 2024
qqqttt123
pushed a commit
to qqqttt123/gravitino
that referenced
this issue
Jan 15, 2024
After discussion, this optimization is useless. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Good for newcomers
help wanted
Extra attention is needed
improvement
Improvements on everything
What would you like to be improved?
Currently,
build.yml
andintegration-test.yml
execute out of order.Integration tests should be performed after the build is successful
How should we improve?
Setting the workflow depends:
build.yml
,The text was updated successfully, but these errors were encountered: