Re: [DISCUSS] Using Travis CI for Artemis PR builds

travis-ci uses GCE, which does not support ipv6 at all https://travis-ci.org/apache/activemq-artemis/builds/342667584#L975 :( 2018-02-17 10:33 GMT+05:00 Илья Шипицин : > Travis seems already performs "mvn install" by itself, we can reduce build > log (it's really huge) >

Re: [DISCUSS] Using Travis CI for Artemis PR builds

Travis seems already performs "mvn install" by itself, we can reduce build log (it's really huge) On Feb 16, 2018 10:46 PM, "Justin Bertram" wrote: > Artemis doesn't yet have AppVeyor integration. > > Perhaps you should open a JIRA or start a separate discussion thread

Re: [DISCUSS] Using Travis CI for Artemis PR builds

Artemis doesn't yet have AppVeyor integration. Perhaps you should open a JIRA or start a separate discussion thread about your JDBC issues. Justin On Fri, Feb 16, 2018 at 11:36 AM, Илья Шипицин wrote: > It turned out that ms SQL jdbc is not being tested (both

Re: [DISCUSS] Using Travis CI for Artemis PR builds

It turned out that ms SQL jdbc is not being tested (both documentation is bad, SQL statements are also broken). Do you accept patches for app veyor as well? On Feb 16, 2018 10:29 PM, "Justin Bertram" wrote: > We're discussing travis-ci.org [1]. > > > Justin > > [1]

Re: [DISCUSS] Using Travis CI for Artemis PR builds

We're discussing travis-ci.org [1]. Justin [1] https://travis-ci.org/apache/activemq-artemis On Fri, Feb 16, 2018 at 11:21 AM, Илья Шипицин wrote: > Sorry for interrupting (joined mailing list to resolve some issues), are > you talking about travis-ci.org or

Re: [DISCUSS] Using Travis CI for Artemis PR builds

Sorry for interrupting (joined mailing list to resolve some issues), are you talking about travis-ci.org or travis-ci.com? On Feb 16, 2018 10:18 PM, "Robbie Gemmell" wrote: > I believe the mirrors in the apache github org have a shared resource > pool at Travis, while

Re: [DISCUSS] Using Travis CI for Artemis PR builds

I believe the mirrors in the apache github org have a shared resource pool at Travis, while jobs for your personal forks run in the global resource pool. Its not unusual for the latter to be quicker off the mark, but even then its usually just seconds of difference. Occasionally there can be a

Re: [DISCUSS] Using Travis CI for Artemis PR builds

I may have spoken too soon. The UI on the Travis website apparently takes awhile to update or got out of sync or something. The PR build looks to be taking around 25 minutes consistently which I think is pretty good. Justin On Thu, Feb 15, 2018 at 3:18 PM, Justin Bertram

Re: [DISCUSS] Using Travis CI for Artemis PR builds

Initial results are not encouraging. I got Apache infrastructure to enable Travis CI builds [1] after which I disabled the current Jenkins-based PR build and sent a PR with the necessary .travis.yml file to trigger a Travis CI build [2]. I had also enabled Travis CI builds on my own GitHub repo

Re: [DISCUSS] Using Travis CI for Artemis PR builds

> It looks like you've got your builds configured to use the same directory for all builds of the Jenkins job, rather than using a different directory for each build (5103, 5104, etc.)... I've looked through the build configuration and couldn't find anything specifically related to this. How

Re: [DISCUSS] Using Travis CI for Artemis PR builds

I'm in no way trying to discourage you guys from evaluating Travis CI. However... There are currently 4 builds that are in a failed state on the history of that job: - https://builds.apache.org/view/A/view/ActiveMQ/job/ActiveMQ-Artemis-PR-Build/5111/consoleFull - Failed due to "Could

Re: [DISCUSS] Using Travis CI for Artemis PR builds

This is great idea! I get so frustrated with these environment issues. +100 Some other advantages I could see we could implement if successful. run a Linux build and a macOS build eg to check bits like kqueue and or other os specific behaviours (aio fallback to nio) look to use appveyor for a

[DISCUSS] Using Travis CI for Artemis PR builds

Over the last several months I've noticed that the Jenkins-based builds used to validate GitHub pull-requests for Artemis are failing at a significant rate for illegitimate reasons (e.g. environmental issues, timing out because they're too slow, etc.) or not being run at all. Even as I type this