That makes me think :

what I would absolutely love to have is a pipeline of performance tests that run against various versions of the server, and various versions of Java...


What would it take to have that, assuming we have the perf tests already existi,g ?


On 21/01/2019 21:53, Pierre Smits wrote:

Jenkins is great. My favourite.

We can even have pipelines that check our current code against latest release 3rd party libraries to ensure that our latest committed changes work not only against specific (identified) versions, but also major and/or minor upgrades.

Best regards,

Pierre Smits

*Apache Trafodion <https://trafodion.apache.org>, Vice President*
*Apache Directory <https://directory.apache.org>, PMC Member*
Apache Incubator <https://incubator.apache.org>, committer
*Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges) since 2008*
Apache Steve <https://steve.apache.org>, committer


On Mon, Jan 21, 2019 at 9:17 PM Stefan Seelmann <m...@stefan-seelmann.de <mailto:m...@stefan-seelmann.de>> wrote:

    On 1/21/19 9:03 PM, Emmanuel Lécharny wrote:
    >> I'd like to create similar pipelines for the other projects,
    then with
    >> more steps (e.g. installer tests etc).
    >
    > FTR, ApacheDS won't build with Java 11 (because of Jaxb not
    being part
    > of the JDK anymore, and I think it's because of ehcahe: another good
    > reason to switch to Caffeine ?)

    Yes, and Studio neither, which is a release blocker for me. But
    Richard
    will fix it :D

Reply via email to