Skip to content
Snippets Groups Projects
Select Git revision
  • 20a3567cfef6688e962676c7c6ff48b6184aeaa3
  • apertis/v2027dev0 default protected
  • wip/aferraris/git-remote-arg
  • pristine-lfs-source
  • apertis/v2026pre protected
  • apertis/v2026dev1 protected
  • apertis/v2026dev2 protected
  • apertis/v2026dev3 protected
  • proposed-copyright-updates/16703947
  • wip/daissi/python3.13-bis
  • apertis/v2025 protected
  • apertis/v2024 protected
  • wip/daissi/create-mr-against-right-project
  • apertis/v2025pre protected
  • apertis/v2026dev0 protected
  • wip/obsolete_pkg_update
  • apertis/v2025dev3 protected
  • apertis/v2025dev2 protected
  • apertis/v2025dev1 protected
  • apertis/v2024pre protected
  • apertis/v2025dev0 protected
  • apertis/0.2026.5
  • apertis/0.2026.4
  • apertis/0.2026.3
  • apertis/0.2026.2
  • apertis/0.2026.1
  • apertis/0.2026.0
  • apertis/0.2024.19
  • apertis/0.2024.18
  • apertis/0.2024.17
  • apertis/0.2024.16
  • apertis/0.2024.4.2
  • apertis/0.2024.15
  • apertis/0.2024.14
  • apertis/0.2024.13
  • apertis/0.2024.4.1
  • apertis/0.2024.11
  • apertis/0.2024.10
  • apertis/0.2024.9
  • apertis/0.2024.8
  • apertis/0.2024.7
41 results

apertis-dev-tools

Apertis Development Environment

Apertis Development Environment (ADE) is a tool that helps developpers to manage sysroots, cross-compile applications, deploy them to target and then debug them.

See the man page for more details about the available commands and subcommands.

import-debian-package

import-debian-package script imports a package from Debian in the format expected by the Apertis CI system.

To import a new package from Debian the previous process required several manual steps which are now performed automatically by the script using the --push-remote option.

The following steps are now automatized:

  • package folder is created and import process is performed in there.
  • target debian package is fetched and imported.
  • remote repo is created if it doesn't exist.
    • Create an empty project on GitLab under the pkg namespace (for instance, pkg/hello). Choose visibility level Public when creating the project.
    • Configure the origin remote on your local git:
$ git remote add origin git@gitlab.apertis.org:pkg/hello
  • remote branches and tags are pushed.
$ git push --all --follow-tags origin
  • gitlab settings are applied to remote repo using gitlab-rulez:
    • sets the CI config path to ci-package-builder.yml@infrastructure/ci-package-builder
    • changes the merge request settings to:
      • only allow fast-forward merges
      • ensure merges are only allowed if pipelines succeed
    • marks the apertis/* and debian/* branches as protected
$ gitlab-rulez apply ../apertis-infrastructure/gitlab-scripts/rulez.yaml --filter pkg/hello
  • CI pipeline is triggered on all downstream branches.