Lineaje Learning Center
  • About Lineaje
  • Lineaje Product Offering
  • Getting started
    • Create an account
      • Configure Azure AD for sso
      • Configure Okta for sso
    • Onboarding workflow
  • SBOM360, OSM
    • Generate an SBOM
      • Source Code Management (SCM) As Source
        • Public Code Repositories
        • Private Code Repositories
          • Configure GitHub credentials
          • Configure Bitbucket credentials
          • Configure Gitlab credentials
          • Configure Git credentials
          • Configure Azure Repo
        • Frequently Asked Questions
      • Container Image As Source
        • Public Container Image
        • Private Container Image
          • Configure AWS Elastic Container Registry
          • Configure Google Container Registry
          • Configure Docker Hub
          • Configure Generic OCI Registry
          • Configure Azure Container Registry
        • Frequently Asked Questions
      • Existing SBOM As Source
        • EO 14028 checks
      • Manifest file As Source
      • Android Package Kit (APK)
      • Using Lineaje CLI
    • Explore Your SBOM
      • Info
      • Attestation
      • IRL
      • Dependencies
      • Provenance
      • Vulnerabilities
      • Mitigations
      • Security Posture
      • Code Quality
      • Suppliers & Licenses
      • Findings
    • Manage Your SBOM
    • Dashboard
    • Search
    • Policies and Gates
    • Organization and User Management
      • Organization example
    • Lineaje AI
    • AI Plan and AI Remediate
      • JIRA Integration
  • SBOM360 Hub
    • My Products
    • My SBOMS
    • Find & Review SBOMs
    • Manage Your Repository
    • Request and Share SBOMS
    • Settings
    • User Roles
  • Lineaje CLI
    • System Configuration
    • Toolset Configuration
    • CLI Installation
    • CLI Usage
    • Troubleshooting CLI issues
    • Support matrix
  • Integration with CICD pipeline
    • Pre-Requisites
    • Generate Project from source code
      • Project creation using Lineaje cloud
  • Abbreviations and Descriptions
  • Release Notes
    • Unified Scanner for AWS
Powered by GitBook
On this page
  1. Integration with CICD pipeline

Pre-Requisites

PreviousIntegration with CICD pipelineNextGenerate Project from source code

Last updated 1 year ago

The first step is to download the Lineaje CLI from the Lineaje portal, register the CLI and store it in a s3 (or an equivalent storage based on the cloud provider) location that will be accessible for the CICD pipeline

  • Create a s3 folder under a bucker that is accessible for the CICD pipeline (s3:<bucketname>/lineaje-cli)

  • Follow the guide

  • Copy the veecli executable to the s3 location (s3:<bucketname>/lineaje-cli/veecli). On a regular interval, update the veecli with newer version by downloading the copy from Lineaje application. A new version does NOT require a re-registration.

  • Locate the config.json, present in the same directory as that of veecli, and copy it to s3 location (s3:<bucketname>/lineaje-cli/config.json). config.json has the tenant, token and other information that is necessary to connect to Lineaje backend

  • Create a new json file, name it as input-src.json with the below content. This serves as a template for input that should be passed to Lineaje CLI. Store the file in s3 (s3:<bucketname>/lineaje-cli/input-src.json)

{
  "project": "",
  "schema": "1.0",
  "version": "",
  "excludeTestDependency": true,
  "excludeOptionalDependency": true,
  "use_native_tools": true,
  "inputs": [
    {
      "SrcInfo": {
        "srcurl": "",
        "type": "",
        "matchingref": ""
      }
    }
  ],
  "repository_access_configs": [
    {
      "path": "",
      "type": "",
      "user_name": "",
      "token": ""
    }
  ]
}
  • To summarize, the s3 folder should have the below files

    • s3:<bucketname>/lineaje-cli/veecli

    • s3:<bucketname>/lineaje-cli/config.json

    • s3:<bucketname>/lineaje-cli/input-src.json

CLI installation