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

"Editable Email Notification" does not resolve $MVN_RELEASE_VERSION

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      We have configured

       <defaultSubject>A: Request Deployment in SBM: $MVN_RELEASE_VERSION ($DEFAULT_SUBJECT)</defaultSubject>
      

      and before Jenkins 1.651.3 that resolved to the version number we specified in "Release" but now it just shows:

      A: Request Deployment in SBM: $MVN_RELEASE_VERSION (buyos-2016.6 - Build # 18 - Fixed!)
      

      This probably is caused by SECURITY-170

        Attachments

          Issue Links

            Activity

            sc_rsc Stefan Cordes created issue -
            sc_rsc Stefan Cordes made changes -
            Field Original Value New Value
            Summary "Delete Editable Email Notification" does not resolve $MVN_RELEASE_VERSION "Editable Email Notification" does not resolve $MVN_RELEASE_VERSION
            Hide
            sc_rsc Stefan Cordes added a comment -

            Workaround should be

            add `-Dhudson.model.ParametersAction.safeParameters=MVN_RELEASE_VERSION,MVN_DEV_VERSION,MVN_ISDRYRUN` to the variable `JENKINS_JAVA_OPTIONS` in config file /etc/sysconfig/jenkins

            (see https://groups.google.com/forum/#!topic/jenkinsci-users/O2ccSWhKhpY )

            Show
            sc_rsc Stefan Cordes added a comment - Workaround should be add `-Dhudson.model.ParametersAction.safeParameters=MVN_RELEASE_VERSION,MVN_DEV_VERSION,MVN_ISDRYRUN` to the variable `JENKINS_JAVA_OPTIONS` in config file /etc/sysconfig/jenkins (see https://groups.google.com/forum/#!topic/jenkinsci-users/O2ccSWhKhpY )
            Hide
            davidvanlaatum David van Laatum added a comment -

            I haven't looked at the security issue in detail but kinda sounds like the problem is on the sending end ie the m2 release plugin needs to whitelist it

            Show
            davidvanlaatum David van Laatum added a comment - I haven't looked at the security issue in detail but kinda sounds like the problem is on the sending end ie the m2 release plugin needs to whitelist it
            davidvanlaatum David van Laatum made changes -
            Component/s m2release-plugin [ 15621 ]
            davidvanlaatum David van Laatum made changes -
            Component/s email-ext-plugin [ 15538 ]
            davidvanlaatum David van Laatum made changes -
            Assignee David van Laatum [ davidvanlaatum ] James Nord [ teilo ]
            davidvanlaatum David van Laatum made changes -
            Component/s email-ext-plugin [ 15538 ]
            teilo James Nord made changes -
            Link This issue duplicates JENKINS-35261 [ JENKINS-35261 ]
            teilo James Nord made changes -
            Resolution Duplicate [ 3 ]
            Status Open [ 1 ] Closed [ 6 ]
            Hide
            sc_rsc Stefan Cordes added a comment -

            Duplicate is ok.

            Hopefully DEFAULT_RELEASE_VERSION_ENVVAR
            is added to safeParams as well in JENKINS-35261
            ( https://github.com/jenkinsci/m2release-plugin/pull/29/commits/9ae40671030ac7ffa495cea1208ff62be71a4bd9 )

            Show
            sc_rsc Stefan Cordes added a comment - Duplicate is ok. Hopefully DEFAULT_RELEASE_VERSION_ENVVAR is added to safeParams as well in JENKINS-35261 ( https://github.com/jenkinsci/m2release-plugin/pull/29/commits/9ae40671030ac7ffa495cea1208ff62be71a4bd9 )
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 173042 ] JNJira + In-Review [ 210187 ]
            teilo James Nord made changes -
            Assignee James Nord [ teilo ]

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              sc_rsc Stefan Cordes
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: