You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by "Andrew Bayer (JIRA)" <ji...@apache.org> on 2015/07/20 16:02:04 UTC

[jira] [Commented] (BUILDS-99) Working copy in kafka Jenkins PR job needs merge

    [ https://issues.apache.org/jira/browse/BUILDS-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633631#comment-14633631 ] 

Andrew Bayer commented on BUILDS-99:
------------------------------------

I've wiped out the workspace and set the job up to always do that and force a fresh clone. And I've closed that PR.

> 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)