-
Bug
-
Resolution: Fixed
-
Major
Hello,
after upgrade to jenkins 1.527, I started experiencing some problems with polling on clearcase jobs.
Symptom is a 'random' error code returned by the cleartool command, only during polling operation. By launching a build manually, the same cleartool command is called and completes successfully.
I've identified the culprit commit as being 6588f42904ea133b2709750089557e3650bb1910 (from JENKINS-19042), but so far I fail to completely understand how it messes up with the environment when polling is called.
- is blocking
-
JENKINS-19042 EnvironmentContributor.buildEnvironmentFor needs another overloaded version that takes Job
-
- Resolved
-
- is duplicated by
-
JENKINS-19486 Polling with workspace gets incorrect environment
-
- Resolved
-
-
JENKINS-19746 SCM poll retrieves system environment variables from Master even though execution is on slave
-
- Closed
-
- is related to
-
JENKINS-19222 EnvInject undefines NODE_NAME environment variable on master
-
- Open
-
I have a similar polling issue that is introduced in 1.527, but is for Mercurial repository. Maybe it might shed more light into this issue as the symptom is similar to the one that is described, ie polling broken after 1.527 and launching a build works fine. My setup is as followed:
Symptom after upgrading to 1.527, and subsequent releases up to 1.531, is that on polling it doesn't trust the owner of the .hg/hgrc and therefore caused an exception when polling, resulting in no builds being triggered. Downgraded to 1.526, polling works again. I don't have the exception stacktrace but managed to capture the top error instead:
ERROR: Expected to get an id but got 'not trusting file /scratch/jenkins/workspace/****/.hg/hgrc from untrusted user scratch, group scratch not trusting file /scratch/jenkins/workspace/****/.hg/hgrc from untrusted user scratch, group scratch
a519e87a23d76389995bcdc0a1c3195983e0303f' instead.