[
https://issues.apache.org/jira/browse/YETUS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006965#comment-15006965
]
Allen Wittenauer commented on YETUS-123:
----------------------------------------
Looks like it is happening on the Jenkins H3 node as well. I'm thinking this
is a recent change in rubocop. :(
I've been debating how well this patch actually fixes YETUS-131. I think the
only way to really improve checking for Docker issues is to suck the
test-patch-docker code into the main body. Then when there are actual docker
issues (esp docker build, where we're gonna see almost all of them), the system
can report back.
The question is: do I take the time now to fix this or should we commit this
(after fixing the rubocop issue) now or should I start work on merging first?
> Various Docker mode fixes: plug-in issues, local patch file problems,
> availability, & Dockerfile re-usability
> -------------------------------------------------------------------------------------------------------------
>
> Key: YETUS-123
> URL: https://issues.apache.org/jira/browse/YETUS-123
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
> Affects Versions: 0.1.0
> Reporter: Sean Busbey
> Assignee: Allen Wittenauer
> Priority: Critical
> Fix For: YETUS-83
>
> Attachments: YETUS-123.00.patch, YETUS-123.01.patch,
> YETUS-123.02.patch, YETUS-123.03.patch, YETUS-123.04.patch
>
>
> I've made three goes at running in docker mode and all fail in a way that
> suggests the set of plugins isn't making it over to the docker invocation.
> since hadoop is working, I guess there's something that presumes a
> personality will be used?
> builds:
> *
> [13|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/13]
> *
> [14|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/14]
> *
> [28|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/28]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
