CIAO: before_merging/scheduled, pt 10: packaging (debian repository)

Stack

• !12695 (merged): test (scripts)
• !12696 (merged): test (tezt)
• !12697 (merged): test (kernels)
• !12698 (merged): docs
• !12699 (merged): coverage
• !12700 (merged): packaging (debian repository) <-- you are here
• !12701 (merged): concluding cleanup

What

Part of the CIAO translation of the test stage for the before_merging/scheduled pipelines.

Translates the file debian_repository.yml and the jobs contained therein.

Why

How

Nothing surprising. Some notes on the translation:

• The file debian_repository.yml would contain a top-level variables declaration to make a variable available to the whole file. This doesn't translate will to CIAO so I just added the same variable to all jobs to all jobs that needed it.
• We make explicit the image of the job oc.build-debian. It had no image specified, so the default docker image would be used. We typically use the alpine image for small jobs, so I picked that here.

Manually testing the MR

For the generated YML, do review the result of these commands (see previous MRs like !11501 (merged) for setup instructions for gci-tezos):

$ gci-tezos diff-full-config master . master_branch,test_release_tag,release_tag,non_release_tag,non_release_tag_test,beta_release_tag
$ gci-tezos diff-full-config master . schedule_extended_tests
$ gci-tezos diff-full-config master . before_merging

Note, depending on the state on local checkout, you might get results of the above commands by replacing master with git merge-base origin/master HEAD, where origin might change depending on the name of your tezos git remote. this also requires that you've run a fetch on origin such that it does not lag behind the branch in this MR.

The first command shows no diff, meaning that those environments are unaffected.

The later two commands will show a diff.

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR