[
https://issues.apache.org/jira/browse/JAMES-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17211814#comment-17211814
]
Benoit Tellier commented on JAMES-3397:
---------------------------------------
Hello Juhan,
Unstable tests are a recurring problem over here too. I will have a look at
the tests you points and see if there can be some easy wins.
However, I'm surprised you get along with so much issues. We get a build
success rate of at least 2/3 on our private Jenkins, and last week I ran 3
builds in a raw manually on a private server.
May you share some details about the target infrastructure? (CPU, memory,
virtualized?)
It looks like a good opportunity to enhance build stability...
> 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.
Overall +1 for this intermediate step though just compiling brings little value
overall. We will have to work on stability ;-)
> 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]
