[
https://issues.apache.org/jira/browse/YUNIKORN-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18007568#comment-18007568
]
Hank Huang commented on YUNIKORN-3035:
--------------------------------------
Hi [~wilfreds] ,
Thanks for the responding, and sharing.
I’d like to ask a couple of clarification questions about this ticket
# In the release repo’s CI workflow, I only see {{check_license}} being
called, but ticket mentions:
{quote}_Enforce the same rules for linting, setting Go versions etc. install
tools_
{quote}I’m not clear *where* this requirement comes from—could you point me to
the design doc or rationale?
# Does YuniKorn use any automated tool to publish Helm charts (e.g.
Chart‑Releaser)?
I don’t see any chart‑release step in the workflow, yet I notice GitHub Pages
updates. How is that being handled?
> Add build tool automation to release repo
> ------------------------------------------
>
> Key: YUNIKORN-3035
> URL: https://issues.apache.org/jira/browse/YUNIKORN-3035
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: release
> Reporter: Wilfred Spiegelenburg
> Assignee: Kaichia Chen
> Priority: Minor
> Labels: newbie
>
> The release repo does not follow the same setup as we do for the other
> repositories.
> It does not contain the go linter or have the option to install tools in an
> automated way. We should introduce a top level Makefile as we have in other
> repos.
> Enforce the same rules for linting, setting go versions etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
