Hi,

I also have (I think) a similar problem.

we use base clearcase, and email-ext doesn't seem to find the emails of the 
users (culprits) who performed check-ins to the scm.

is there a good solution for this? (yes, I know there is git, we don't use 
it yet)

On Thursday, November 10, 2011 at 4:58:41 PM UTC+2, slide wrote:
>
>
>
> On Thu, Nov 10, 2011 at 7:39 AM, Dirk Kuypers <[email protected] 
> <javascript:>> wrote:
>
>> Could it be related to JENKINS-9336?
>>
>> In the first failing build I have the following changes pattern as
>> mentioned in the issue above.
>>
>> Changes for Build #1759
>> [User A] Some text
>> [User B] Some text
>> [User A] Some text
>> [User A] Some text
>> [User A] Some text
>> [User A] Some text
>> [User C] Some text
>> [User A] Some text
>>
>> We are using basic ClearCase and it does not support the concept of
>> commiting several files in one patch set. So it normally occurs in our
>> team that someone edited 10 files and checks those files in one file
>> per minute because the developer has to diff with the previous version
>> to generate a commit message. (That's not my style of work, but a lot
>> of people here are used to working like this for the last 10 years).
>> Dirk
>>
>>
>> 2011/11/10 Slide <[email protected] <javascript:>>:
>> > Not a lot of info there....I'll see what I can do.
>> >
>> > On Nov 10, 2011 7:06 AM, "Dirk Kuypers" <[email protected] 
>> <javascript:>> wrote:
>> >>
>> >> 2.15, me as global default recipient, tick at "Send To Culprits" and
>> >> "Send to Recipients List" and as default recipients of the Still
>> >> failing trigger $PROJECT_DEFAULT_RECIPIENTS
>> >>
>> >> 14:55:12  Time Elapsed 00:01:25.11
>> >> 14:55:12  Build step 'Build a Visual Studio project or solution using
>> >> MSBuild.' marked build as failure
>> >> 14:55:12  [WARNINGS] Skipping publisher since build result is FAILURE
>> >> 14:55:12  Build does not meet criteria for workspace archiving -
>> >> result is not at least UNSTABLE.
>> >> 14:55:12  Archiving artifacts
>> >> 14:55:12  Recording fingerprints
>> >> 14:55:54  Email was triggered for: Failure
>> >> 14:55:54  Email was triggered for: Still Failing
>> >> 14:55:54  Trigger Failure was overridden by another trigger and will
>> >> not send an email.
>> >> 14:55:54  Sending email for trigger: Still Failing
>> >> 14:55:55  Sending email to: [email protected] <javascript:>
>> >> 14:55:55  Notifying upstream projects of job completion
>> >> 14:55:55  Finished: FAILURE
>> >>
>> >> BR
>> >> Dirk
>> >>
>> >> 2011/11/10 Slide <[email protected] <javascript:>>:
>> >> > can you post the end of the build log where the emails are being 
>> sent?
>> >> >
>> >> > On Nov 10, 2011 6:53 AM, "Dirk Kuypers" <[email protected] 
>> <javascript:>>
>> >> > wrote:
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >> > No, in fact 2.16 should not have the default recipients in global
>> >> >> > config
>> >> >> > anymore. It does nothing. Somehow my repo got messed up before I
>> >> >> > issued
>> >> >> > a
>> >> >> > pull request and then when the merge occurred things went terribly
>> >> >> > wrong. I
>> >> >> > am working on fixing it using a clean fork/repo.
>> >> >>
>> >> >> hm, ok. But now I am back to 2.15. And why does it not work anymore
>> >> >> with sending to culprits? Is there a possibility to get a hint via
>> >> >> logs?
>> >> >>
>> >> >> Dirk
>> >> >>
>> >> >> --
>> >> >> Never trust a short-haired guru
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Never trust a short-haired guru
>> >
>>
>>
>>
>> --
>> Never trust a short-haired guru
>>
>
>
> It's quite possible that is the case.
>
> slide
>
> -- 
> slide-o-blog
> http://slide-o-blog.blogspot.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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c116ecc2-4116-46cb-93a8-e6ba20e4899d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to