You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Olaf Flebbe <of...@oflebbe.de> on 2017/11/09 20:59:48 UTC

Update repo and CI

Hi Evans,

I have some of the platform adjustments ready to be put into CI .

Can I adjust within CI bigtop-toolchain-trunk and the bigtop trunk docker images ? Or should I wait for the release of 1.2.1 to be completed,
since it may interfere with the 1.2.1 build ?

Best,
Olaf

Re: Update repo and CI

Posted by Evans Ye <ev...@apache.org>.
You're right.
I think we should better start to tag bigtop/puppet images with versions.
For example Puppet 3 might work with 1.2.1 but does not work with 1.3+.

I think you can generate new set of images with trunk keyword for what
you'd like to do.


2017-11-13 4:12 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:

> Hi Evans,
>
> what about the bigtop/puppet:* images ?
>
> Shouldn't we tag them as "trunk" as well (and in future with
> bigtop-release number as well).
> May only affect the provisioner ...
>
> I will not touch docker images now ...
>
> Best
> Olaf
>
>
> > Am 10.11.2017 um 10:57 schrieb Evans Ye <ev...@apache.org>:
> >
> > As long as you're changing trunk specific CI jobs and docker images, then
> > it's fine.
> > All the 1.2.1 related stuff is separated into different jobs and
> different
> > images.
> >
> > If you break something, I should fix it:)
> > So please go ahead and do it.
> >
> >
> > Evans
> >
> >
> > 2017-11-10 4:59 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
> >
> >> Hi Evans,
> >>
> >> I have some of the platform adjustments ready to be put into CI .
> >>
> >> Can I adjust within CI bigtop-toolchain-trunk and the bigtop trunk
> docker
> >> images ? Or should I wait for the release of 1.2.1 to be completed,
> >> since it may interfere with the 1.2.1 build ?
> >>
> >> Best,
> >> Olaf
> >>
>
>

Re: Update repo and CI

Posted by Olaf Flebbe <of...@oflebbe.de>.
Hi Evans,

what about the bigtop/puppet:* images ?

Shouldn't we tag them as "trunk" as well (and in future with bigtop-release number as well).
May only affect the provisioner ...

I will not touch docker images now ...

Best
Olaf


> Am 10.11.2017 um 10:57 schrieb Evans Ye <ev...@apache.org>:
> 
> As long as you're changing trunk specific CI jobs and docker images, then
> it's fine.
> All the 1.2.1 related stuff is separated into different jobs and different
> images.
> 
> If you break something, I should fix it:)
> So please go ahead and do it.
> 
> 
> Evans
> 
> 
> 2017-11-10 4:59 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
> 
>> Hi Evans,
>> 
>> I have some of the platform adjustments ready to be put into CI .
>> 
>> Can I adjust within CI bigtop-toolchain-trunk and the bigtop trunk docker
>> images ? Or should I wait for the release of 1.2.1 to be completed,
>> since it may interfere with the 1.2.1 build ?
>> 
>> Best,
>> Olaf
>>

Re: Update repo and CI

Posted by Evans Ye <ev...@apache.org>.
As long as you're changing trunk specific CI jobs and docker images, then
it's fine.
All the 1.2.1 related stuff is separated into different jobs and different
images.

If you break something, I should fix it:)
So please go ahead and do it.


Evans


2017-11-10 4:59 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:

> Hi Evans,
>
> I have some of the platform adjustments ready to be put into CI .
>
> Can I adjust within CI bigtop-toolchain-trunk and the bigtop trunk docker
> images ? Or should I wait for the release of 1.2.1 to be completed,
> since it may interfere with the 1.2.1 build ?
>
> Best,
> Olaf
>