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.

          [JENKINS-19307] Polling environment broken somehow since 1.527

          Hansen Loke added a comment -

          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:

          • Linux environment
          • Mercurial repository workspace
          • Owner of the repository is different to Jenkins, as it is on a NFS mount
          • /etc/mercurial/hgrc is modified to trust the owner of the repository

          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.

          Hansen Loke added a comment - 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: Linux environment Mercurial repository workspace Owner of the repository is different to Jenkins, as it is on a NFS mount /etc/mercurial/hgrc is modified to trust the owner of the repository 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.

          I've submitted https://github.com/jenkinsci/jenkins/pull/937 some time ago.

          Vincent Latombe added a comment - I've submitted https://github.com/jenkinsci/jenkins/pull/937 some time ago.

          Code changed in jenkins
          User: Jesse Glick
          Path:
          changelog.html
          core/src/test/java/jenkins/model/CoreEnvironmentContributorTest.java
          http://jenkins-ci.org/commit/jenkins/1c68183ae80b44e3e11d46d1eb6b20af8f4ecde2
          Log:
          [FIXED JENKINS-19307] Noting merge of pull #937.

          Compare: https://github.com/jenkinsci/jenkins/compare/5c25cb6a1b3d...1c68183ae80b

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/test/java/jenkins/model/CoreEnvironmentContributorTest.java http://jenkins-ci.org/commit/jenkins/1c68183ae80b44e3e11d46d1eb6b20af8f4ecde2 Log: [FIXED JENKINS-19307] Noting merge of pull #937. Compare: https://github.com/jenkinsci/jenkins/compare/5c25cb6a1b3d...1c68183ae80b

          dogfood added a comment -

          Integrated in jenkins_main_trunk #2918
          [FIXED JENKINS-19307] Noting merge of pull #937. (Revision 1c68183ae80b44e3e11d46d1eb6b20af8f4ecde2)

          Result = SUCCESS
          Jesse Glick : 1c68183ae80b44e3e11d46d1eb6b20af8f4ecde2
          Files :

          • core/src/test/java/jenkins/model/CoreEnvironmentContributorTest.java
          • changelog.html

          dogfood added a comment - Integrated in jenkins_main_trunk #2918 [FIXED JENKINS-19307] Noting merge of pull #937. (Revision 1c68183ae80b44e3e11d46d1eb6b20af8f4ecde2) Result = SUCCESS Jesse Glick : 1c68183ae80b44e3e11d46d1eb6b20af8f4ecde2 Files : core/src/test/java/jenkins/model/CoreEnvironmentContributorTest.java changelog.html

          Code changed in jenkins
          User: Vincent Latombe
          Path:
          core/src/main/java/jenkins/model/CoreEnvironmentContributor.java
          http://jenkins-ci.org/commit/jenkins/8fdc471f0278943d587ebafd3a708ae685ae5799
          Log:
          JENKINS-19307 buildEnvironmentFor job shouldn't override slave's environment with
          master's

          (cherry picked from commit 5ac042752ffa0a3303666acc0df1c553a9d50f15)

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Vincent Latombe Path: core/src/main/java/jenkins/model/CoreEnvironmentContributor.java http://jenkins-ci.org/commit/jenkins/8fdc471f0278943d587ebafd3a708ae685ae5799 Log: JENKINS-19307 buildEnvironmentFor job shouldn't override slave's environment with master's (cherry picked from commit 5ac042752ffa0a3303666acc0df1c553a9d50f15)

          Code changed in jenkins
          User: Vincent Latombe
          Path:
          core/src/test/java/jenkins/model/CoreEnvironmentContributorTest.java
          http://jenkins-ci.org/commit/jenkins/65158b098327cfd1bd755c41d5e63cab57b2002b
          Log:
          JENKINS-19307 Check that Computer.currentComputer() is never called
          inside buildEnvironmentFor Job since it doesn't make sense
          outside of a running build.

          (cherry picked from commit 5d56102232ac99ab1812884ba0633c27f82d944b)

          Compare: https://github.com/jenkinsci/jenkins/compare/7501dbed6d71...65158b098327

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Vincent Latombe Path: core/src/test/java/jenkins/model/CoreEnvironmentContributorTest.java http://jenkins-ci.org/commit/jenkins/65158b098327cfd1bd755c41d5e63cab57b2002b Log: JENKINS-19307 Check that Computer.currentComputer() is never called inside buildEnvironmentFor Job since it doesn't make sense outside of a running build. (cherry picked from commit 5d56102232ac99ab1812884ba0633c27f82d944b) Compare: https://github.com/jenkinsci/jenkins/compare/7501dbed6d71...65158b098327

          Dennys Hsieh added a comment -

          Will this patch release to main trunk or just in 1.532 LTS?

          Dennys Hsieh added a comment - Will this patch release to main trunk or just in 1.532 LTS?

          Vincent Latombe added a comment - - edited

          Last message from SCM/JIRA link daemon indicates this has been cherry-picked to 1.532 lts branch. So we should see it in 1.532.1 when it gets released.

          Vincent Latombe added a comment - - edited Last message from SCM/JIRA link daemon indicates this has been cherry-picked to 1.532 lts branch. So we should see it in 1.532.1 when it gets released.

            Unassigned Unassigned
            vlatombe Vincent Latombe
            Votes:
            2 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: