Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
Date: Mon, 20 Jul 2015 14:01:04 +0000 (UTC)
From: "Andrew Bayer (JIRA)" <jira@apache.org>
To: builds@apache.org
Message-ID: <JIRA.12846272.1437400673000.234328.1437400864537@Atlassian.JIRA>
In-Reply-To: <JIRA.12846272.1437400673000@Atlassian.JIRA>
References: <JIRA.12846272.1437400673000@Atlassian.JIRA>
 <JIRA.12846272.1437400673349@arcas>
Subject: [jira] [Assigned] (BUILDS-99) Working copy in kafka Jenkins PR job
 needs merge
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/BUILDS-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Bayer reassigned BUILDS-99:
----------------------------------

    Assignee: Andrew Bayer

> Working copy in kafka Jenkins PR job needs merge
> ------------------------------------------------
>
>                 Key: BUILDS-99
>                 URL: https://issues.apache.org/jira/browse/BUILDS-99
>             Project: Infra Build Platform
>          Issue Type: Task
>            Reporter: Ismael Juma
>            Assignee: Andrew Bayer
>
> All builds are failing because the working copy has an unresolved conflict. For example:
> https://builds.apache.org/job/kafka-trunk-git-pr/18/
> It would be good to fix the working copy, but even better would be to change the config so that this kind of issue doesn't happen again (if possible).
> It seems like this issue was triggered by this pull request that tries to merge `trunk` into `0.8.1`:
> https://github.com/apache/kafka/pull/42
> Seems like an accidental pull request. We can't close it and the author is unresponsive. Any chance you can close it? Or do I need to file a separate INFRA issue for that?
> Thanks!


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)