-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #3 from scantist/jackie-vite-press
Various changes
- Loading branch information
Showing
13 changed files
with
275 additions
and
32 deletions.
There are no files selected for viewing
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Empty file.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,68 @@ | ||
--- | ||
title: Upload Scan Settings | ||
author: Shamala Mani Vannan, Jackie Tan | ||
page: true | ||
lang: en-US | ||
tags: scan type, schedule scan, binary, build-based, docker, cli | ||
--- | ||
|
||
<ClientOnly> | ||
|
||
# {{ $frontmatter.title }} | ||
|
||
>Get the most out of your upload scans with these configuration options | ||
## Select your Scan Type | ||
|
||
<hr style="border:2px solid gray" /> | ||
|
||
1. Click on the newly added project | ||
|
||
2. Click on "Project Settings" in the top right corner | ||
|
||
3. Under the "Scan Settings", select the testing solution you want to configure | ||
|
||
![insert image]() | ||
|
||
## Schedule Scan | ||
|
||
<hr style="border:2px solid gray" /> | ||
|
||
You can set your scan to be done on a scheduled basis for all scan types. The available options for the scheduled scans are as follows: | ||
|
||
::: tip Daily | ||
7:00 AM Singapore Timezone | ||
::: | ||
|
||
::: tip Weekly | ||
every Monday at 7:00 AM Singapore Timezone | ||
::: | ||
|
||
::: tip Monthly | ||
Starting from the date the scheduled scan is enabled. For example, if you enable the schedule scan settings on Janaury 1, the subsequent monthly scans will occur on the 1st of every month | ||
::: | ||
|
||
<div style="display: flex;"> | ||
<div style="flex: 2;"> | ||
|
||
To schedule a scan in Scantist, you can follow these steps: | ||
|
||
1. Toggle the switch to enable scheduled scans | ||
|
||
2. Choose whether your project is a source code or binary project | ||
|
||
3. Select the version of the project that you want to scan | ||
|
||
4. Choose the frequency of the scheduled scan: daily, weekly or monthly | ||
|
||
5. Click "Save" to save the scheduled scan settings | ||
|
||
</div> | ||
<div style="flex: 1;"> | ||
|
||
![insert image]() | ||
|
||
</div> | ||
</div> | ||
|
||
</ClientOnly> |
14 changes: 0 additions & 14 deletions
14
docs/en-US/Trigger-Scan/build-based-scan-ci-cd/jenkins-ci.md
This file was deleted.
Oops, something went wrong.
40 changes: 40 additions & 0 deletions
40
docs/en-US/build-based-scan-ci-cd/Jenkins-CI-Integration.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
--- | ||
title: Jenkins CI Integration | ||
author: Shamala Mani Vannan, Jackie Tan | ||
page: true | ||
lang: en-US | ||
tags: ci, jenkins, continuous integration | ||
description: This document explains how to integrate Jenkins CI | ||
--- | ||
|
||
<ClientOnly> | ||
|
||
# {{ $frontmatter.title }} | ||
|
||
>Discover Scantist's capabilities with Jenkins integration | ||
## Jenkins CI | ||
|
||
Jenkins is a popular choice of continuous integration and continuous delivery solution for developers to integrate with a variety of development, testing, and deployment tools. Jenkins is highly extensible and customizable, which makes it suitable for a wide range of projects - from small single-developer projects to large enterprise-level applications. | ||
|
||
Integrating Scantist into the development lifecycle of Jenkins CI can help enforce security and licensing compliance in the CI/CD pipeline. There are two ways to integrate Scantist with Jenkins CI: | ||
|
||
1. Using Jenkinsfile | ||
|
||
2. Using Scantist CLI | ||
|
||
## Follow these steps to integrate Scantist with Jenkins CI using Jenkinsfile | ||
|
||
|
||
This approach allows Jenkins users to scan their code for security vulnerabilities and licensing issues during the build process. | ||
|
||
**1. Create access token** | ||
|
||
You will need to create an access token on Scantist to authenticate and authorize the integration between Scantist and other tools. | ||
|
||
…….. | ||
|
||
Follow these steps to integrate Scantist with Jenkins CI using Scantist CLI | ||
This approach involves running the Scantist CLI as part of your Jenkins build process - can be more flexible than using the Jenkinsfile, but it required more configuration and setup | ||
|
||
</ClientOnly> |
Empty file.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters