[libre-riscv-dev] Broken build notification from debian salsa

[libre-riscv-dev] Broken build notification from debian salsa

[Jacob Lifshay]

Checking to see if you saw this Luke:
https://salsa.debian.org/Kazan-team/soc/-/jobs/652909

If you don't have email notifications enabled, you probably should. We
should probably figure out how to get salsa build failures sent to the
mailing list as well, though we'd have to remove the unsubscribe link to
prevent accidental/malicious unsubscription.

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

Re: [libre-riscv-dev] Broken build notification from debian salsa

[Luke Kenneth Casson Leighton]

---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68

On Tue, Apr 7, 2020 at 3:37 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> Checking to see if you saw this Luke:
> https://salsa.debian.org/Kazan-team/soc/-/jobs/652909

no, i don't see anything from that because it's not sent to a public
mailing list / resource.


> If you don't have email notifications enabled, you probably should.

the implications of relying on and reacting to something that's sent
via a *private message* - even one that comes from an automated system
- are that we are "hiding something".

that seriously violates the goals of the project and undermines the
basis of the funding that we receive from NLNet.

although it's fantastic that you've done them, none of the rest of the
team have any idea why those bugs were fixed in the unit tests, except
when reviewing the "final result" - the commit.

this is a huge alarm-bell.


> We
> should probably figure out how to get salsa build failures sent to the
> mailing list as well,

build failures, job runs - everything.

this is important, jacob.

i didn't realise what was going to be involved in the deployment of
CI, otherwise i would have raised it as a proper discussion for
evaluation, long before the time and effort was spent on getting it
set up.

including properly evaluating alternatives, and how to ensure that
everything is archived and transparent.

l.

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

Re: [libre-riscv-dev] Broken build notification from debian salsa

[Immanuel, Yehowshua U]

>  We
> should probably figure out how to get salsa build failures sent to the
> mailing list as well, though we'd have to remove the unsubscribe link to
> prevent accidental/malicious unsubscription.

I think we had talked about creating another mailing list for builds and bugs.
Now might be a good time to set that up.

The three mailing lists discussed were
 - main/dev
 - bugs
 - watercooler

I’ll see if I can find the reference links.

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

Re: [libre-riscv-dev] Broken build notification from debian salsa

[Luke Kenneth Casson Leighton]

On Tue, Apr 7, 2020 at 4:03 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> >  We
> > should probably figure out how to get salsa build failures sent to the
> > mailing list as well, though we'd have to remove the unsubscribe link to
> > prevent accidental/malicious unsubscription.
>
> I think we had talked about creating another mailing list for builds and bugs.
> Now might be a good time to set that up.

https://bugs.libre-soc.org/show_bug.cgi?id=184

best discussed there.

> The three mailing lists discussed were
>  - main/dev
>  - bugs
>  - watercooler

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

Re: [libre-riscv-dev] Broken build notification from debian salsa

[Jacob Lifshay]

On Tue, Apr 7, 2020, 08:00 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> ---
> crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
>
> On Tue, Apr 7, 2020 at 3:37 PM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
> >
> > Checking to see if you saw this Luke:
> > https://salsa.debian.org/Kazan-team/soc/-/jobs/652909
>
> no, i don't see anything from that because it's not sent to a public
> mailing list / resource.
>
>
> > If you don't have email notifications enabled, you probably should.
>
> the implications of relying on and reacting to something that's sent
> via a *private message* - even one that comes from an automated system
> - are that we are "hiding something".
>
> that seriously violates the goals of the project and undermines the
> basis of the funding that we receive from NLNet.
>
> although it's fantastic that you've done them, none of the rest of the
> team have any idea why those bugs were fixed in the unit tests, except
> when reviewing the "final result" - the commit.
>

Actually, everything but the notification email is currently public --
anyone can look at the build log and see the builds corresponding to all
commits. I think anyone can subscribe to the notifications, but I could be
wrong. If we subscribe the mailing list we should figure out how to filter
out the unsubscribe link to avoid people unsubscribing the mailing list
from gitlab.

https://salsa.debian.org/Kazan-team/soc/pipelines

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

Re: [libre-riscv-dev] Broken build notification from debian salsa

[Luke Kenneth Casson Leighton]

On Tue, Apr 7, 2020 at 4:13 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Tue, Apr 7, 2020, 08:00 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:

> Actually, everything but the notification email is currently public --
> anyone can look at the build log and see the builds corresponding to all
> commits. I think anyone can subscribe to the notifications, but I could be
> wrong. If we subscribe the mailing list we should figure out how to filter
> out the unsubscribe link to avoid people unsubscribing the mailing list
> from gitlab.

a separate list can be set up, one that is admin-moderator-only, no
subscribes or unsubscribes permitted.

l.

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

Re: [libre-riscv-dev] Broken build notification from debian salsa

[Luke Kenneth Casson Leighton]

On Tue, Apr 7, 2020 at 4:47 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:

> a separate list can be set up, one that is admin-moderator-only, no
> subscribes or unsubscribes permitted.

