[
https://issues.apache.org/jira/browse/LOG4J2-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150325#comment-17150325
]
ASF subversion and git services commented on LOG4J2-2764:
---------------------------------------------------------
Commit 762d1636287ab86d344e9690f4dd6215497d9894 in logging-log4j2's branch
refs/heads/master from Volkan Yazıcı
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=762d163 ]
LOG4J2-2764 Implement CI pipeline via GitHub Actions. (#379)
> 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
> Assignee: Volkan Yazici
> Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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)
