www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Halperin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-11721) spam from Jenkins
Date Thu, 21 Apr 2016 17:13:25 GMT

    [ https://issues.apache.org/jira/browse/INFRA-11721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252227#comment-15252227

Daniel Halperin commented on INFRA-11721:

Hi [~ipv6guru], [~daniel], [~abayer], [~humbedooh]:

First, [~daniel], I'm sorry that you have been negatively impacted by this problem. Thank
you for reporting the issue yesterday.
    I wish you had given us some time to investigate and respond before you escalated to INFRA
-- you waited less than 12 hours, and as I write this it has still not been 24 hours since
your initial report.
    You are likely to be very sad if you expect a weird issue like this to get resolved that
quickly across time zones by volunteers.

Second, [~ipv6guru]: It is completely unacceptable that you changed the BEAM project's configuration
without looping anyone from the BEAM project in and giving us a chance to respond. Please
revert this change ASAP -- you've dramatically hurting our ability to communicate.

Finally, let's talk about the issue. We did not have time to investigate this in the very
few work hours remaining yesterday after it was filed, but we've been looking into it since
first thing this morning.

>From what I can tell, there must be a bug somewhere in Apache or Jenkins mailer in terms
of how it identified Apache user IDs from commit messages. The pattern seems to be some related
to commits that I author.

If you look at #134 (https://builds.apache.org/job/beam_PostCommit_RunnableOnService_GoogleCloudDataflow/134/changes)
you will see that is indeed attributed to [~daniel]:

Commit 9a3a6d6befd25f2f1aaa75b2bbbd64cf0c1213a5 by daniel
Revert "This closes #178"
This reverts commit 9039949d5f518fed84bc7cf7e08870e023b53951, reversing 
changes made to e9f1b579a4f5a134b3f00ef011af8d83185e8598.
 (commit: 9a3a6d6befd25f2f1aaa75b2bbbd64cf0c1213a5)

However, this is totally bogus.

Specifically, the commit (https://github.com/apache/incubator-beam/commit/9a3a6d6befd25f2f1aaa75b2bbbd64cf0c1213a5.patch)
has the following header and From line:

>From 9a3a6d6befd25f2f1aaa75b2bbbd64cf0c1213a5 Mon Sep 17 00:00:00 2001
From: Daniel Halperin <daniel@halper.in>
Date: Sat, 16 Apr 2016 17:12:49 -0700
Subject: [PATCH] Revert "This closes #178"

You can see that this commit is authored by me ("Daniel Halperin") and from my email "daniel@halper.in".
None of this should be indicating [~daniel]. There is no malicious action on our part to spam
this user. I think there is an actual bug here to be investigated and fixed in the root cause.

Is it possible that Jenkins is somehow ignoring the email domain and assuming that any email
from daniel@XXXXX is from daniel@apache.org and in fact the Apache user [~daniel]?

Summary and Action items:

1. Please revert any changes you've made to our config.
2. In the future, please loop in the BEAM project management into any tickets like this. It's
unacceptable to unilaterally make such a change within 12 hours and without any chance for
us to get involved.
3. There seems to be an actual bug worth investigating.


> spam from Jenkins
> -----------------
>                 Key: INFRA-11721
>                 URL: https://issues.apache.org/jira/browse/INFRA-11721
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Jenkins
>            Reporter: Daniel Pocock
>            Assignee: Gavin
>            Priority: Critical
> Jenkins has started spamming me about a project I am not involved in.  The spamming started
on 17 April 2016.
> If you can't control the emails to stop spam, please disable email from Jenkins.
> Here is an example:
> Return-Path: <jenkins@builds.apache.org>
> Received-SPF: None (no SPF record) identity=mailfrom; client-ip=; helo=mail.apache.org;
envelope-from=jenkins@builds.apache.org; receiver=daniel@pocock.pro 
> Received: from mail.apache.org (hermes.apache.org [])
> 	by mail1.trendhosting.net (Postfix) with SMTP id 787FD1509D
> 	for <daniel@pocock.pro>; Sun, 17 Apr 2016 02:01:27 +0100 (BST)
> Received: (qmail 13774 invoked by uid 99); 17 Apr 2016 01:01:24 -0000
> Received: from crius.apache.org (HELO crius.apache.org) (
>     by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Apr 2016 01:01:24 +0000
> Received: from crius.apache.org (localhost [])
> 	by crius.apache.org (ASF Mail Server at crius.apache.org) with ESMTP id 1036A9C0097;
> 	Sun, 17 Apr 2016 01:01:16 +0000 (UTC)
> Date: Sun, 17 Apr 2016 01:01:16 +0000 (UTC)
> From: Apache Jenkins Server  <jenkins@builds.apache.org>
> To: commits@beam.incubator.apache.org, bchambers@google.com, daniel@pocock.pro, 
> 	davor@google.com, dhalperi@google.com, lcwik@google.com, 
> 	tgroh@google.com
> Message-ID: <913957783.6890.1460854876064.JavaMail.jenkins@crius>
> In-Reply-To: <293699841.6881.1460851670118.JavaMail.jenkins@crius>
> References: <293699841.6881.1460851670118.JavaMail.jenkins@crius>
> Subject: Jenkins build is still unstable:
>  beam_PostCommit_RunnableOnService_GoogleCloudDataflow #134
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 7bit
> X-Instance-Identity: MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkqVKZPv7YyHBB3FvWfV7XQehwe/Ga3aadzSNknt8g382X3uN8A3SOQ+Ixq9HxS+ZlN6XR4TECySmSRy2JN5Rx8svxAD0TjtSF9LuU98dD+LniNDP7Lq6gvRFuJhbMHoS0nuTizDZLsK4X8TW5MyV9w+jFbdoZfRE5O/Mse0fkOeL5uoIS/3Vvu/W+x9QSjDkB7CaU56bPFlQjqqJBl3Cn9r34CkXQZYnLb/NjW4vcpw0+TgMUAPTIVEr5BTPZRshz19g7huwg3zANT5HBIZnzV4hsVY9w4JHkceFdKi/ibNnjPjsFs9pm0HSGJ/RDxjIvSTYT02eH4+m1RAYaj2E9QIDAQAB
> X-Jenkins-Job: beam_PostCommit_RunnableOnService_GoogleCloudDataflow
> X-Jenkins-Result: UNSTABLE
> See <https://builds.apache.org/job/beam_PostCommit_RunnableOnService_GoogleCloudDataflow/changes>

This message was sent by Atlassian JIRA

View raw message