Thank you Rob, that's exactly the info I need. It's not clear to me when I can expect a public release of the fixed perforce plugin, but at least now I understand specifically what the problem is and see options for how to work around it until there is a new release of the plugin.
-Jim On Sun, Jun 15, 2014 at 10:03 PM, Rob Petti <rob.pe...@gmail.com> wrote: > Email-ext changed the functions used for getting changeset and timestamp > information. Details are here: > https://issues.jenkins-ci.org/browse/JENKINS-11600 > > > On Friday, 13 June 2014 12:29:35 UTC-6, Jim Lloyd wrote: >> >> Hello. I am new to Jenkins and am trying to make configuration changes to >> support the addition of new jobs using Git for SCM. Previously the server >> only had jobs using Perforce for SCM. We were running Jenkins v1.499, which >> was too old to support the Git related plugins we wanted to install, so we >> upgraded to Jenkins v1.565, which was the current release at the time. >> Almost everything is working fine. Previous Perforce jobs and new Git jobs >> are able to run to successful completion. But we have noticed that emails >> now sent from jobs that use Perforce are now missing the changelist number >> and show an invalid date/timestamp. For example: >> >> [null] Dec 31, 1969 3:59:59 PM joedev >> Bug 24409 - ..... >> >> Before the upgrade, the email was formated as: >> >> [70468] 2014-05-30 14:56:00 janedev >> Fix for 24328 - .... >> >> We didn't make any changes to either the global settings for Extended >> E-mail Notification, or for the project specific settings for Editable >> Email Notification. >> >> We're using just "$DEFAULT_CONTENT" in the Editable Email Notification. >> The relevant section in our global settings for Extended E-mail >> Notification contains: >> >> <h4><a href="${BUILD_URL}/changes">Changes:</a></h4> >> ${CHANGES_SINCE_LAST_SUCCESS, reverse=true, showPaths=true, format="%c<br >> />", changesFormat="[%r] %d <strong>%a</strong><br />%m<br />%p", >> pathFormat="%p<br />"} >> >> I have searched to try to understand why ${CHANGES_SINCE_LAST_SUCCESS} >> is now partially broken but have so far not found an answer. Can someone >> help? >> >> Thanks, >> Jim >> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/eZQsgfCSYM4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
