You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "P. Ottlinger" <po...@apache.org> on 2017/11/14 23:11:00 UTC

Travis integration working from individual project forks

Hi,

Travis integration seems to be working fine :-)
At least the first build went through successfully in contrast to the
current situation on Jenkins ....

Not sure if you guys see the result, but it is GREEN:
https://travis-ci.org/ottlinger/incubator-tamaya

Does anyone know if INFRA can enable Travis access for our root repos?

Cheers + n8
Phil

PS: I had to create a fork in my private Github account in order to
verify the travis integration.

Re: Travis integration working from individual project forks

Posted by "P. Ottlinger" <po...@apache.org>.
Am 15.11.2017 um 08:27 schrieb P. Ottlinger:
> Am 15.11.2017 um 01:25 schrieb Anatole Tresch:
>> Wow, cool!
>>
>> If we add the travis file they should also end up in the Github mirror, I
>> suggest. Does that not work then?
> 
> No, I've added the file to the main incubator-tamaya project,
> but you need a travis account, which is linked to a Github account.
> 
> AS long as we do not have an account that has our apache-repos as base
> it won't work.


I filed
https://issues.apache.org/jira/browse/INFRA-15584
to ask if INFRA can help to integrate with Travis.

Just fyi

Phil


Re: Travis integration working from individual project forks

Posted by "P. Ottlinger" <po...@apache.org>.
Am 15.11.2017 um 01:25 schrieb Anatole Tresch:
> Wow, cool!
> 
> If we add the travis file they should also end up in the Github mirror, I
> suggest. Does that not work then?

No, I've added the file to the main incubator-tamaya project,
but you need a travis account, which is linked to a Github account.

AS long as we do not have an account that has our apache-repos as base
it won't work.

Phil

Re: Travis integration working from individual project forks

Posted by Anatole Tresch <at...@gmail.com>.
Wow, cool!

If we add the travis file they should also end up in the Github mirror, I
suggest. Does that not work then?

2017-11-15 0:11 GMT+01:00 P. Ottlinger <po...@apache.org>:

> Hi,
>
> Travis integration seems to be working fine :-)
> At least the first build went through successfully in contrast to the
> current situation on Jenkins ....
>
> Not sure if you guys see the result, but it is GREEN:
> https://travis-ci.org/ottlinger/incubator-tamaya
>
> Does anyone know if INFRA can enable Travis access for our root repos?
>
> Cheers + n8
> Phil
>
> PS: I had to create a fork in my private Github account in order to
> verify the travis integration.
>



-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> *
*Twitter:  @atsticks, @tamayaconf*

*Speaking at:*

  [image: JSD_Speaker_2017][image: J-Con 2017 logo][image: JVM Con]

Re: Travis integration working from individual project forks

Posted by "P. Ottlinger" <po...@apache.org>.
Am 15.11.2017 um 00:46 schrieb Werner Keil:
> So Travis works while Jenkins builds for the same artifacts keep failing?

I've only integrated the main project incubator-tamaya, since all other
projects have compilation/test failures after the SPI changes.

It was only meant as a prototype ;-)

Cheers,
Phil

Re: Travis integration working from individual project forks

Posted by Werner Keil <we...@gmail.com>.
So Travis works while Jenkins builds for the same artifacts keep failing?

Am 15.11.2017 00:11 schrieb "P. Ottlinger" <po...@apache.org>:

> Hi,
>
> Travis integration seems to be working fine :-)
> At least the first build went through successfully in contrast to the
> current situation on Jenkins ....
>
> Not sure if you guys see the result, but it is GREEN:
> https://travis-ci.org/ottlinger/incubator-tamaya
>
> Does anyone know if INFRA can enable Travis access for our root repos?
>
> Cheers + n8
> Phil
>
> PS: I had to create a fork in my private Github account in order to
> verify the travis integration.
>