-
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
-
-
- Closed
-
[JENKINS-16992] Since EnvInject 1.81 variables cannot be used for Base ClearCase plugin VCS polling
Kurt
created issue -
Kurt
made changes -
| Description |
Original:
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). |
New:
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": {noformat} PROJECT=KC001 MinorVersion=${MinorBaseVersion}${MinorMinorVersion} {noformat} Then, in the "Base ClearCase Plugin" I'm using those in the following fields: {noformat} 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 {noformat} 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: {noformat} *************************** 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 {noformat} 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). |
| Component/s | Original: clearcase [ 15503 ] |
| Assignee | Original: Vincent Latombe [ vlatombe ] | New: Gregory Boissinot [ gbois ] |
Gregory Boissinot
added a comment - Which Jenkins version do you use? Kurt
made changes -
| Environment | Original: All machines: Windows 7 x64, JRE 7 x64 |
New:
All machines: Windows 7 x64, JRE 7 x64 Jenkins Versions: At least from 1.501 to 1.504 ClearCase Plugin: 1.3.14 |
Sorry for not giving the versions right away.
I'm quite frequently updating to latest versions. The problem occured when updating the EnvInject plugin to 1.81.
Not sure what was the exact Jenkins version when EnvInject 1.81 was released. But I guess it was something around Jenkins 1.501. So I would say at least for Jenkins 1.501 to 1.504 the problem occurs for me.
ClearCase Plugin Version (maybe no longer relevant but for completness): 1.3.14 (not changed for some time - so not tested any older version)
Additional Remark: I didn't find any exception or other hints in any of the Jenkins logs.
Kurt
added a comment - - edited Sorry for not giving the versions right away.
I'm quite frequently updating to latest versions. The problem occured when updating the EnvInject plugin to 1.81.
Not sure what was the exact Jenkins version when EnvInject 1.81 was released. But I guess it was something around Jenkins 1.501. So I would say at least for Jenkins 1.501 to 1.504 the problem occurs for me.
ClearCase Plugin Version (maybe no longer relevant but for completness): 1.3.14 (not changed for some time - so not tested any older version)
Additional Remark: I didn't find any exception or other hints in any of the Jenkins logs. 
Arjan Veenstra
added a comment - I've first seen this in Jenkins 1.500, together with EnvInject 1.81. I downgraded EnvInject back to 1.80 wich solved the issue. It currently all works for me ruining 1.80 on 1.504.
I'm loading the properties from a file, which might matter. Perhaps this issue is related to JENKINS-16575?
Arjan Veenstra
added a comment - I've first seen this in Jenkins 1.500, together with EnvInject 1.81. I downgraded EnvInject back to 1.80 wich solved the issue. It currently all works for me ruining 1.80 on 1.504.
I'm loading the properties from a file, which might matter. Perhaps this issue is related to JENKINS-16575 ? Kurt
added a comment - I see the problem while using properties from "Properties Content" field.
So it seems this is independent of where the EnvInject properties are coming from.
Kurt
added a comment - I see the problem while using properties from "Properties Content" field.
So it seems this is independent of where the EnvInject properties are coming from. 
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:
Started on Mar 6, 2013 3:54:57 PM Location 'https://server/svn/REPO/${SVN_LOCATION}/Project' does not exist One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@4d4a39[Project], project will be disabled. Done. Took 0.19 sec No changesAfter 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.