Skip to content
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

CHEF-7180: Configures sonarqube for code coverage anlaysis #758

Merged
merged 1 commit into from
Nov 20, 2023
Merged

CHEF-7180: Configures sonarqube for code coverage anlaysis #758

merged 1 commit into from
Nov 20, 2023

Conversation

Vasu1105
Copy link
Contributor

Description

This PR

  • adds the sonar-project.properties file required for sonarqube configuration for code coverage analysis.
  • Updates the expeditor coverage pipeline configurations
  • Update coverage.sh to access the sonar token and run the sonar scan.

Related Issue

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New content (non-breaking change)
  • Breaking change (a content change which would break existing functionality or processes)

Checklist:

  • I have read the CONTRIBUTING document.

@Vasu1105 Vasu1105 requested a review from a team as a code owner November 20, 2023 08:26
@Vasu1105 Vasu1105 changed the title Configures sonarqube for code coverage anlaysis CHEF-7180: Configures sonarqube for code coverage anlaysis Nov 20, 2023
@Vasu1105 Vasu1105 merged commit 85f5453 into main Nov 20, 2023
1 check passed
@Vasu1105 Vasu1105 mentioned this pull request Nov 20, 2023
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ahasunos ahasunos ahasunos approved these changes

@sathish-progress sathish-progress Awaiting requested review from sathish-progress sathish-progress is a code owner automatically assigned from inspec/inspec-core-team

Assignees

@Vasu1105 Vasu1105

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@Vasu1105 @ahasunos