Add the ability for Harness to report GitHub commit status
complete
H
Historic Scallop
We use GitHub's pull request feature exclusively for ensuring that code passes certain tests before it's allowed to be merged. This can be things like linting, code quality checks, or executing test builds.
Having the ability for Harness to run a build when a PR is created (works today) and then report back the commit status (pass/fail) to the pull request will allow us to bypass the use of GitHub actions.
We're aware that we can setup a webhook, but this must be done on each repo and will become quite laborious.
Sonarqube is a good example of a thirdparty application that reports back the status of a PR and allows (or disallows) the merging capability of the PR
I believe this is GitHub Statuses here: https://docs.github.com/en/rest/commits/statuses?apiVersion=2022-11-28
Sonarqube docs: https://docs.sonarsource.com/sonarqube/latest/devops-platform-integration/github-integration/#reporting-your-quality-gate-status-in-github
Deepsource is another great example of how to integrate a thirdparty into the GitHub PR process: https://discuss.deepsource.com/t/improved-github-pull-request-integration/442
Log In
Canny AI
Merged in a post:
Harness STO Build Status Icons
F
Fuzzy Woodpecker
In GitHub repositories it is currently possible to link to a Jenkins CI job to show the build status as an icon (badge) - this is achieved using an image link to a Jenkins server URL that shows the status of the repositories corresponding build status - passing / failing / errors, etc in the repository README.md. It would be fantastic if we could do the same for Harness STO - we have two STO pipelines, one that ingests Anchore scan results and policy and another that performs SAST analysis - it would be great to be able to link to those URLs for the given repository's latest execution on the default branch in Harness STO and get the vulnerability status as a clickable image link to the latest executions.
N
Nofar Bluestein
complete
N
Nofar Bluestein
Hey,
This is already supported. If you are using a CI stage which automatically clones your repository per 'codebase' setting, the status of each stage is automatically sent to github as a status check for the PR that fired the build.
Please see this document for more information : https://developer.harness.io/docs/continuous-integration/use-ci/codebase-configuration/scm-status-checks/
Regards,
Nofar Bluestein,
Harness product team
This post was marked as
in progress
Pranav Rastogi
this fiscal quarter
Pranav Rastogi
under review