hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10200) Fix precommit script patch_tested.txt fallback option
Date Fri, 03 Jan 2014 11:07:51 GMT

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

Hudson commented on HADOOP-10200:

SUCCESS: Integrated in ZooKeeper-trunk #2174 (See [https://builds.apache.org/job/ZooKeeper-trunk/2174/])
HADOOP-10200. Fix precommit script patch_tested.txt fallback option. Contributed by Brock
Noland. (todd: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1555008)
* /hadoop/nightly/jenkinsPrecommitAdmin.py

> Fix precommit script patch_tested.txt fallback option
> -----------------------------------------------------
>                 Key: HADOOP-10200
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10200
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Brock Noland
>            Assignee: Brock Noland
>         Attachments: HADOOP-10200.patch
> HADOOP-10199 created a "fallback" option when there is successful artifact. However that
fallback option used the jenkins lastBuild build indicator. It appears that does not mean
the last completed build, but strictly the last build, which in this context is the current
build. The current build is running so it doesn't have any artifacts.

This message was sent by Atlassian JIRA

View raw message