You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mime4j-dev@james.apache.org by "Benoit Tellier (Jira)" <mi...@james.apache.org> on 2021/06/20 02:47:00 UTC

[jira] [Closed] (MIME4J-300) Create an automated build for MIME4J

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

Benoit Tellier closed MIME4J-300.
---------------------------------
    Resolution: Fixed

> Create an automated build for MIME4J
> ------------------------------------
>
>                 Key: MIME4J-300
>                 URL: https://issues.apache.org/jira/browse/MIME4J-300
>             Project: James Mime4j
>          Issue Type: New Feature
>          Components: project
>    Affects Versions: 0.8.4
>            Reporter: Benoit Tellier
>            Priority: Major
>              Labels: buid, ci, jenkins
>             Fix For: master, 0.8.5
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Today committers needs to run test manually before merging contributions as we did not (yet) set up any build for the MIME4J components.
> Also, we do not currently publish snaposhot.
> We should leverage the Apache CI to set up a build for MIME4J in order to address this issue.
> I propose we inspire ourselves from the Apache James JenkinsFile.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)