8000 Improvements in project build coverage reporting. by jgebal · Pull Request #1182 · utPLSQL/utPLSQL · GitHub
[go: up one dir, main page]
Skip to content

Improvements in project build coverage reporting. #1182

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 7 commits into from
Feb 6, 2022
Merged

Improvements in project build coverage reporting. #1182

merged 7 commits into from
Feb 6, 2022

Conversation

jgebal
Copy link
Member
@jgebal jgebal commented Feb 4, 2022 •
edited
Loading

Testing to see if we can get multiple sonar analysis results in a PR (one per each job run).

Running parallel Sonar analysis is not possible.

Added CodeCov coverage analysis on project.
Added DB level object analysis with sonar.

@jgebal jgebal force-pushed the feature/test_parallel_sonar_analysis branch from 84336b5 to f216a28 Compare February 4, 2022 23:42
@codecov-commenter
Copy link
codecov-commenter commented Feb 5, 2022 •
edited by codecov bot
Loading

Codecov Report

❗ No coverage uploaded for pull request base (develop@b0a2aab). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##             develop    #1182   +/-   ##
==========================================
  Coverage           ?   94.88%           
==========================================
  Files              ?      104           
  Lines              ?     4844           
  Branches           ?       21           
==========================================
  Hits               ?     4596           
  Misses             ?      241           
  Partials           ?        7
Flag Coverage Δ
11xe 94.32% <0.00%> (?)
18xe 94.68% <0.00%> (?)
21xe 94.68% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b0a2aab...1448ef1. Read the comment docs.

@jgebal
Adding Codecov.
3f4d2f6 
Trying to fix Sonar DB level analysis.
@jgebal jgebal force-pushed the feature/test_parallel_sonar_analysis branch from 92e338e to 3f4d2f6 Compare February 5, 2022 22:59
@jgebal jgebal force-pushed the feature/test_parallel_sonar_analysis branch from 292ab24 to 0e5d404 Compare February 5, 2022 23:22
@jgebal jgebal changed the title Composing a separate build string for sonar analysis on parallel builds Improvements in project build coverage reporting. Feb 6, 2022
@github-actions
Copy link
Contributor
github-actions bot commented Feb 6, 2022 •
edited
Loading

Unit Test Results

       1 files         2 suites   1m 50s ⏱️
1 014 tests 1 010 ✔️ 4 💤 0 ❌
1 017 runs  1 009 ✔️ 8 💤 0 ❌

Results for commit 1448ef1.

♻️ This comment has been updated with latest results.

@sonarqubecloud
Copy link
sonarqubecloud bot commented Feb 6, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@jgebal jgebal merged commit d81824a into develop Feb 6, 2022
@jgebal jgebal deleted the feature/test_parallel_sonar_analysis branch February 6, 2022 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@jgebal @codecov-commenter
0