[ 
https://issues.apache.org/jira/browse/JAMES-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17211578#comment-17211578
 ] 

Juhan Aasaru commented on JAMES-3397:
-------------------------------------

I have reached this far and have now been stuck for some time already due to 
tests failing in travis. I wonder if anyone could help me out.

Code changes:
[https://github.com/apache/james-project/compare/master...aasaru:travis-ci]

Build:

[https://travis-ci.com/github/aasaru/james-project/builds/188823725] 

Basically there are two major problems

1. when running this build:

cd $ROOTDIR/mailbox && ../mvnw --no-transfer-progress install

there is an error:


[ERROR] 
RabbitMQEventBusDeadLetterQueueUpgradeTest.eventBusShouldStartWhenDeadLetterUpgradeWasNotPerformed
 » ShutdownSignal

that results with:


[INFO] Apache James :: Mailbox :: Event :: RabbitMQ implementation FAILURE 
[02:43 min]

 

and 2-nd problem:

 

cd server/mailet/integration-testing && ../../../mvnw --no-transfer-progress 
test 

fails with:

[ERROR] Errors: 
[ERROR] RemoteDeliveryErrorTest.remoteDeliveryShouldNotRetryWhenRCPT500:237 » 
Retryable
[ERROR] 
SizeGreaterThanIntegrationTest.mailShouldBeDeliveredWhenSizeWithinLimit:99 » 
ConditionTimeout

 

Test logic.

As you can see I first compile and install jar-s into .m2 directory at phase 1.

Then in second phase I run tests in parallel. I have devided the tests into 
separate *.sh files (and placed them into .travis directory).

Travis fails if the build output is too long so the *.sh files take care of 
this (by logging into separate file and taking a tail of that file in the end 
of the build and only outputing that).


Stability:

I removed -T flag from tests as it seemed to be unstable ocasionally.

Ocasionally some more tests fail.

 

My idea is to only run first phase (compile) for PR-s and the whole build every 
time something is merged to master branch. Of course if we get the whole build 
to be stable then we could run the whole build for each PR.

> Set up travis-ci continuous integration to build the project and all pull 
> requests
> ----------------------------------------------------------------------------------
>
>                 Key: JAMES-3397
>                 URL: https://issues.apache.org/jira/browse/JAMES-3397
>             Project: James Server
>          Issue Type: Improvement
>            Reporter: Juhan Aasaru
>            Priority: Major
>
> continuous integration increases quality and reduces chances that some PR can 
> accidentally break the build
> I would like to work on this.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to