Skip to content
Snippets Groups Projects
New look: Off

Staging repositories

    • Closed Imported Issue created by Administrator @root

    Let bpo create staging repositories when pushing to certain pmaports branches (e.g. with _staging_ in the name).

    Example for a v23.06 service pack:

    • we push commits for the service pack to a v23.06_staging_sp1 branch
    • bpo realizes that changes were made to this staging branch
      • if the staging repo does not exist yet:
        • create the staging repository by creating the same structure as currently in the v23.06 repository
        • but instead of copying the packages, have symlinks to the packages in v23.06 (to save space)
      • run the usual job to check for packages that were changes in the pmaports branch vs. what's in the binary repository
      • build packages for the staging branch
      • for each package that was changed, the symlinks get replaced with the new package
      • or in case a package was deleted, the symlink gets removed

    Users need to configure the staging repository in /etc/apk/repositories, and can then get the changes with apk upgrade -a.

    I'm planning to implement this before v23.06 SP1, then we'll have a good way to have service packs tested easily by multiple people.

    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • Administrator assigned to @ollieparanoid · Imported

      assigned to @ollieparanoid

      By Oliver Smith on 2023-05-16T21:13:18

    • Administrator
      Administrator @root · Imported
      Author Owner

      @dylanvanassche suggested to make this implicit, that users switch to a service pack staging branch once and then always get the new service packs.

      I'm currently leaning towards making it explicit though, I'd rather have an explicit call for testing, then people switch to the branch and report whether it works or not. If people set the branch once and forget about it, they will not explicitly post when a service pack works.

      Also this makes it a bit more flexible for us, we can prepare a staging branch, apply a few changes on top and request tests at a later point when it's actually ready for testing by others. If we do the other approach, then every change we make to the staging branch would directly land on the devices where the staging branch is still configured from testing a previous service pack.

      By Oliver Smith on 2023-05-16T22:27:05

      Edited by Administrator
    • Administrator
      Administrator @root · Imported
      Author Owner

      Feature is implemented, I've done extensive local testing with the testsuite and new test cases, and rolled it out. I've created a test staging branch for v23.06 SP1 with 1 package. This will need some documentation and verifying that the whole generated repository actually works as intended, but so far it looks good.

      Under published pkgs:

      v23.06_staging_sp1/aarch64/mobile-config-firefox-4.0.4-r0 [log]
v23.06_staging_sp1/armv7/mobile-config-firefox-4.0.4-r0 [log]
v23.06_staging_sp1/x86_64/mobile-config-firefox-4.0.4-r0 [log]
v23.06_staging_sp1/aarch64 synced 193 package(s) from original repository
v23.06_staging_sp1/armv7 synced 150 package(s) from original repository
v23.06_staging_sp1/x86_64 synced 135 package(s) from original repository

      By Oliver Smith on 2023-08-23T22:35:36

    • Administrator
      Administrator @root · Imported
      Author Owner

      After some fixes, it worked as expected.

      Documentation:

      Closing!

      By Oliver Smith on 2023-09-07T21:36:34

    • Administrator closed · Imported

      closed

    Please register or sign in to reply