Re: Move pgAdmin git repo to Github?

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: pgadmin-hackers <pgadmin-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Move pgAdmin git repo to Github?
Date: 2020-05-21 19:26:53
Message-ID: CABUevExLUf6u5Qm6zJLEUYPaOOqtsRL_oHi+O2pEuA9fke0aUg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

On Thu, May 21, 2020 at 1:08 PM Dave Page <dpage(at)pgadmin(dot)org> wrote:

> We see a non-trivial amount of automated build failures caused by git
> timeouts and Varnish cache meditation. This is only likely to get worse as
> we've automated so many different build configurations, and the PostgreSQL
> sysadmin team don't really want to get into the business of large-scale
> repository hosting.
>
> I suggest we move our primary repo to Github. Any objections?
>
>
Don't you already have a mirror there? Can't you just point the tests at
that, regardless of where you keep your primary? (It is distributed after
all)

That said you are of course free to change the primary for whatever reason,
but this one doesn't seem like one.

And AFAIK nobody has actually reported any such issues. But it is certainly
true that a lot of the git serving stuff is terribly slow -- but I was
under the impression that it was mostly gitweb, since thats what people
tend to report issues with...

But again, no actual objections to moving.

//Magnus

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2020-05-22 08:13:04 pgAdmin 4 commit: Test commit
Previous Message Akshay Joshi 2020-05-21 14:15:27 Re: [pgAdmin]: Patch fixing Feature Tests failures on Selenium Grid