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

Bad user data in runtime job parameters

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • job-exporter-plugin
    • None
    • Linux, LDAP authentification.

      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.

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

              Created:
              Updated: