[
https://issues.apache.org/jira/browse/YETUS-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195558#comment-17195558
]
Allen Wittenauer commented on YETUS-990:
----------------------------------------
Some thoughts/questions/comments:
a) The default ENTRYPOINT should almost certainly be firing off test-patch.
b) Need to make sure we still allow running other stuff if provided on the CLI.
c) Need to make sure we don't break Jenkins and other systems that run commands
inside the image as the operating environment. (Functionally, I'm particularly
worried about this one)
d) How does --plugins work? Just default to all? That sort of goes against the
ASF rules but on the flip side, if one is using the container, they are likely
OK with running category X bits anyway...?
e) Or do we start categorizing each plug-in and default to just non-cat-X ones?
f) We almost certainly need to figure this situation out to enable a GitHub
Action.
> ENTRYPOINT for apache/yetus:(tag) container images
> --------------------------------------------------
>
> Key: YETUS-990
> URL: https://issues.apache.org/jira/browse/YETUS-990
> Project: Yetus
> Issue Type: New Feature
> Components: build
> Affects Versions: 0.13.0
> Reporter: Allen Wittenauer
> Priority: Major
>
> Currently, the apache/yetus:(foo) images are built without an ENTRYPOINT.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
