https://phabricator.apertis.org/T8169



Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

Ariel D'Alessandro authored 3 years ago and Frederic Danis committed 3 years ago

The Apertis convention for release versions is to use `+` suffix instead
of `~`. Fix this.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

Ryan Gonzalez authored 3 years ago and Andre Moreira Magalhaes committed 3 years ago

https://phabricator.apertis.org/T8592



Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

Detlev Casanova authored 3 years ago and Andre Moreira Magalhaes committed 3 years ago

This commit removes the use of profiles to generate test jobs and add
information about test groups.

It also removes the personal_lava_tests.md page which is covered in
guides/lava-apertis-testing

Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

This adds details on the reference runtimes contents, as well as the
relationship between flatpak-builder and apertis-flatdeb.

https://phabricator.apertis.org/T8169



Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

Add additional steps when updating components from a new Debian release
in order to also create `upstream` branch.

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

Emanuele Aina authored 3 years ago and Ryan Gonzalez committed 3 years ago

Using `master` to refer to the main branch is not accurate:
1. some projects already have transitioned to `main`
2. mainy projects use multiple release-specific branches anyway,
   like `apertis/v2023dev1`, `apertis/v2022`, etc.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Arnaud Ferraris authored 3 years ago and Andre Moreira Magalhaes committed 3 years ago

This will make things a bit more up-to-date and less ambiguous.

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

Ariel D'Alessandro authored 3 years ago and Andre Moreira Magalhaes committed 3 years ago

import-debian-package script now runs all the steps automatatically. The
recently added --push-remote option allows creating and pushing the
imported package to apertis remote gitlab instance.

The following steps are now automatized:
* package folder is created and import process is performed in there.
* remote repo is created if it doesn't exist.
* remote branches and tags are pushed.
* gitlab settings are applied to remote repo.
* CI pipeline is triggered on all downstream branches.

The previously manual steps (performed now by the script) are kept
documented in the import-debian-package repository.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Add step for checking of disk space in release preparation

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

These outline the overall steps

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

FORCE_SKIP_JOB is a very handy feature allowing users to skip certain
jobs in the pipeline

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

This document describes the new Release Branching Automation through the
Gitlab CI Pipeline

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Ryan Gonzalez authored 3 years ago and Frederic Danis committed 3 years ago

This now covers the basics of using the current `ostree-push` version.

https://phabricator.apertis.org/T8173



Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

Instead of using git example, use gbp's

Our own tools, import-debian-package for example, all use
gbp-buildpackage as the intermediary than using git directly.

The other perk of using gbp-buildpackage is that it takes care of
nuances like .gitattributes and upstream debian/ folders.

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Ritesh Raj Sarraf authored 3 years ago and Emanuele Aina committed 3 years ago

This MR covers the use case where the user would be updating a package
directly from the upstream sources.

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Sudarshan CP authored 3 years ago and Andre Moreira Magalhaes committed 3 years ago

Signed-off-by: Sudarshan C P <sudarshan.cp2@in.bosch.com>

Walter Lozano authored 3 years ago and Emanuele Aina committed 3 years ago

As a way to follow some common guidelines while working on license
configuration add additional tips and examples to illustrate how to
proceed on different common scenarios.

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

This updates the current Flatpak distribution document with information
on both the new reference runtimes and creating new, custom runtimes.

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

Add a note about project visibility when creating an empty project.
If the project visibility is not Public, gitlab-rulez will fail
with the below error,

$ ./gitlab-rulez apply rulez.yaml --filter pkg/linuxptp
-----------[ cut here ]------------
found 1 errors
project pkg/linuxptp: settings: save changes -> error: 403: 403 Forbidden

Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

Frederic Danis authored 3 years ago and Walter Lozano committed 3 years ago

To be consistent in the guide, add "$ " in front of shell commands.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>