Apex Code Quality Tools for Force.com

This guide will get a fully functional 30 day Multi-Project evaluation version of the enterprise CodeScan running on your own server.

For more information about Multi-Project and Single-Project licenses, visit the FAQ.

Installation Methods

There are several ways of getting CodeScan running.

CodeScan Bundler

This method will download SonarQube, Jenkins and CodeScan and get it running on a Windows machine.

Pros:

  • Quick to get going, ideal for trialling and demos

Cons:

  • Not appropriate for shared usage as it’s not installed as a service, and SonarQube is not running on a ‘production’ database.

If you want to use our quickstart bundler please go to our bundler instructions page.

CodeScan Full Install

This method will guide you through doing a full install.

Pros:

  • It’s production ready

Cons:

  • It takes a bit longer and requires a bit more skill

Go to our installation instructions page.

Using Heroku

This method gets you running on your own Heroku cloud service.

Pros:

  • You don’t need to install any servers

Cons:

  • It’s not on premises, which may not suite your needs.

To get SonarQube running on Heroku, go to our Setting up SonarQube on Heroku page

Running a job:

  • If you are integrating with Git, you may choose to use the CodeScan with Heroku CI Pipelines option
  • If you are happy running the job locally, you can set run the jobs from the command line. See our installation instructions page, in particular the ‘Setting up a project’ section
  • There are variou other options for running the jobs on CI servers like Jenkins and Bamboo. You may also choose to use a cloud CI service like CloudBees - as long as the service supports running ant tasks, then you should be able to get it to work.
CodeScan documentation

Copyright © Village Chief Pty Ltd – 2014-2017. ABN: 11 153 295 571