-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
All machines: Windows 7 x64, JRE 7 x64
Jenkins Versions: At least from 1.501 to 1.504
ClearCase Plugin: 1.3.14
Since update from EnvInject 1.80 to 1.81 or higher (also tested with 1.82 and 1.83), the variables set by EnvInject plugin in "Prepare an environment for the run"-->"Properties Content" are not expanded when used by ClearCase VCS polling (ClearCase plugin) any longer.
I'm setting the following variables in "Prepare an environment for the run"-->"Properties Content":
PROJECT=KC001 MinorVersion=${MinorBaseVersion}${MinorMinorVersion}
Then, in the "Base ClearCase Plugin" I'm using those in the following fields:
View tag: ${COMPUTERNAME}-snap-${PROJECT}-cont View path: ${COMPUTERNAME}-snap-${PROJECT}-cont Get config spec from a file: ${CCProfiles}\RRM\Continuous\${PROJECT}\Rules Branch(es): br_${PROJECT}_REL_${MajorVersion}_${MinorBaseVersion}x
This has always been working up to now.
Since update to EnvInject 1.81 (no update to ClearCase plugin) this is what's written in the SCM Polling Log of Jenkins:
*************************** get view CSPEC *********************** [Snapshots] $ cleartool catcs -tag RRM-BUILD-S3-snap-${PROJECT}-cont cleartool: Error: View tag "RRM-BUILD-S3-snap-${PROJECT}-cont": ClearCase object not found FATAL: Base ClearCase failed. exit code=1
Hence all variables not coming from EnvInject are expanded properly but the EnvInject "Prepare Environment ..." variables are not.
This only happens in the VCS Polling activity. When manually triggering a build everything works just as expected and all variables are expanded properly.
Unclear whether it's a bug in EnvInject or ClearCase plugin (i.e. using wrong way for expanding the vars).
- is duplicated by
-
JENKINS-17377 Environment variables are not injected at Clearcase polling
-
- Closed
-
I'm seeing the same issue with SVN polling, so it seems this isn't specific to ClearCase. It worked with 1.80, started failing with 1.81 and still fails on 1.83.
The symptoms are like this, when Jenkins polls this is what happens:
After starting the build manually everything works, it builds normally and the polling continues work as well. That is, polling works once the build has finished, not during the build. And after a restart of Jenkins everything is broken again.