Build-based Scan - CI/CD Pipeline
Explore the possibilities of automating the entire software development lifecycle, from building, testing, and, deployment to production.
Continuous Integration (CI)
Merging code changes from multiple developers into a shared code repository multiple times a day, and then automatically building and testing the code to detect any issues early on. This approach helps teams catch errors before they become bigger problems and allows for quicker resolution.
Continuous Delivery (CD)
Automatically deploying code changes to production or testing environments, depending on the team's preferences and requirements. Although the approach is automatic, it requires human intervention to manually trigger the deployment of the changes.
Scantist CI/CD Integration
By integrating Scantist with your CI/CD system, you can automatically scan your open source components for vulnerabilities and compliance issues, as part of your build and testing processes. To learn more about the CI/CD system of choice, please refer to the table below and select the corresponding system.
To integrate Scantist with your CI/CD system, you need to ensure the followings:
- Java is available in the build environment (minimum JDK1.8)
- A manifest file is available in the source code project
 |  |  |
| Bamboo | CircleCI | Github Actions |
 |  |  |
| Gitlab CI | Jenkins | Travis |
Other CI/CD Tool
Scantist can be integrated with any CI/CD tool that is not mentioned on the list. To integrate with other CI/CD tools, set environmental variables on your system and configure your build script.