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

[jira] [Closed] (JSIEVE-117) Create an automated build for JSIEVE

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

Benoit Tellier closed JSIEVE-117.
---------------------------------
    Resolution: Fixed

Done. See https://ci-builds.apache.org/job/james/job/Apache-James-JSIEVE/

> Create an automated build for JSIEVE
> ------------------------------------
>
>                 Key: JSIEVE-117
>                 URL: https://issues.apache.org/jira/browse/JSIEVE-117
>             Project: James jSieve
>          Issue Type: New Feature
>          Components: JSieve (Main)
>            Reporter: Benoit Tellier
>            Priority: Major
>             Fix For: master
>
>          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 JSIEVE 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)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org