Codety Scanner Quickstart

Let's discover Codety in less than 5 minutes.

Overview

tips

• The Codety Scanner will be running inside your CI/CD workflow, and your code will not leave your CI/CD compute environment.
• It is recommended to trigger Codety analysis pull/merge request events to receive prompt and relevant code analysis results, ensuring code quality is maintained.

Based on the above diagram, your CI/CD pipeline will be:

1. Preparing the analysis environment
   • Checking out source code from git server
   • Pulling Codety analyzer image from container registries(e.g. Docker Hub)
   • Pulling configurations and settings from Codety server (default setting will be applied if you don't set Codety Access Token)
2. Conducting static code analysis according to the custom ruleset settings
3. Assembling and distributing the result, below is an example for GitHub:

Start using it

• Quickstart with GitHub Actions
• Quickstart with GitLab CI
• Quickstart with Harness CI
• Quickstart with Circle CI
• Quickstart with Bitbucket CI

Next step

You can start exploring Codety Cloud-Hosted or Self-Hosted solution for having fine-tuned code analysis settings along with more features.