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] gitlab-ci-archiver status
Date: Thu, 9 Apr 2020 21:24:35 +0100
Message-ID: <CAPweEDwnXBeRzMMJmcuZAsR1hOec=Xx6kvmsuYasO_sDYr82Gw@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD6Ui4j9PiWkc1ofn_xek+HmsM0qr8VvrRah885Dp3gKPA@mail.gmail.com>
On Thu, Apr 9, 2020 at 9:03 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> > ahh, fantastic.
> >
> > is that in a position to hand over to frieder or alain?
> >
>
> Currently it needs modification to respond properly to adding a new build
> to an existing pipeline (if someone clicks rebuild), it currently ignores
> all pipelines already committed to the archive git repo. I'd estimate maybe
> an hour of work by an experienced Rust programmer is needed.
ok time's been committed, might as well finish it.
> It also needs code to send out the build failure emails, or that could be
> done by a shell script by parsing all the new commits -- so an hour of work
> in either bash or Rust
the general UNIX philosohpy is that one program do one task and do it
well. therefore farm that task to an external program.
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: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 19:21 [libre-riscv-dev] more build failures Jacob Lifshay
2020-04-09 19:31 ` Luke Kenneth Casson Leighton
2020-04-09 20:03 ` [libre-riscv-dev] gitlab-ci-archiver status Jacob Lifshay
2020-04-09 20:24 ` Luke Kenneth Casson Leighton [this message]
2020-04-09 20:31 ` Jacob Lifshay
2020-04-09 21:48 ` Luke Kenneth Casson Leighton
2020-04-09 21:54 ` Jacob Lifshay
2020-04-09 23:19 ` Luke Kenneth Casson Leighton
2020-04-10 1:56 ` Luke Kenneth Casson Leighton
2020-04-10 2:27 ` Jacob Lifshay
2020-04-10 12:08 ` Luke Kenneth Casson Leighton
2020-04-10 17:15 ` Jacob Lifshay
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='CAPweEDwnXBeRzMMJmcuZAsR1hOec=Xx6kvmsuYasO_sDYr82Gw@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