• Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • email-ext-plugin
    • None
    • Jenkins 1.651.1
      email-ext-plugin 2.41.3

      After updating to version 2.41.3, tokens in email subjects are not replaced any more. Instead they are sent plain:

      $PROJECT_NAME - Build # 137 - $BUILD_STATUS!

      After downgrading to 2.40.5 they are again replaced correctly.

          [JENKINS-34267] Email-ext doesn'r replace all tokens any more

          Alex Earl added a comment -

          Did you also upgrade token-macro?

          Alex Earl added a comment - Did you also upgrade token-macro?

          Yes, it's on the latest version 1.12.1.

          Thorsten Meinl added a comment - Yes, it's on the latest version 1.12.1.

          Alex Earl added a comment -

          Can you share your job configuration? I haven't heard of anyone else with three same issue, so there must be something unique in your setup

          Alex Earl added a comment - Can you share your job configuration? I haven't heard of anyone else with three same issue, so there must be something unique in your setup

          Thorsten Meinl added a comment - - edited

          Jenkins configuration files are attached.
          BTW, if you perform a search on the internet for "$BUILD_STATUS" and "Jenkins" you will find quite a lot of hits that seem to indicate the same or a similar issue.

          Thorsten Meinl added a comment - - edited Jenkins configuration files are attached. BTW, if you perform a search on the internet for "$BUILD_STATUS" and "Jenkins" you will find quite a lot of hits that seem to indicate the same or a similar issue.

          Alex Earl added a comment -

          I didn't see any hits that related to email-ext

          Alex Earl added a comment - I didn't see any hits that related to email-ext

          Alex Earl added a comment -

          I just tried running with a maven project locally and the tokens were replaced correctly. Did you restart Jenkins after upgrading email-ext and token-macro?

          Alex Earl added a comment - I just tried running with a maven project locally and the tokens were replaced correctly. Did you restart Jenkins after upgrading email-ext and token-macro?

          Yes, I restarted after the update (Jenkins does this automatically). If you given me some pointers where to start looking, I can give it a try.

          Thorsten Meinl added a comment - Yes, I restarted after the update (Jenkins does this automatically). If you given me some pointers where to start looking, I can give it a try.

          Alex Earl added a comment -

          Are there any errors in the Jenkins logs?

          Alex Earl added a comment - Are there any errors in the Jenkins logs?

          It seems the automatic "restart" that Jenkins performs after updating extensions isn't enough. After I completely restarted the service on the OS level, tokens are again replaced. Sorry for the noise.

          Thorsten Meinl added a comment - It seems the automatic "restart" that Jenkins performs after updating extensions isn't enough. After I completely restarted the service on the OS level, tokens are again replaced. Sorry for the noise.

          Alex Earl added a comment -

          I'm just glad it is working!

          Alex Earl added a comment - I'm just glad it is working!

            slide_o_mix Alex Earl
            sithmein Thorsten Meinl
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: