[
https://issues.apache.org/jira/browse/YETUS-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590890#comment-16590890
]
Jack Bearden commented on YETUS-640:
------------------------------------
I tested it in two modes: patch and empty patch.
In empty patch mode, every thing works as I would expect: giving me a nice
report at the end of the build.
{code:java}
| Vote | Subsystem | Runtime | Comment
============================================================================
| | | | Prechecks
| | | | Compile Tests
| 0 | mvndep | 0m 25s | Maven dependency ordering
| -1 | hadolint | 0m 00s | The source tree has 36 issues.
{code}
Patch mode works as expected as it picks it up when a Dockerfile is a part of
the patch. While the report still functions and doesn't appear to have much
impact, I do believe we get some kind of race condition during the run:
{code:java}
* hadoop-tools/hadoop-rumen/Dockerfile
hadolint: hadoop-tools/hadoop-rumen/Dockerfile: openBinaryFile: does not exist
(No such file or directory)
{code}
Let's fix that if possible. Great work! +1
> add hadolint (Dockerfile linter) support
> ----------------------------------------
>
> Key: YETUS-640
> URL: https://issues.apache.org/jira/browse/YETUS-640
> Project: Yetus
> Issue Type: New Feature
> Components: Test Patch
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Major
> Fix For: 0.8.0
>
> Attachments: YETUS-640.00.patch, YETUS-640.01.patch,
> YETUS-640.02.patch, YETUS-640.03.patch, YETUS-640.04.patch
>
>
> hadolint is a linter for Dockerfiles.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
