Repository navigation
HDDS-16935. Distinguish CI checks and splits in Develocity - #11492
Draft
adoroszlai wants to merge 1 commit into
Draft
adoroszlai wants to merge 1 commit into
adoroszlai wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changes were proposed in this pull request?
Develocity can show build time trends, but currently they are meaningless, because various checks with different "usual" run time are mixed.
This change proposes to add two custom key/value pairs:
check: added in checks using Maven to distinguish checks (e.g.build,checkstyle,integration)testset: added inintegrationcheck to record the name of the split (eg.hdds,snapshot,flaky)Disable scan publishing for a
mvn cleancommand run injunit.sh, no need to pollute Develocity with these.Make
REPORT_DIRdefinition uniform across the check scripts touched.https://issues.apache.org/jira/browse/HDDS-16935
How was this patch tested?
Develocity scans are saved only for runs in
apacherepo, so the custom key/values can be verified after CI run of commit onmasterif this is merged.CI in fork for regression:
https://github.com/adoroszlai/ozone/actions/runs/38228367914