Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-8291

Bad user data in runtime job parameters

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Reopened (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: job-exporter-plugin
    • Labels:
      None
    • Environment:
      Linux, LDAP authentification.
    • Similar Issues:

      Description

      Hi,

      I just upgraded to the latest Hudson version 1.389. Previous version was 1.387, and there this problem did not appear.

      We have Hudson jobs where the user who triggers a build will subsequently receive notifications via email.

      To find out the user's email address and full name, I use the job-exporter plugin. The corresponding fields

      • 'build.user.fullName' and
      • 'build.user.emailAddress'
        used to contain the correct information.

      Since version 1.389, this is no longer true - these two fields contain the Hudson administrator's data.
      Additionally, the 'build.user.name' field now contains the full user name, and not the user id.

      See for example this hudsonBuild.properties file:

      #Mon Dec 13 11:49:53 CET 2010
      build.cvsBranch=
      build.hudson.version=1.389
      build.jobName=MAC Developer's SCT
      build.user.fullName=Joe Doe
      build.number=2016
      build.summary=Executor #0 for slave350 \: executing Test #2016
      build.admin.emailAddress=Hudson CI MAC SCT <ciadmin@foobar.com>
      build.id=2010-12-13_11-49-53
      build.user.emailAddress=Hudson CI MAC SCT <ciadmin@foobar.com>
      build.user.name=Joe Doe

      Since the Job Export Plugin hasn't changed, I suspect that this bug is related to the core.

      Please kindly have a look at this issue.

        Attachments

          Activity

          Hide
          evernat evernat added a comment -

          This issue was fixed in the plugin in January 2011, according to https://wiki.jenkins-ci.org/display/JENKINS/Job+Exporter+Plugin

          Please upgrade the plugin to verify.

          Show
          evernat evernat added a comment - This issue was fixed in the plugin in January 2011, according to https://wiki.jenkins-ci.org/display/JENKINS/Job+Exporter+Plugin Please upgrade the plugin to verify.
          Hide
          arost Alexander Ost added a comment -

          Well, the build.user.* fields are no longer wrong, but they are missing completely now (see bug JENKINS-11244).

          Verified with Jenkins version 1.438 (job exporter plugin version 0.3.1).

          Example properties files:

          vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
          #created by com.meyling.hudson.plugin.job_exporter.ExporterBuilder
          #Fri Dec 09 17:37:15 CET 2011
          build.summary=Executor #0 for host341 \: executing Test Job #990
          build.number=990
          build.id=2011-12-09_17-37-15
          build.hudson.version=1.438
          build.admin.emailAddress=Jenkins MAC SCT CI <foo@bar.com>
          build.jobName=Test Job
          build.cvsBranch=
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

          Show
          arost Alexander Ost added a comment - Well, the build.user.* fields are no longer wrong, but they are missing completely now (see bug JENKINS-11244 ). Verified with Jenkins version 1.438 (job exporter plugin version 0.3.1). Example properties files: vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv #created by com.meyling.hudson.plugin.job_exporter.ExporterBuilder #Fri Dec 09 17:37:15 CET 2011 build.summary=Executor #0 for host341 \: executing Test Job #990 build.number=990 build.id=2011-12-09_17-37-15 build.hudson.version=1.438 build.admin.emailAddress=Jenkins MAC SCT CI <foo@bar.com> build.jobName=Test Job build.cvsBranch= ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
          Hide
          m31 m31 added a comment -

          The new plugin version 0.4 should solve this issue.

          Show
          m31 m31 added a comment - The new plugin version 0.4 should solve this issue.
          Hide
          m31 m31 added a comment -

          Please try the new plugin version.

          Show
          m31 m31 added a comment - Please try the new plugin version.
          Hide
          slavd slav dok added a comment -

          Seems like it works as regular build step, but doesn't work when ran from Promoted Builds. This used to work fine for both before.

          I am using 0.4 with Jenkins 1.509.4 (latest LTS version)
          Promoted Builds Plugin is what came bundled with Jenkins (2.11)

          I am missing quite a lot of attributes, but in particular i need build.user.emailAddress

          This is what i see in the build step:###################################################################
          job-exporter plugin started
          hudson.version: 1.509.2
          host: ****
          id: 2013-10-11_14-52-21
          duration: 1.4 sec
          slave:
          started: 2013-10-11T14:52:21
          result: SUCCESS
          result: SUCCESS
          summary: Executor #2 for master : executing GB API Trunk Build » promotion » 2 - Deploy to DEV #1
          executor: 2
          elapsedTime: 1484
          number: 1
          jobName: GB-API-Trunk-Build/promotion/2 - Deploy to DEV
          we have 1 build cause:
          Cause.UserCause Started by user slavd
          new file written: ****\jobs\GB-API-Trunk-Build\workspace\hudsonBuild.properties
          job-exporter plugin finished. That's All Folks!
          ###################################################################

          And this is what i see in the file:#created by com.meyling.hudson.plugin.job_exporter.ExporterBuilder
          #Fri Oct 11 14:52:22 EDT 2013
          build.result=SUCCESS
          build.host=****
          build.slave=
          build.hudson.version=1.509.2
          build.jobName=GB-API-Trunk-Build/promotion/2 - Deploy to DEV
          build.elapsedTime=1484
          build.number=1
          build.executor=2
          build.started=2013-10-11T14\:52\:21
          build.duration=1.4 sec
          build.summary=Executor #2 for master \: executing GB API Trunk Build \u00BB promotion \u00BB 2 - Deploy to DEV #1
          build.admin.emailAddress=*****
          build.id=2013-10-11_14-52-21

          Show
          slavd slav dok added a comment - Seems like it works as regular build step, but doesn't work when ran from Promoted Builds. This used to work fine for both before. I am using 0.4 with Jenkins 1.509.4 (latest LTS version) Promoted Builds Plugin is what came bundled with Jenkins (2.11) I am missing quite a lot of attributes, but in particular i need build.user.emailAddress This is what i see in the build step:################################################################### job-exporter plugin started hudson.version: 1.509.2 host: **** id: 2013-10-11_14-52-21 duration: 1.4 sec slave: started: 2013-10-11T14:52:21 result: SUCCESS result: SUCCESS summary: Executor #2 for master : executing GB API Trunk Build » promotion » 2 - Deploy to DEV #1 executor: 2 elapsedTime: 1484 number: 1 jobName: GB-API-Trunk-Build/promotion/2 - Deploy to DEV we have 1 build cause: Cause.UserCause Started by user slavd new file written: ****\jobs\GB-API-Trunk-Build\workspace\hudsonBuild.properties job-exporter plugin finished. That's All Folks! ################################################################### And this is what i see in the file:#created by com.meyling.hudson.plugin.job_exporter.ExporterBuilder #Fri Oct 11 14:52:22 EDT 2013 build.result=SUCCESS build.host=**** build.slave= build.hudson.version=1.509.2 build.jobName=GB-API-Trunk-Build/promotion/2 - Deploy to DEV build.elapsedTime=1484 build.number=1 build.executor=2 build.started=2013-10-11T14\:52\:21 build.duration=1.4 sec build.summary=Executor #2 for master \: executing GB API Trunk Build \u00BB promotion \u00BB 2 - Deploy to DEV #1 build.admin.emailAddress=***** build.id=2013-10-11_14-52-21

            People

            Assignee:
            m31 m31
            Reporter:
            arostfx arostfx
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: