chore: Add weekly coverage run to Ci, publish to GitHub pages, create and upload TiCS report #5570
Conversation
This file contains 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
Signed-off-by: Peter Makowski <peter.makowski@canonical.com>
- condense some targets in package.json as the in between stages have not been used - add comment to vitest for istanbul coverage - move coverage in own workflow
also add comment to schedule run
- artifact upload v3 will be deprecated on Dec 4th - tics analyzer seems to have run in diagnostic mode, need to test in production (qserver/client) modes now
at least in client mode, probably not in qserver mode(?)
- move TiCS stuff into main test run to profit from checkout and PR info - setup client vs qserver mode for test runs and qualifying runs
workflow name changed but did not update dependent workflow
add soft link
TICS seems to need more than 360 minutes (6 Hours) which is the default for GitHub workers. We bump this to 12 hours to align with the backend TICS runner, which we can reduce down if not needed.
make sure to write cobertura output to `.coverage/` so that it is properly picked up by TiCS
- forgot to remove thresholds - link step should not be needed anymore
Demo
Jenkins 
demos.haus
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.
Done
test.yamlas we do not want to involve a full TiCS measurement on every MP/pushcoverage.yamljob.coveragefor TiCSci-tics-mainis always provoking a run so that we can test thingsQA steps
Fixes
Fixes: TiCS report, adds coverage
Screenshots
(see QA links above)
Notes
Do not merge before January 6th as Tiobe is updating their services and runs will fail or produce incorrect results