Re: Travis for testing

2017-08-22 Thread jay vyas
Hi everyone, I work at blackduck software and have been lending a hand for our open source scanning tool, co-pilot. We'd like to lend a hand and using travis as an integration/scanning point is a great plugin for us. We can submit patches to leverage copilot soon if there's interest in the CTakes

Re: Travis for testing

2017-08-22 Thread Andrey Kurdumov
Cool, looks like it is already here, just not advertised anywhere in the docs. Thanks 2017-08-21 12:11 GMT+03:00 Richard Eckart de Castilho : > On 20.08.2017, at 10:56, Andrey Kurdumov wrote: > > > > I'm good with Jenkins, just was not aware about it. I never work with it, > > but my impressio

Re: Travis for testing

2017-08-21 Thread Richard Eckart de Castilho
On 20.08.2017, at 10:56, Andrey Kurdumov wrote: > > I'm good with Jenkins, just was not aware about it. I never work with it, > but my impression is that is better suited for automation of infrastructure > tasks > > Does cTakes use Jenkins? If not, I would like to volunteer in the > configuratio

Re: Travis for testing

2017-08-20 Thread Andrey Kurdumov
I'm good with Jenkins, just was not aware about it. I never work with it, but my impression is that is better suited for automation of infrastructure tasks Does cTakes use Jenkins? If not, I would like to volunteer in the configuration of it. What sort of bureaucracy hoops should I jump through to

Re: Travis for testing

2017-08-20 Thread Richard Eckart de Castilho
On 19.08.2017, at 16:34, Andrey Kurdumov wrote: > > Given the fact that cTakes is available over GitHub ( > https://github.com/apache/ctakes) I interested in having configure Travis > to run exiting test suite of cTakes. > > That give clear visibility of the workflow and this investment in the >