From: Jacob Lifshay <programmerjake@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] submitted bugreport to upstream nmigen
Date: Fri, 3 Apr 2020 13:21:57 -0700
Message-ID: <CAC2bXD4zCEh-TGckx1dpHEV2N6ARftkV-oseTCjE4NEt-mQwEA@mail.gmail.com> (raw)
In-Reply-To: <CAPweEDyB2Rng3Mm10ymgyz0WwY7EKHGLVgb4FT_1Xm7gOWZNRg@mail.gmail.com>
On Fri, Apr 3, 2020 at 12:24 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> On Fri, Apr 3, 2020 at 7:26 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > We can build it on any other gitlab installation, if all else fails, we can
> > install gitlab on jacob-build-server.
>
> which has ridiculous resources (32 GB RAM for a start). plus, we have
> root access so can do backups etc.
Actually only 20GB ram, I have 2 2GB sticks and 2 8GB sticks of ddr3
because if I have the ram why not use it. :)
If we want to get more ram, we should get ddr4 ram instead since I
also have a Ryzen 2600 and a motherboard for it that I could swap into
jacob-build-server, however I don't have any spare ddr4 ram.
> would you be happy for frieder to install gitlab on it? (the more
> people doing stuff in parallel the better).
Sure, though it doesn't have a public IP address and will be nearly
impossible to access publicly. Also, I won't guarantee that
jacob-build-server will be up and running all the time or that I will
even respond quickly to issues (feel free to ssh in and power it off
if all else fails), so we shouldn't have it be a critical
time-sensitive dependency, such as hosting a website.
We should probably still use debian salsa for building and setup some
kind of log scraper since it is publicly visible, unlike
jacob-build-server.
I was thinking we would just put gitlab on jacob-build-server if
debian salsa is no longer viable.
Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 3:21 Jacob Lifshay
2020-04-01 10:16 ` Luke Kenneth Casson Leighton
2020-04-02 3:03 ` Jacob Lifshay
2020-04-02 9:27 ` Luke Kenneth Casson Leighton
2020-04-02 18:19 ` Immanuel, Yehowshua U
2020-04-03 4:10 ` Jacob Lifshay
2020-04-03 10:37 ` Luke Kenneth Casson Leighton
2020-04-03 17:41 ` Jacob Lifshay
2020-04-03 18:11 ` Luke Kenneth Casson Leighton
2020-04-03 18:26 ` Jacob Lifshay
2020-04-03 19:24 ` Luke Kenneth Casson Leighton
2020-04-03 20:21 ` Jacob Lifshay [this message]
2020-04-03 21:48 ` Luke Kenneth Casson Leighton
2020-04-04 8:15 ` Frieder Paape
2020-04-04 11:07 ` Luke Kenneth Casson Leighton
2020-04-03 20:27 ` Cole Poirier
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=CAC2bXD4zCEh-TGckx1dpHEV2N6ARftkV-oseTCjE4NEt-mQwEA@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