[Koha-devel] Last month before the release

[Jonathan Druart]

David, if you don't know Jenkins and you are part of the QA team, I guess
you are not alone to be lost with our CI structure and it means we have a
big problem. Either motivation, or tools or communication.
I am not answering you now but maybe we need to document a bit better how
it works for the next release, responsibilize people (asking them to fix
what they broke instead of fixing for them) and finally maybe have a live
chat beginning of the cycle with RMaints and QA team to (re) explain how it
works.

Le vendredi 3 novembre 2023, David Cook via Koha-devel <
koha-devel at lists.koha-community.org> a écrit :
> It’s not clear to me though how you look at Jenkins runs. Is it going to
https://dashboard.koha-community.org/ and then clicking on one of the
badges to go to Jenkins like
https://jenkins.koha-community.org/job/Koha_Master_U22/ and then clicking
on “Latest Test Result”?
>
>
>
> David Cook
>
> Senior Software Engineer
>
> Prosentient Systems
>
> Suite 7.03
>
> 6a Glen St
>
> Milsons Point NSW 2061
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Online: 02 8005 0595
>
>
>
> From: Tomas Cohen Arazi <tomascohen at gmail.com>
> Sent: Friday, 3 November 2023 11:25 AM
> To: David Cook <dcook at prosentient.com.au>
> Cc: koha-devel <koha-devel at lists.koha-community.org>
> Subject: Re: [Koha-devel] Last month before the release
>
>
>
> The suggested sequence is:
>
>
>
> 1. You notice your stuff for pushed, yay!
>
> 2. You look at Jenkins runs for the relevant branches (e.g. Koha_Master_*
tasks)
>
> 3. If some test gets broken that day, you try too see if it was you.
Beware sometimes it is not obvious.
>
>
>
> Today there was a failure in the holds API tests, because of a bug that
didn't touch the API, but made the code stricter (?) so the loose tests we
had written had to be tweaked so they didn't trigger a silly error.
>
>
>
> So the devs did right, didn't introduce a bug, but made the tests fail.
But it is all of us, specially those who got patches pushed, who should be
looking after those failures. Team work
>
>
>
> Thanks!
>
>
>
> El jue, 2 nov 2023 21:15, David Cook <dcook at prosentient.com.au> escribió:
>
> What’s the best way to do this?
>
>
>
> I think Jenkins might send emails, but I think my mail server blocked it
ages ago as spam.
>
>
>
> David Cook
>
> Senior Software Engineer
>
> Prosentient Systems
>
> Suite 7.03
>
> 6a Glen St
>
> Milsons Point NSW 2061
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Online: 02 8005 0595
>
>
>
> From: Koha-devel <koha-devel-bounces at lists.koha-community.org> On Behalf
Of Tomas Cohen Arazi via Koha-devel
> Sent: Friday, 3 November 2023 12:31 AM
> To: koha-devel <koha-devel at lists.koha-community.org>
> Subject: [Koha-devel] Last month before the release
>
>
>
> Hi all.
>
>
>
> We are almost done with the release, a couple medium/big things to push
today/tomorrow and then bug fixing.
>
>
>
> I wanted to ask y'all to please view the Jenkins tasks status anytime
after your stuff has been pushed. I know I said this many times, but some
devs clearly break some tests that are trivially fixable and the team needs
you to take care of your breakages.
>
>
>
> I'm doing my best to track things and fix, but you should all be worried
about that.
>
>
>
> --
>
> Tomás Cohen Arazi
>
> Theke Solutions (https://theke.io)
> ✆ +54 9351 3513384
> GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20231103/314eb9c9/attachment.htm>