You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ctakes.apache.org by Andrey Kurdumov <ka...@googlemail.com> on 2017/08/19 14:34:27 UTC
Travis for testing
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
infrastructure could help let other people start faster.
Re: Travis for testing
Posted by jay vyas <ja...@gmail.com>.
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 community.
On Tue, Aug 22, 2017 at 8:31 AM, Andrey Kurdumov <ka...@googlemail.com>
wrote:
> 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 <re...@apache.org>:
>
> > On 20.08.2017, at 10:56, Andrey Kurdumov <ka...@googlemail.com>
> 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
> > > configuration of it.
> > > What sort of bureaucracy hoops should I jump through to be able work on
> > > this :)
> >
> > Here is the Apache Jenkins: https://builds.apache.org
> >
> > Searching for "ctakes", I found two jobs there.
> >
> > Cheers,
> >
> > -- Richard
> >
>
--
jay vyas
Re: Travis for testing
Posted by Andrey Kurdumov <ka...@googlemail.com>.
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 <re...@apache.org>:
> On 20.08.2017, at 10:56, Andrey Kurdumov <ka...@googlemail.com> 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
> > configuration of it.
> > What sort of bureaucracy hoops should I jump through to be able work on
> > this :)
>
> Here is the Apache Jenkins: https://builds.apache.org
>
> Searching for "ctakes", I found two jobs there.
>
> Cheers,
>
> -- Richard
>
Re: Travis for testing
Posted by Richard Eckart de Castilho <re...@apache.org>.
On 20.08.2017, at 10:56, Andrey Kurdumov <ka...@googlemail.com> 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
> configuration of it.
> What sort of bureaucracy hoops should I jump through to be able work on
> this :)
Here is the Apache Jenkins: https://builds.apache.org
Searching for "ctakes", I found two jobs there.
Cheers,
-- Richard
Re: Travis for testing
Posted by Andrey Kurdumov <ka...@googlemail.com>.
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 be able work on
this :)
2017-08-20 11:48 GMT+03:00 Richard Eckart de Castilho <re...@apache.org>:
> On 19.08.2017, at 16:34, Andrey Kurdumov <ka...@googlemail.com> 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
> > infrastructure could help let other people start faster.
>
> The ASF runs a Jenkins server. It includes the necessary plugins to
> build pull requests and to update the build status on GitHub.
>
> Also, the "Embeddable Build Status" plugin is available which
> can provide you with a "badge" that indicates the build status.
>
> Travis offers a great *free* service to the OSS community, in
> particular to smaller projects to help them get started with
> proper development infrastructure. But since the ASF has proper
> development infrastructure run on own resources, there is no
> need to make use of this free service - IMHO we should leave the
> free resources to others who do not have their own build infrastructure.
>
> Cheers,
>
> -- Richard
>
Re: Travis for testing
Posted by Richard Eckart de Castilho <re...@apache.org>.
On 19.08.2017, at 16:34, Andrey Kurdumov <ka...@googlemail.com> 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
> infrastructure could help let other people start faster.
The ASF runs a Jenkins server. It includes the necessary plugins to
build pull requests and to update the build status on GitHub.
Also, the "Embeddable Build Status" plugin is available which
can provide you with a "badge" that indicates the build status.
Travis offers a great *free* service to the OSS community, in
particular to smaller projects to help them get started with
proper development infrastructure. But since the ASF has proper
development infrastructure run on own resources, there is no
need to make use of this free service - IMHO we should leave the
free resources to others who do not have their own build infrastructure.
Cheers,
-- Richard