[bv-dev] CI for API, TCK..

[Gunnar Morling]

Hi,

Thanks for making this proposal!

As Guillaume is saying, we have CI jobs for all the BV/HV artifacts on
CloudBees already (some other related things such as the website build are
on the main Hibernate CI server).

So I don't think we'll gain very much by adding the Travis configuration.
But if would actually be helpful to you, e.g. in order to more easily have
CI for your own forks, then I don't mind having the config added. Glad to
accept a PR if you feel like giving it a shot.

Cheers,

--Gunnar




2016-08-19 14:23 GMT+02:00 Guillaume Smet <guillaume.smet at gmail.com>:

> Hi Hendrik,
>
> At the moment, the official CI for BV and Hibernate Validator is on
> Cloudbees: https://hibernate-validator.ci.cloudbees.com/ .
>
> I did the work to add a .travis.yml for Validator a while ago so that we
> can have CI for our own forks.
>
> Not sure it's worth it for every repository but it might be worth the work
> for some.
>
> Gunnar, thoughts?
>
>
> On Fri, Aug 19, 2016 at 1:10 PM, Hendrik Ebbers <hendrik.ebbers at me.com>
> wrote:
>
>> Hi,
>>
>> should we use Travis (https://travis-ci.org) for CI of all the repos? I
>> can provide a PR that contains the configuration.
>>
>> Cheers,
>>
>> Hendrik
>> _______________________________________________
>> beanvalidation-dev mailing list
>> beanvalidation-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>>
>
>
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/beanvalidation-dev/attachments/20160819/1341dafc/attachment.html