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

email-ext plugin does not save configuration on job

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • email-ext-plugin
    • Email-ext plugin version 2.24.1 / 2.25
      Jenkins version LTS 1.446.2 / LTS 1.480.2

      Each job lost the stored email addresses.
      $DEFAULT_RECIPITENS is the env that I see each time I reopen a previously confiugred job.
      This does not allow to communicate to developers the failing builds.

        1. issue_snapshot.png
          issue_snapshot.png
          71 kB
        2. jenkins_email_ext.png
          jenkins_email_ext.png
          77 kB
        3. ext-email.jpg
          ext-email.jpg
          110 kB

          [JENKINS-15442] email-ext plugin does not save configuration on job

          Federico Paolantoni created issue -

          Alex Earl added a comment -

          I can't replicate this. I use the same versions with no problems.

          Alex Earl added a comment - I can't replicate this. I use the same versions with no problems.

          I configured some env variables instead of typing each time the list of recipients.
          So in the main jenkins configuration there is a variable MAILING_LIST_JAVA and in each job i type $MAILING_LIST_JAVA in recipient form, but when I re-open a previously saved configuration I always see $DEFAULT_RECIPIENTS

          Federico Paolantoni added a comment - I configured some env variables instead of typing each time the list of recipients. So in the main jenkins configuration there is a variable MAILING_LIST_JAVA and in each job i type $MAILING_LIST_JAVA in recipient form, but when I re-open a previously saved configuration I always see $DEFAULT_RECIPIENTS

          Alex Earl added a comment -

          I also use environment variables in my configuration and have no issues. Are you sure you are running 2.24.1? Did you restart Jenkins after upgrading?

          Alex Earl added a comment - I also use environment variables in my configuration and have no issues. Are you sure you are running 2.24.1? Did you restart Jenkins after upgrading?

          Yes, i allways use to check the checkbox "restart jenkins after plugin installation".
          I don't see error in logs on restart.

          Federico Paolantoni added a comment - Yes, i allways use to check the checkbox "restart jenkins after plugin installation". I don't see error in logs on restart.

          Alex Earl added a comment -

          I just tried this again to make sure, and I am unable to reproduce the issue.

          Alex Earl added a comment - I just tried this again to make sure, and I am unable to reproduce the issue.

          The environment where i'm having this issue is a Red Hat Enterprise Linux Server release 6.2 (Santiago)
          Tocmat 7.
          Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
          Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode)

          Unfortunately I don't know how to give you more info..
          Could I set a different log level for this plugin?

          Thanks for your investigation.

          Federico Paolantoni added a comment - The environment where i'm having this issue is a Red Hat Enterprise Linux Server release 6.2 (Santiago) Tocmat 7. Java(TM) SE Runtime Environment (build 1.6.0_30-b12) Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode) Unfortunately I don't know how to give you more info.. Could I set a different log level for this plugin? Thanks for your investigation.

          Alex Earl added a comment -

          No, there isn't a higher level of logging for the plugin. Can you try looking at the HTTP traffic in your browser when you submit and send the fields that are being sent to the server?

          Alex Earl added a comment - No, there isn't a higher level of logging for the plugin. Can you try looking at the HTTP traffic in your browser when you submit and send the fields that are being sent to the server?

          Alex Earl added a comment -

          Looks like your Jenkins version is pretty old. Can you try upgrading to the most recent LTS (1.466.x) and see if you still have the issue. The testing for the plugin is always done with the latest LTS.

          Alex Earl added a comment - Looks like your Jenkins version is pretty old. Can you try upgrading to the most recent LTS (1.466.x) and see if you still have the issue. The testing for the plugin is always done with the latest LTS.
          Alex Earl made changes -
          Resolution New: Cannot Reproduce [ 5 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            slide_o_mix Alex Earl
            frido82 Federico Paolantoni
            Votes:
            5 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: