On 01/06/2014 05:48 PM, Arun Neelicattu wrote:
----- Original Message -----
> From: "Cole Robinson" <crobinso(a)redhat.com>
> To: "python-bugzilla user/developer list"
<python-bugzilla(a)lists.fedorahosted.org>, "Arun Neelicattu"
> <abn(a)redhat.com>
> Sent: Tuesday, January 7, 2014 1:17:45 AM
> Subject: Re: [python-bugzilla] [PATCH] Add travis-ci configuration.
>
> On 12/19/2013 09:04 AM, Don Zickus wrote:
>> On Wed, Dec 18, 2013 at 05:24:17PM -0500, Arun Neelicattu wrote:
>>> Hi Don,
>>>
>>> The change is anticipating a move to github. Travis CI is a continuous
>>> integration server [1]. A sample build is available to view at [2].
>>>
>>> This change can be ignored if we no longer plan to move to github. Hope
>>> that clarifies things a bit.
>>
>> Ah, that makes sense now. :-) Thanks! I don't know what the plan is for
>> github.
>>
>
> I'll look into moving to github after the next release, which I intend to
> work
> on this month.
>
> anb, is there a way to trigger travis-ci without a github repo, or is this
> config unused until we move to github?
>
AFAIK, travis does not support non-github repos yet. Could not find any mention
in the docs either. So, yes, the config will be unused unless someone has a copy
of the repo on github with the travis-ci service hook enabled.
Thanks. Regardless I decided to just push your patch, and expanded the commit
message a bit. Maybe it will motivate me to do the github migration sooner :)
- Cole