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

E-mail subject contains "Exception while replacing SVN_REVISION"

      E-mail subject contains the following message:

      "base-devel ยป lucid_32 - Build # 969-[[ Exception while replacing SVN_REVISION. Please report this as a bug. ]] {{ java.lang.InterruptedException }} - Successful!"

      Intention was to use environment variable SVN_REVISION in the e-mail subject. In some cases the message above is shown instead of the revision, in all other cases fixed number 400 is shown instead of proper value.

          [JENKINS-8995] E-mail subject contains "Exception while replacing SVN_REVISION"

          Matej Kenda added a comment -

          I have upgraded to 1.403. The problem is still reported occasionally.

          Build # 1032-[[ Exception while replacing SVN_REVISION. Please report this as a bug. ]]
          {{ java.lang.InterruptedException }}

          Matej Kenda added a comment - I have upgraded to 1.403. The problem is still reported occasionally. Build # 1032-[[ Exception while replacing SVN_REVISION. Please report this as a bug. ]] {{ java.lang.InterruptedException }}

          Indra Gunawan added a comment -

          I am getting "400" all the time with SVN_REVISION.
          I also have recently upgraded to version 1.23 of Subversion plug-in to take advantage of SVN polling bug fix.
          The new subversion plugin provides env variables:

          SVN_REVISION
          SVN_REVISION_n
          SVN_REVISION_<n> environment variables, where <n> is a 1-based index matching the locations configured. The URLs are available through similar SVN_URL_<n> environment variables

          SVN_URL_n

          However none of them is being substituted in the email-ext below:

          SVN URL and SVN Revision Number:
          ${SVN_REVISION}
          ${ENV, var="SVN_URL_1"} : ${ENV, var="SVN_REVISION_1"}
          ${ENV, var="SVN_URL_2"} : ${ENV, var="SVN_REVISION_2"}

          I get "400" for SVN_REVISION and blank for the rest. I have multiple modules checked-out from Subversion in the job.
          Environment: Hudson 1.393; Plug-in version 2.10, 2.12, 2.14.

          -Indra

          Indra Gunawan added a comment - I am getting "400" all the time with SVN_REVISION. I also have recently upgraded to version 1.23 of Subversion plug-in to take advantage of SVN polling bug fix. The new subversion plugin provides env variables: SVN_REVISION SVN_REVISION_n SVN_REVISION_<n> environment variables, where <n> is a 1-based index matching the locations configured. The URLs are available through similar SVN_URL_<n> environment variables SVN_URL_n However none of them is being substituted in the email-ext below: SVN URL and SVN Revision Number: ${SVN_REVISION} ${ENV, var="SVN_URL_1"} : ${ENV, var="SVN_REVISION_1"} ${ENV, var="SVN_URL_2"} : ${ENV, var="SVN_REVISION_2"} I get "400" for SVN_REVISION and blank for the rest. I have multiple modules checked-out from Subversion in the job. Environment: Hudson 1.393; Plug-in version 2.10, 2.12, 2.14. -Indra

          Indra Gunawan added a comment -

          Is it possible it is related?

          Indra Gunawan added a comment - Is it possible it is related?

          Alex Earl added a comment -

          Make sure you don't have a space between ENV, and var.

          ${ENV,var="SVN_REVISION"}

          SVN_REVISION is not a direct token in email-ext, you would need it setup as an environment variable. Are you sure they are environment variables that are exported and not part of the token-macro plugin? The email-ext plugin does not currently support the token-macro plugin.

          Alex Earl added a comment - Make sure you don't have a space between ENV, and var. ${ENV,var="SVN_REVISION"} SVN_REVISION is not a direct token in email-ext, you would need it setup as an environment variable. Are you sure they are environment variables that are exported and not part of the token-macro plugin? The email-ext plugin does not currently support the token-macro plugin.

          Alex Earl added a comment -

          I take that back, SVN_REVISION is now a token.

          Alex Earl added a comment - I take that back, SVN_REVISION is now a token.

            Unassigned Unassigned
            matejk Matej Kenda
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: