回复： [DISCUSS] Service-Center Docker images version numbering

[bismy <bi...@qq.com>]

+1 For daily build, we only test against released server center for java-chassis, e.g. 1.0.0.m2. We can test lastest version or other to check compatibility before release new version or weeks a day.




------------------ 原始邮件 ------------------
发件人: "willem.jiang"<wi...@gmail.com>;
发送时间: 2018年7月19日(星期四) 下午4:34
收件人: "dev"<de...@servicecomb.apache.org>;

主题: Re: [DISCUSS] Service-Center Docker images version numbering



For the system test and integration test, it could be good the
ServiceCenter is stable.
So we may not use the latest version in the Java-Chassis system tests.
If we want to check the service-center compatible, we can start a CI with
some basic test per day.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Jul 17, 2018 at 9:24 PM, Mohammad Asif Siddiqui <
asifdxtreme@apache.org> wrote:

> Hi All,
>
> There was an issue raised in github[1] of service-center regarding the
> images of SC in docker hub for which we need your feedback.
>
> Problem : Currently there are no docker images of service-center which
> reflects the current state of the service-center. We only make docker
> images when we cut new version and also update the "latest" tag at that
> time. If someone(like Java-Chassis and Saga CI) wants to test their changes
> with the latest Service-Center then they have to either wait for a new
> version to be released or make there own docker image which might be
> sometimes difficult.
>
> Solution : For every successful merge to Service-Center the CI will make a
> new docker image and push it to Dockerhub with the "latest" tag. Whenever a
> new version is cut then we will make a new tag with the version number. So
> the Service-Center tags will look like:
> "latest" : Always represents the latest state of the Service-Center in
> github repo.
> "VersionNumer"(like 1.0.0) : This will be created whenever a new version is
> released.
>
> CI's which are using the SC docker hub images can always use the latest tag
> for their test as well as recent versions of the service-center to check
> backward compatibility.
>
> Since Java-Chassis and Saga CI's uses these SC docker images very
> frequently in their test so we want to know the opinion on this from
> maintainers of Java-Chassis and Saga.
>
> [1]
> https://github.com/apache/incubator-servicecomb-service-center/issues/277
>
> Regards
> Asif
>

Re: [DISCUSS] Service-Center Docker images version numbering

[Bin Ma <ma...@gmail.com>]

+1 for Yang Bo' suggestion.
Service Center backend and frontend is better to integrated in one docker
image, so that easy for users get and run complete function anywhere, such
as in Mac OS.


Best Wishes & Regards
-------------------------------
Mabin



bismy <bi...@qq.com> 于2018年7月20日周五 上午11:16写道：

> +1 For daily build, we only test against released server center for
> java-chassis, e.g. 1.0.0.m2. We can test lastest version or other to check
> compatibility before release new version or weeks a day.
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "willem.jiang"<wi...@gmail.com>;
> 发送时间: 2018年7月19日(星期四) 下午4:34
> 收件人: "dev"<de...@servicecomb.apache.org>;
>
> 主题: Re: [DISCUSS] Service-Center Docker images version numbering
>
>
>
> For the system test and integration test, it could be good the
> ServiceCenter is stable.
> So we may not use the latest version in the Java-Chassis system tests.
> If we want to check the service-center compatible, we can start a CI with
> some basic test per day.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Jul 17, 2018 at 9:24 PM, Mohammad Asif Siddiqui <
> asifdxtreme@apache.org> wrote:
>
> > Hi All,
> >
> > There was an issue raised in github[1] of service-center regarding the
> > images of SC in docker hub for which we need your feedback.
> >
> > Problem : Currently there are no docker images of service-center which
> > reflects the current state of the service-center. We only make docker
> > images when we cut new version and also update the "latest" tag at that
> > time. If someone(like Java-Chassis and Saga CI) wants to test their
> changes
> > with the latest Service-Center then they have to either wait for a new
> > version to be released or make there own docker image which might be
> > sometimes difficult.
> >
> > Solution : For every successful merge to Service-Center the CI will make
> a
> > new docker image and push it to Dockerhub with the "latest" tag.
> Whenever a
> > new version is cut then we will make a new tag with the version number.
> So
> > the Service-Center tags will look like:
> > "latest" : Always represents the latest state of the Service-Center in
> > github repo.
> > "VersionNumer"(like 1.0.0) : This will be created whenever a new version
> is
> > released.
> >
> > CI's which are using the SC docker hub images can always use the latest
> tag
> > for their test as well as recent versions of the service-center to check
> > backward compatibility.
> >
> > Since Java-Chassis and Saga CI's uses these SC docker images very
> > frequently in their test so we want to know the opinion on this from
> > maintainers of Java-Chassis and Saga.
> >
> > [1]
> >
> https://github.com/apache/incubator-servicecomb-service-center/issues/277
> >
> > Regards
> > Asif
> >