Introducing KDE Activity Filter

[Ben Cooksley]

On Tue, Jul 14, 2020 at 8:21 PM Kåre Särs <kare.sars at mailbox.org> wrote:
>
> On söndag 12 juli 2020 kl. 20:48:29 EEST Ben Cooksley wrote:
>
> > On Mon, Jul 13, 2020 at 4:46 AM Albert Astals Cid <aacid at kde.org> wrote:
>
> > > El diumenge, 12 de juliol de 2020, a les 8:08:11 CEST, Ben Cooksley va escriure:
>
> > > > Hi all,
>
> > > >
>
> > > > A few years back Sysadmin had to turn off the old Commit Filter
>
> > > > service due to a number of security issues, with no replacement
>
> > > > available.
>
> > > >
>
> > > > I'm now happy to announce that a replacement service is now available,
>
> > >
>
> > > Very much appreciated! Now i can stop using ifttt :)
>
>
> Very much appreciated! :)
>
>
>
> > >
>
> > > > with the added functionality of also being able to cover activity on
>
> > > > Bugzilla and Gitlab (for Tasks and Merge Requests). It is intended
>
> > > > that Activity Filter will be used to provide Gitlab notifications for
>
> > > > merge requests and tasks to mailing lists, along with CI notifications
>
> > > > if desired (once that is moved to Gitlab)
>
> > > >
>
> > > > The new service is configured through YAML format files in the
>
> > > > sysadmin/activityfilter repository
>
> > > > (https://invent.kde.org/sysadmin/activityfilter), which is open to
>
> > > > developers to commit. Please ensure that you read the README contained
>
> > > > in the repository before doing so.
>
> > > >
>
> > > > Please let us know if you have any questions on the above!
>
> > >
>
> > > Can i do stuff like this?
>
> > >
>
> > > - name: "Commits"
>
> > >
>
> > >   subscribes: "aacid at kde.org"
>
> > >   to: commits
>
> > >
>
> > >   where:
>
> > >     project: 'bla'
>
> > >     project: 'bla1'
>
> > >     project: 'bla2'
>
> > >     project: 'bla3'
>
> > >     project: 'bla4'
>
> > >     project: 'bla5'
>
> > >     project: 'bla6'
>
> > >     project: 'bla7'
>
> > >     project: 'bla8'
>
> > >
>
> > > ?
>
> >
>
> > I'm afraid rules like that aren't supported, however you can specify a
>
> > regex so something like:
>
> >
>
> > where:
>
> >     project: 'foo1|foo2|foo3'
>
> >
>
> > should work fine.
>
> >
>
>
> Is there a way to verify that the yaml file is syntactically correct before pushing the change?

At this time i'm afraid there is nothing to validate the syntax of the
files pushed to the repository.

It will however skip any file that is invalid format wise when
generating the rules for use by procmail.

>
>
> Regards,
>
>   Kåre

Thanks,
Ben

>
>
>
> > > Cheers,
>
> > >
>
> > >   Albert
>
> >
>
> > Cheers,
>
> > Ben
>
> >
>
> > > > Thanks,
>
> > > > Ben Cooksley
>
> > > > KDE Sysadmin
>
>
>