[yocto-autobuilder2] Add branch selector for Mathieu

From: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>

As Alexandre is no longer using the autobuilder daily, remove his branch
selector and add mine.

Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
---
 schedulers.py | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

I wonder if we should give this branch a generic, stable name? It
would also help when we need to point to people that, no, their
patches aren't ignored, and are in fact being tested in a staging
branch.

Ideas for the name? 'master-next-next'?

Alex

On Wed, 23 Oct 2024 at 12:03, Mathieu Dubois-Briand via
lists.yoctoproject.org
<mathieu.dubois-briand=bootlin.com@lists.yoctoproject.org> wrote:
>
> From: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
>
> As Alexandre is no longer using the autobuilder daily, remove his branch
> selector and add mine.
>
> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
> ---
>  schedulers.py | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/schedulers.py b/schedulers.py
> index ec3a085ace8a..7bf27f8537dc 100644
> --- a/schedulers.py
> +++ b/schedulers.py
> @@ -44,13 +44,13 @@ branchdefaults = {
>          'branch_meta-openembedded': 'master',
>          'branch_oecore': 'master-next',
>      },
> -    'abelloni-next': {
> +    'mathieu-next': {
>          'repo_poky': 'ssh://git@push.yoctoproject.org/poky-contrib',
> -        'branch_poky': 'abelloni/master-next',
> +        'branch_poky': 'mathieu/master-next',
>          'repo_oecore': 'ssh://git@push.openembedded.org/openembedded-core-contrib',
> -        'branch_oecore': 'abelloni/master-next',
> +        'branch_oecore': 'mathieu/master-next',
>          'repo_bitbake': 'ssh://git@push.openembedded.org/bitbake-contrib',
> -        'branch_bitbake': 'abelloni/master-next',
> +        'branch_bitbake': 'mathieu/master-next',
>      },
>      'mut': {
>          'branch': 'master',
> @@ -454,7 +454,7 @@ def parent_scheduler(target):
>              name="branchselector",
>              default="master",
>              label="Release Shortcut Selector",
> -            choices=["master", "master-next", "abelloni-next", "mut", "styhead", "scarthgap", "nanbield", "mickledore", "langdale", "kirkstone", "honister", "hardknott", "gatesgarth", "dunfell", "zeus", "warrior", "thud", "sumo", "rocko", "pyro", "morty"],
> +            choices=["master", "master-next", "mathieu-next", "mut", "styhead", "scarthgap", "nanbield", "mickledore", "langdale", "kirkstone", "honister", "hardknott", "gatesgarth", "dunfell", "zeus", "warrior", "thud", "sumo", "rocko", "pyro", "morty"],
>              selectors=branchdefaults),
>          util.BooleanParameter(
>              name="swat_monitor",
> --
> 2.39.5
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#730): https://lists.yoctoproject.org/g/yocto-patches/message/730
> Mute This Topic: https://lists.yoctoproject.org/mt/109167694/1686489
> Group Owner: yocto-patches+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto-patches/leave/13197349/1686489/315264618/xyzzy [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

On Wed, 2024-10-23 at 12:08 +0200, Alexander Kanavin via lists.yoctoproject.org wrote:
> I wonder if we should give this branch a generic, stable name? It
> would also help when we need to point to people that, no, their
> patches aren't ignored, and are in fact being tested in a staging
> branch.
> 
> Ideas for the name? 'master-next-next'?

master-next-under-testing
master-next-ab-testing

?

We should probably move from the contrib repos into the main repo at the same time?

If Ross were doing it would this be:

master-next-ab-testing-ross

?

There is probably only a small number of people doing this. I'll
probably merge the branch selector change since it just helps people
run builds but we should resolve the bigger question.

Cheers,

Richard