Knowledge Base > DCover in the CI Pipeline > 6. Installation on VMs or during a CI run

Installation on VMs or during a CI run

Before you begin the installation, please obtain the link to download DCover (from your product update email, or contact Diffblue). Please note you need version 2022.03.02 or above, installed and activated with an appropriate license.

Installing on a VM

If you only have a few machines it is possible to manually install DCover on each machine. To do this:

1. Unzip the DCover jar files to a common and accessible directory inside each VM

2. Activate DCover

3. Reference these jar files when calling DCover in your CI scripts.

Installing during a CI run

For most CI systems, you will want to download DCover as part of your CI run.

This link should be added as a secret variable for your CI system, with a memorable name, such as “RELEASE_URL”, so that it can be referenced later. Depending on your CI system this will have a different name but common examples are:

  • Github actions = Secrets
  • Coderbuild = Parameter store
  • Jenkins = Secret text in credentials
  • Gitlab CI = Protected variables

Then, add a step to your pipeline which downloads from this link and extract the contents. Below is an example in github actions:

- name: Get DCover
        run: |
          mkdir dcover
          cd dcover
          wget -c "${{ secrets.RELEASE_URL }}" -O -q

From this point on you will be able to call DCover by referencing the executable extracted from this zip at the location you specified (dcover/dcover in the example above).

Similarly, add a secret variable for your CI system that holds the Dcover license key, such as “LICENSE_KEY”. Activate Dcover each time CI is run. For example

- name: Get DCover
        run: dcover/dcover activate "$LICENSE_KEY"