-
Notifications
You must be signed in to change notification settings - Fork 8.8k
optimize: enhance ci configuration #7270
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
Open
YoWuwuuuw
wants to merge
12
commits into
apache:2.x
Choose a base branch
from
YoWuwuuuw:20250401
base: 2.x
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 2.x #7270 +/- ##
============================================
+ Coverage 54.24% 54.27% +0.03%
- Complexity 7264 7267 +3
============================================
Files 1178 1178
Lines 41965 41965
Branches 4924 4924
============================================
+ Hits 22764 22777 +13
+ Misses 17050 17036 -14
- Partials 2151 2152 +1 🚀 New features to boost your workflow:
|
xingfudeshi
approved these changes
Apr 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Well done! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ⅰ. Describe what this PR did
● Optimized CI Trigger Conditions:
○Skip CI for .md file-only changes: CI process will not be triggered when the PR only contains modifications to .md files (like: #7226) , reducing unnecessary resource consumption.
○ PR Status Filtering: Avoid closed PRs (like: #7263) from occupying CI activities and prevent the Codecov bot from commenting on closed PRs.
● Maven Repository Caching:
○ Added caching for the Maven repository to accelerate build preparation and speed up CI testing (estimated improvement of 30-60 seconds). Cache status and usage can be viewed at https://github.com/apache/incubator-seata/actions/caches.
○ Reference
● Retry Mechanism:
○ Introduced a retry mechanism(1 time) to avoid CI failures caused by occasional issues. For example, in https://github.com/apache/incubator-seata/actions/runs/14049309257/job/39336574577?pr=7225 and https://github.com/apache/incubator-seata/actions/runs/14026429452/job/39265823304, CI occasionally fails due to sporadic problems (which should not happen), requiring manual triggering of CI.
○ Optimization Enhancement: Manually triggered CI rebuilds tests for all versions, while automatic retries only retry tests for the failed versions, improving efficiency.
○Reference
Ⅱ. Does this pull request fix one issue?
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews