From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] submitted bugreport to upstream nmigen
Date: Sat, 4 Apr 2020 12:07:48 +0100
Message-ID: <CAPweEDxv+vy9J1bioVfGy+muK0xY-S8BkG+BL+=vPvGM=Ba0Mg@mail.gmail.com> (raw)
In-Reply-To: <67ac8a43-5610-b2e4-f648-a0af7d68a09b@paape.io>
On Sat, Apr 4, 2020 at 9:15 AM Frieder Paape <frieder@paape.io> wrote:
>
> There is an api endpoint for jobs
> <https://docs.gitlab.com/ee/api/jobs.html>. We could write a cronjob
> which polls the api every day for new jobs and then saves the logs for
> those jobs locally.
>
> BUT I personaly think instead of investing time into workarounds because
> we don't have gitlab hosted ourselves, we should rather invest time to
> host it ourselves. Why not try to host it on the new talos 2 server.
although it would be a nuisance, we may need to blow it away and do a
full reinstall at the bare metal (hypervisor testing, BE OS instead of
LE OS, and so on).
> Does it have a public IP? We will probably run into problems, but hey,
> we are building a CPU on that architecture, it would look nice if we
> host our development tools on such architecture as well. And if there
> are larger problems we could bring them to IBM, which probably use
> gitlab in high quantity and might have the muscle to ask for a quick
> solution.
hmm it's good thinking: we are however reliant on them.
> Hosting it on a donated x86 server I guess would be fine as well
i pay for the mythic-beasts vCPU (and make sure it's backed up).
l.
_______________________________________________
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
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 [this message]
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='CAPweEDxv+vy9J1bioVfGy+muK0xY-S8BkG+BL+=vPvGM=Ba0Mg@mail.gmail.com' \
--to=lkcl@lkcl.net \
--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