[
https://issues.apache.org/jira/browse/JAMES-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282909#comment-17282909
]
Benoit Tellier commented on JAMES-3500:
---------------------------------------
https://github.com/apache/james-project/pull/289 Fasten build by dropping
irrelevant server/protocols/jmap-draft-integration-testing/cassandra
integration tests
According to
https://builds.apache.org/blue/organizations/jenkins/james%2FApacheJames/detail/PR-264/58/pipeline/83
we gain 33:48 min + 34:07 min allowing the Apache build to get down 6h.
These tests are redundant with
`server/protocols/jmap-draft-integration-testing/rabbitmq-jmap-draft-integration-testing`
Furthermore (even if it *might* be considered irrelevant by some) I do consider
the Cassandra + ES without a distributed messaging technology irrelevant as it
do not address the scalability / high availability promise, hence running
expensive integration tests for this combination seems like a non sense to me.
As a proof, webadmin integration tests and JMAP RFC-8621 integration tests are
not run against this app. Doing the same for soon-to-be-deprecated JMAP draft
would make sense to me.
> Fasten the build
> ----------------
>
> Key: JAMES-3500
> URL: https://issues.apache.org/jira/browse/JAMES-3500
> Project: James Server
> Issue Type: Improvement
> Components: Build System
> Reporter: Benoit Tellier
> Priority: Major
>
> On master, stable tests takes 5h16 and unstable tests takes 1h51
> Deploy (whatever it means took 1h05)
> Total, this took 8h+
> I can not be productive while waiting a full work-day for a build result, and
> I believe I am not the only one in that case.
> I would like to help reduce the total build time down to (say) 3 hours.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
