You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Matt Sicker (Jira)" <ji...@apache.org> on 2022/05/11 23:14:00 UTC

[jira] [Assigned] (LOG4J2-3376) Publish SNAPSHOT artifacts via GitHub Actions

     [ https://issues.apache.org/jira/browse/LOG4J2-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Sicker reassigned LOG4J2-3376:
-----------------------------------

    Assignee: Volkan Yazici

> Publish SNAPSHOT artifacts via GitHub Actions
> ---------------------------------------------
>
>                 Key: LOG4J2-3376
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3376
>             Project: Log4j 2
>          Issue Type: Improvement
>            Reporter: Volkan Yazici
>            Assignee: Volkan Yazici
>            Priority: Major
>
> GitHub Actions have been the preferred CI for a couple of months. It has produced more stable builds compared to Jenkins. As a result, in order to avoid the confusion caused in GitHub PRs due to multiple CIs, Jenkins support has been disabled. Though Jenkins was responsible for publishing SNAPSHOT artifacts. Now somebody needs to figure out how we can publish SNAPSHOT artifacts using GitHub Actions.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)