hm that wouldn't work, would it... hmm...

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

Re: [libre-riscv-dev] Broken build notification from debian salsa

[Jacob Lifshay]

On Tue, Apr 7, 2020, 08:53 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Tue, Apr 7, 2020 at 4:47 PM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
>
> > a separate list can be set up, one that is admin-moderator-only, no
> > subscribes or unsubscribes permitted.
>
> hm that wouldn't work, would it... hmm...


I'm thinking what will work best is just to build our own system that uses
the gitlab api to monitor builds and send emails CCed to the committer and
to a mailing list. neither are currently supported by gitlab, it currently
sends them all to me since I registered the ssh key for the git mirroring
cron job.

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

Re: [libre-riscv-dev] Broken build notification from debian salsa

[Jacob Lifshay]

On Tue, Apr 7, 2020, 09:00 Jacob Lifshay <programmerjake@gmail.com> wrote:

> On Tue, Apr 7, 2020, 08:53 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>
>> On Tue, Apr 7, 2020 at 4:47 PM Luke Kenneth Casson Leighton
>> <lkcl@lkcl.net> wrote:
>>
>> > a separate list can be set up, one that is admin-moderator-only, no
>> > subscribes or unsubscribes permitted.
>>
>> hm that wouldn't work, would it... hmm...
>
>
> I'm thinking what will work best is just to build our own system that uses
> the gitlab api to monitor builds and send emails CCed to the committer and
> to a mailing list. neither are currently supported by gitlab, it currently
> sends them all to me since I registered the ssh key for the git mirroring
> cron job.
>

for monitoring the soc repo, you can get the required info in json:

curl
https://salsa.debian.org/api/v4/projects/Kazan-team%2Fsoc/pipelines?scope=finished

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

Re: [libre-riscv-dev] Broken build notification from debian salsa

[Luke Kenneth Casson Leighton]

On Tue, Apr 7, 2020 at 5:00 PM Jacob Lifshay <programmerjake@gmail.com> wrote:

> I'm thinking what will work best is just to build our own system that uses
> the gitlab api to monitor builds and send emails CCed to the committer and
> to a mailing list. neither are currently supported by gitlab, it currently
> sends them all to me since I registered the ssh key for the git mirroring
> cron job.

i'd very much like to hand that task over to frieder and alain, so
that we can focus on hardware / software / simulation, if that's ok.

we only have six months left until the oct 2020 deadline.

l.

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

[libre-riscv-dev] GitLab CI Archiver

[Jacob Lifshay]

On Tue, Apr 7, 2020 at 9:53 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> On Tue, Apr 7, 2020 at 5:00 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > I'm thinking what will work best is just to build our own system that uses
> > the gitlab api to monitor builds and send emails CCed to the committer and
> > to a mailing list. neither are currently supported by gitlab, it currently
> > sends them all to me since I registered the ssh key for the git mirroring
> > cron job.
>
> i'd very much like to hand that task over to frieder and alain, so
> that we can focus on hardware / software / simulation, if that's ok.

Sorry, I ended up writing a Rust program that does at least part of
what we need (I thought it might take an hour or two -- it took 10):

https://salsa.debian.org/Kazan-team/gitlab-ci-archiver

There's example output in the demo branch.

Jacob

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

Re: [libre-riscv-dev] GitLab CI Archiver

[Luke Kenneth Casson Leighton]

On Wed, Apr 8, 2020 at 4:42 PM Jacob Lifshay <programmerjake@gmail.com> wrote:

> Sorry, I ended up writing a Rust program that does at least part of
> what we need (I thought it might take an hour or two -- it took 10):

we need to be careful about that: sysadmin tasks are typically done in
bash, using awk, sed, grep, curl and others.

alain will definitely be unable to work on rust programs: he'll be
able to install and use them but it will take him potentially 3-8
months full-time (doing nothing else) to get to the point where he
could _modify_ - take over - anything written in rust, and maintain
it.

l.

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

Re: [libre-riscv-dev] GitLab CI Archiver

[Jacob Lifshay]

On Wed, Apr 8, 2020, 09:16 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Wed, Apr 8, 2020 at 4:42 PM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
>
> > Sorry, I ended up writing a Rust program that does at least part of
> > what we need (I thought it might take an hour or two -- it took 10):
>
> we need to be careful about that: sysadmin tasks are typically done in
> bash, using awk, sed, grep, curl and others.
>
> alain will definitely be unable to work on rust programs: he'll be
> able to install and use them but it will take him potentially 3-8
> months full-time (doing nothing else) to get to the point where he
> could _modify_ - take over - anything written in rust, and maintain
> it.
>

Once the modifications mentioned in the other thread are done, it's highly
likely to not need modification. I split out nearly all the things that are
likely to change into an external toml config file, which should be easy to
modify/understand. It also has full-featured command line help and
autocompletion thanks to the structopt and clap libraries.
I'm not the only one who knows Rust if something goes wrong, and most of
the code is quite simple (though it could just be me that thinks that since
I've been working on Kazan which is *very* complex).

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