Change Details

Currently we have a script on each cli that allows you to easily build the package on your own laptop `utils/build_deb.sh`, but that's not what we use on CI. So I propose to use the `gitlab-ci-local` client instead, that will build the packages the same way that CI does, and remove that script from all the repos. This might help also build locally in lima-kilo (though there's some permissions needing figuring out there, as the code is mounted through sshfs). The command would be something like: ``` gitlab-ci-local package:deb ``` That takes care of getting the scirpts from gitlab, running inside containers, extracting artifacts, etc.

Currently we have a script on each cli that allows you to easily build the package on your own laptop `utils/build_deb.sh`, but that's not what we use on CI. So I propose to use the `gitlab-ci-local` client instead (https://github.com/firecow/gitlab-ci-local), that will build the packages the same way that CI does, and remove that script from all the repos. This might help also build locally in lima-kilo (though there's some permissions needing figuring out there, as the code is mounted through sshfs). The command would be something like: ``` gitlab-ci-local package:deb ``` That takes care of getting the scirpts from gitlab, running inside containers, extracting artifacts, etc.

Currently we have a script on each cli that allows you to easily build the package on your own laptop `utils/build_deb.sh`, but that's not what we use on CI. So I propose to use the `gitlab-ci-local` client instead (https://github.com/firecow/gitlab-ci-local), that will build the packages the same way that CI does, and remove that script from all the repos. This might help also build locally in lima-kilo (though there's some permissions needing figuring out there, as the code is mounted through sshfs). The command would be something like: ``` gitlab-ci-local package:deb ``` That takes care of getting the scirpts from gitlab, running inside containers, extracting artifacts, etc.