Conda Application Analysis


The Conda coordinate based matching feature provides the ability to scan and evaluate  dependencies for any language (Python, Java, JavaScript, C++) found in the conda.txt file.

What is supported

Files named conda.txt  will be analyzed. Only requirements using the "=" operator and version without wildcards will be considered. 

Integrations with Conda scanning support

  • CLI from version 88
  • Jenkins from version 3.9.20200623-110149.2e546a0
  • Bamboo from version 1.16.0

Steps to analyze using the CLI

Create requirements

Run conda list command with the flag -e (export).

conda list -e > conda.txt

The conda.txt encoding is UTF-8.  Special note for Microsoft Windows users, the cmd.exe encoding may need to be changed to UTF-8.  Please refer to Microsoft documentation on how to do this.

Example conda.txt file 

# platform: linux-64

Run a scan

Invoke a CLI scan of a directory or subdirectories containing a conda.txt file.  Instructions on how to do this can be found here: Nexus IQ CLI.

Output from cli

Dashboard results

Report results

Steps to analyze using the Jenkins plugin

By default, the Jenkins plugin will not evaluate the conda.txt file. A custom Scan Target is needed.

nexusPolicyEvaluation iqApplication: 'SampApp', iqScanPatterns: [[scanPattern: '**/conda.txt']], iqStage: 'build'

To find more information on how to configure Jenkins please go to the Nexus Platform Plugin for Jenkins.

Steps to analyze using the Bamboo plugin

Bamboo Scan Targets control what files are examined.  To evaluate Conda, add conda.txt to the scan targets via "**/conda.txt".  To find more information on how to configure Bamboo please go to the Nexus IQ for Bamboo.