I set up a job where 'CVS Plugin' is used to check out sources from a CVS repository using legacy 'pserver' protocol.

In Jenkins' global settings, I configured an environment variable

CVS_ROOT = :pserver:jenkins@192.168.0.100:/home/cvs

In the 'Source Code Management' section of the job, I configured CVSROOT to use this variable (e.g. '${CVS_ROOT}/Prj-0001/').

Building the job manually works as expected (see JENKINS-13186), the variable is expanded and the sources get checked out.

The job should be triggered when changes in the SCM/CVS are recognized. This is done by configuring SCM polling (e.g. 'H/20').

-> Polling CVS fails because the environment variable does not get expanded (see attached screenshot)

(The error messages regarding 'ssh' result from failed parsing of the CVSROOT string and are not related to the issue).

I'm not familiar with developing plugins for Jenkins, but I think the problem should be located somewhere in the CVS plugin. I found a workaround (quick hack) which makes changes to

AbtractCvs.getCvsClient()

and replaces the variable maually in

envVars.expand(repository.getCvsRoot());