Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Jacob Lifshay <programmerjake@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] sorry state of ieee754fpu repo -- CI desperately needed
Date: Sun, 5 Apr 2020 17:59:15 -0700
Message-ID: <CAC2bXD6nw7pgNFug9yNiZ3uzGykPKe-Xq+4_+TOe_OKR6oOJvQ@mail.gmail.com> (raw)
In-Reply-To: <CAPweEDxdGWzGyz-GKvjqNUn8Pmh7W4GdZtVHsJr_vhBOmY6ptw@mail.gmail.com>

On Fri, Apr 3, 2020 at 4:10 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> On Fri, Apr 3, 2020 at 11:52 AM Frieder Paape <frieder@paape.io> wrote:
> >
> > Alright, it would finally be a chance for me to get a foot in the door
> > since gitlabs CI is something I know about and fixing tests will lead to
> > me getting an idea what the code is about.
>
> ok great.
>
> jacob you good with that?
>
> and with frieder helping on the backend server? (will need your ssh
> pubkey, frieder)

Sure, sounds good. A warning: gitlab-runner thinks it can use all the
free disk space, so you may want to figure out how to reconfigure it
to not use all the space.

I put some manual git syncing code in /home/git-mirroring so you can
add the new gitlab instance as an additional target repo.

Instructions on https://libre-riscv.org/resources/server-setup/git-mirroring/

Do note that I configured iptables to specifically block all local
addresses from docker, so if you try to run gitlab inside a docker
container it will probably not work.

> we can, say, use... EUR 500 from the Purism budget, and see how it goes?
>
> one top priority thing, working out how we can archive copies of all
> messages generated by CI
>
> and in particular, recover the ones already generated, even if it
> means writing a web scraper.

Should be relatively easy to use gitlab's API.

> we absolutely cannot rely on salsa as an uncontrolled resource.  we
> are guests on that machine and should in no way rely on that hosting
> to continue to be provided (and no i am not running gitlab on the 1GB
> memory allocation vCPU behind libreriscv!)

Luke, do note that we are currently relying on the combination of
github and debian salsa to host Kazan's source code, so if they both
kick us out, we'd have to move all the source. We could probably add
some more mirrors using the above git-mirroring script since due to
your selection of port 922 instead of port 22 for ssh, gitlab doesn't
support push mirroring to libre-riscv.org.

Jacob

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

  reply index

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03  7:04 Jacob Lifshay
2020-04-03 10:24 ` Luke Kenneth Casson Leighton
2020-04-03 10:28   ` N.A.
2020-04-03 10:29   ` Frieder Paape
2020-04-03 10:48     ` Luke Kenneth Casson Leighton
2020-04-03 10:52       ` N.A.
2020-04-03 10:52       ` Frieder Paape
2020-04-03 11:09         ` Luke Kenneth Casson Leighton
2020-04-06  0:59           ` Jacob Lifshay [this message]
2020-04-06  1:06             ` Jacob Lifshay
2020-04-06 10:38               ` Luke Kenneth Casson Leighton
2020-04-06 10:39             ` Luke Kenneth Casson Leighton
2020-04-11 15:55             ` Frieder Paape
2020-04-11 16:10               ` Luke Kenneth Casson Leighton
2020-04-12  3:46               ` Jacob Lifshay
2020-04-12  5:44                 ` Luke Kenneth Casson Leighton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAC2bXD6nw7pgNFug9yNiZ3uzGykPKe-Xq+4_+TOe_OKR6oOJvQ@mail.gmail.com \
    --to=programmerjake@gmail.com \
    --cc=libre-riscv-dev@lists.libre-riscv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git