Skip to content

chore: disable SonarCloud scan for forks#301

Merged
haakemon merged 1 commit into
mainfrom
chore/234-disable-sonarcloud-check-for-fork-pr
Jun 30, 2022
Merged

chore: disable SonarCloud scan for forks#301
haakemon merged 1 commit into
mainfrom
chore/234-disable-sonarcloud-check-for-fork-pr

Conversation

@haakemon
Copy link
Copy Markdown
Contributor

@haakemon haakemon commented Jun 29, 2022

Description

Builds from forks always result in a failed check, because they do not have access to the SONAR_TOKEN secret. This is very annoying. We investigated possibilities to be able to run this check in a separate workflow which had access to the secret in #255 , but it turned out to be a bit complex, and not worth the trouble.

We should instead disable SonarCloud scan on forks, and if we want coverage checks (or other checks) from forks, we should add other tools to our pipeline (tools which ideally do not require any secrets, because then we get into the same problem again)

Related Issue(s)

Verification

  • Your code builds clean without any errors or warnings
  • Manual testing done (required)
  • Relevant automated test added (if you find this hard, leave it and we'll help out)
  • All tests run green

@haakemon haakemon requested a review from tjololo June 29, 2022 08:42
@sonarqubecloud
Copy link
Copy Markdown

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

Copy link
Copy Markdown
Contributor

@olemartinorg olemartinorg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SonarCloud seems to be happy about this change, and so am I. 😉

@haakemon haakemon merged commit 086515b into main Jun 30, 2022
@haakemon haakemon deleted the chore/234-disable-sonarcloud-check-for-fork-pr branch June 30, 2022 07:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants