User Guide
  • Fundamentals
    • Quick Start Guide
      • Signing Up
      • Package Discovery
        • Connecting to GitHub
        • Connecting to GitLab
        • Connecting to Azure DevOps
        • Connecting to the CI Pipeline
        • Connecting to the Artifact Server
      • Package Sealing
        • Integrating the CLI in the CI
        • Editing Dependencies
    • Deployments
      • Choosing Your Deployment
      • Automatic Remediation
      • Remote Configuration
      • Local Configuration
      • Artifact Server
    • CLI
      • Download and Installation
      • Scanning
      • Fixing All Dependencies
      • Fixing Specific Dependencies
      • Fixing OS Vulnerabilities
      • Integrating with the CI
      • Uploading Scan Results
      • Commands
      • SCA Integrations
      • JFrog Integration
      • Usage Examples
        • Sealing Application Dependencies
        • Sealing Linux Environments
    • Artifact Server
      • Generating a Token
      • Artifact Server Ordering
      • Configuring the Package Manager
        • Configuring apk
        • Configuring Composer
        • Configuring Go
        • Configuring Gradle
        • Configuring Maven
        • Configuring npm
        • Configuring pip
        • Configuring Poetry
        • Configuring yarn
        • Configuring yum
      • Clearing the Cache
      • Editing Your Dependencies
    • Web Interface
      • Rules Screen
  • APIs
    • List Vulnerable Packages
  • FAQ
  • Vulnerability Disclosure
Powered by GitBook
On this page
  1. Fundamentals
  2. Artifact Server

Clearing the Cache

As an artifact server Seal only has visibility to those artifacts that are pulled by the build machine. Therefore, if instead of pulling libraries from an artifact server the build machine uses a locally cached copy, the Seal server will be unaware of its usage.

To get an up-to-date snapshot of the packages used as part of your build process, you should first clear your package manager's cache.

Javascript:

  • For npm run:

npm cache clean --force
  • For Yarn v1 run:

yarn cache clean
  • For Yarn v2 and later run:

yarn cache clean --all
  • For pnpm run:

pnpm store prune

Python:

  • For pip run:

pip cache purge
  • For Poetry run:

poetry cache clear --all

Java:

  • For Maven run:

mvn dependency:purge-local-repository -DactTransitively=false -DreResolve=false
  • For Gradle run:

rm -rf $HOME/.gradle/caches/

Go:

  • For Go run:

go clean -modcache

Composer:

  • For compose run:

rm -rf vendor/

PreviousConfiguring yumNextEditing Your Dependencies

Last updated 5 months ago