Did you upgrade the Perforce plugin at the same time? My guess is something
in the Perforce plugin changed, but that is just a guess. Without more
information on versions of all the plugins you have mentioned, it will be
hard to help out.
slide
On Fri, Jun 13, 2014 at 11:39 AM, Mark Waite <mark.earl.wa...@gmail.com>
wrote:
> I don't have any help to offer for the specific problem you reported.
>
> I have a general question you might consider. Since you stayed on an
> older version that long, I suspect you prefer stability rather than the
> latest set of features. You may want to consider choosing the "long term
> support" release (LTS) instead of the tip of the Jenkins development
> stream. The current long term support release is 1.554.2, so it is not
> dramatically older than the version you chose, but it has been tested more
> deeply than 1.565.
>
> Mark Waite
>
>
> On Fri, Jun 13, 2014 at 12:29 PM, Jim Lloyd <jim.ll...@gmail.com> 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 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.
>>
>
>
>
> --
> Thanks!
> Mark Waite
>
> --
> 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.
>
--
Website: http://earl-of-code.com
--
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.
