Continuous Integration Guide
Setting up Fixinator to scan your code for security issues every time code is committed to your ColdFusion / CFML source code repository requires the use of a Continuous Integration (CI) tool. There are many tools to choose from and we've created instructions for many of the popular tools.
There are a few considerations when choosing a tool, in many cases your version control platform may have a CI tool built in. BitBucket provides Bitbucket Pipelines, GitLab has GitLab Pipelines, GitHub has Github Actions (in beta). Then there are CI tools that run standalone, examples include TravisCI, CircleCI, and Jenkins.
If you need to run CI on your own servers (not in the cloud) then you might consider using something like Jenkins or Microsoft Team Foundation Server (TFS).
Here are a few popular integrations, if your CI tool is not listed we'd be happy to help guide you.
- Running Fixinator on Bitbucket
- Running Fixinator on Github Actions
- Running Fixinator on GitLab CI / CD
- Running Fixinator on Azure DevOps or TFS (Any Git or Subversion Repository)
- Running Fixinator on AWS CodeBuild (GitHub, BitBucket or AWS CodeCommit)
- Running Fixinator on Jenkins (Any Git or Subversion Repository, Run Locally)
- Running Fixinator on Travis-CI (GitHub)
- Running Fixinator on CircleCI (GitHub or Bitbucket)
- Running Fixinator on TeamCity (Run Locally any Git, Mercurial or Perforce repository)
