Good that Christopher pointed this out and that you have taken the first
steps.

a

On Tue, Jul 21, 2020 at 7:08 AM Piotr Zarzycki <[email protected]>
wrote:

> Relevant link to archive on builds:
>
> https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E
>
> Jira where I'm asking for creating folder/space for Royale:
> https://issues.apache.org/jira/browse/INFRA-20571
>
> Thanks,
> Piotr
>
> niedz., 19 lip 2020 o 18:54 Christofer Dutz <[email protected]>
> napisał(a):
>
> > I think they are switching to a commercial Jenkins distribution from
> > CloudBees.
> >
> > I think in general managing such a huge CI server like the Apache one
> with
> > the Open-Source version is a challenge.
> > The commercial distributions usually have some bells and whistles that
> > allow managing the CI for large corporates which Apache might benefit
> from.
> >
> > But I'm just guessing, so this might not be true.
> >
> > Chris
> >
> > Am 19.07.20, 15:06 schrieb "Piotr Zarzycki" <[email protected]
> >:
> >
> >     Hi Chris,
> >
> >     Why they are changing that? Do you know the reason?
> >
> >     Do you know Is there any way to just copy settings without manual
> > steps?
> >
> >     Thanks,
> >     Piotr
> >
> >
> >     On Sun, Jul 19, 2020, 2:06 PM Christofer Dutz <
> > [email protected]>
> >     wrote:
> >
> >     > Hi all,
> >     >
> >     > if you haven’t been following [email protected]<mailto:
> > [email protected]>.
> >     >
> >     > It seems that builds.apache.org will be soon replaced by
> >     > ci-builds.apache.org and all jobs have to be re-setup on the new
> CI
> >     > system.
> >     > So I think you should probably start setting up as I think the old
> > CI will
> >     > be turned off somewhere around August 15th.
> >     >
> >     > Chris
> >     >
> >     >
> >     >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Reply via email to