Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Let the job "branch-update-tests-projects" run during stage
"branch" like other branching jobs.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Apertis CI <devel@lists.apertis.org>

At this point, even if NEXT_RELEASE is a stable release, it hasn't yet
been released. So, the latest stable version released is currently PREV_STABLE_RELEASE.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

To clarify that the user doesn't have to run commands himself on OBS.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

branch-obs: split the creation of OBS repos for -security, -updates and -backports in two steps due to OBS constraints

OBS refuses to create repo with nonexistent dependencies and because
we have circular dependencies between target and development,
we first need to create repo without dependencies and later re-add
dependencies.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Walter Lozano authored 5 months ago and Dylan Aïssi committed 4 months ago

Stable releases are special as the the name is very similar to the preview
one. To properly check if the repo was already branched the check should
be done using full words and not only parts, if not the match will always
be true.

As a real example, when branching v2025 from v2025pre the check for v2025
will true as if not using full words.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

apt-create-repos: clarify message which is confusing since now this job is triggered before creating OBS repos

Since 5edfb3dc



apt repositories are created before OBS repositories.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

branch-protection-tighten aims to protect branches that were unprotected
during branch-protection-relax. Howerver in dry mode, branch-protection-relax
doesn't unprotect branches on purpose. Thus, branch-protection-tighten
won't report that it will protect branches because they are already
protected due to dry mode. So, we cannot check during the dry mode that
branch-protection-tighten will reprotect branches.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

This is the default value.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

This repo is not used since apertis/v2021

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Otherwise this variable is undefined but used later, thus the script
fails with:

./release-scripts/branch-obs: line 82: [: -ne: unary operator expected

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Dylan Aïssi authored 5 months ago and Walter Lozano committed 4 months ago

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

This list contains repositories whose default branch is "master".

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Due to the issues with using + in the name of packages, like with gtk+2.0,
Apertis decided to replace + by - in several cases, which can be used as
default.

The current code took the approach of escaping the +, but that is not really
needed for the folding/branching process which rely on package names.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

The dashboard is quite important to monitor packages health, so having
the dashboard not up-to-date because of failure is to be avoided.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Walter Lozano authored 5 months ago and Dylan Aïssi committed 5 months ago

The periodic checks are useful, as a single point of notification about
for failures, however, the current configuration checks for every repo
in the infrastructure namespace. By doing this, it spot known issues
with low priority, which could lead to confusions and miss important
reports.

Change the configuration to focus in the important repos.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

By default gitlab-rulez defines the default branch based on the
value of current_release_branch which is currently "apertis/v2025pre".

But some packages have been dropped from Apertis in previous releases,
that means they don't have the default branch. Thus we need to teach
gitlab-rulez what is the latest branch to use as default branch.

nano was in the v2023_repositories
list since its default branch was apertis/v2023 because it got
removed after. Now that it has been re-added in apertis/v2025pre,
gitlab-rulez can rely on the current_release_branch to define its
default branch.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

To have a single place where to check if infrastructure pipelines are green
add a new functionality based on the gitlab-check script.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

By default gitlab-rulez defines the default branch based on the
value of current_release_branch which is currently "apertis/v2025pre".

But some packages have been dropped from Apertis in previous releases,
that means they don't have the default branch. Thus we need to teach
gitlab-rulez what is the latest branch to use as default branch.

pysvn and rpcbind were in the v2023_repositories
list since its default branch was apertis/v2023 because it got
removed after. Now that it has been re-added in apertis/v2025pre,
gitlab-rulez can rely on the current_release_branch to define its
default branch.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

tests/sanity doesn't have any CI, so using the CI default config
for it, makes the merge button disabled.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

The default branch of infrastructure/httpbin is master.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

By default gitlab-rulez defines the default branch based on the
value of current_release_branch which is currently "apertis/v2025pre".

But some packages have been dropped from Apertis in previous releases,
that means they don't have the default branch. Thus we need to teach
gitlab-rulez what is the latest branch to use as default branch.

jitterentropy-rngd and libsocketcan were in the v2023_repositories
list since its default branch was apertis/v2023 because it got
removed after. Now that it has been re-added in apertis/v2025pre,
gitlab-rulez can rely on the current_release_branch to define its
default branch.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Add missing steps to the branching pipeline to keep track of the overall
process.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Fix the code to update infrastructure repo to match expectations.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored 6 months ago and Dylan Aïssi committed 6 months ago

To make the code more readable and easier to reuse simplify the
check-pipelines by using gitlab-check arguments.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored 6 months ago and Dylan Aïssi committed 6 months ago

The current gitlab-check configuration is only used after branching so
rename it accordingly.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored 6 months ago and Dylan Aïssi committed 6 months ago

To improve readability define verbosity levels.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored 6 months ago and Dylan Aïssi committed 6 months ago

To only print relevant information by default add a debug option.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored 7 months ago and Dylan Aïssi committed 6 months ago

In order to improve consistncy and to make the code easier to read move
variables which set the behavior of the code to be in the object. While
doing this rework how config file is handled to avoid changing the values
in memory.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored 7 months ago and Dylan Aïssi committed 6 months ago

The functionality of expaning project was implemented as a stand alone
function, but there is no real benefit on doing that. Instead, move
this functionality to the class to make it easier to share data.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored 7 months ago and Dylan Aïssi committed 6 months ago

The variable projet seems to be spelled in French rather than English.
Unfortunately both spellings are very similiar, causing a typo.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Walter Lozano authored 7 months ago and Dylan Aïssi committed 6 months ago

Removing the protection on the repos can be risky, for this reason
re-enable it as soon as possible, right after projects have been
updated.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored 7 months ago and Dylan Aïssi committed 6 months ago

Following the same approach done for other repos update gitlab-rulez.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>