You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Volkan Yazici (Jira)" <ji...@apache.org> on 2020/02/04 13:49:00 UTC
[jira] [Commented] (LOG4J2-2764) Implement CI pipeline via GitHub
Actions
[ https://issues.apache.org/jira/browse/LOG4J2-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029847#comment-17029847 ]
Volkan Yazici commented on LOG4J2-2764:
---------------------------------------
Note that once LOG4J2-2771 is done, this story becomes pretty much straightforward.
> Implement CI pipeline via GitHub Actions
> ----------------------------------------
>
> Key: LOG4J2-2764
> URL: https://issues.apache.org/jira/browse/LOG4J2-2764
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Volkan Yazici
> Priority: Minor
>
> Given Log4j is hosted on GitHub, migrating away from existing CI pipelines (Travis CI and Apache) to GitHub Actions will bring in the following benefits:
> * A central CI
> * CI for each PR/issue/branch
> * A more GitHub-friendly project
> In its current form, [setup-java doesn't support multiple JDKs during build|https://github.com/actions/setup-java/issues/44], though I believe this can be worked around by either submitting a PR to {{setup-java}} or providing a custom Docker image.
> See [the relevant mailing list discussion|http://mail-archives.apache.org/mod_mbox/logging-dev/202001.mbox/%3CCAP7pH7swrLzD424DrNEUUP%2BEqeHse%3DaT2LfLKF99HDRtrYXEbQ%40mail.gmail.com%3E] for further details.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)