Moreover, the delegates with the support of Software in the Public Interest (SPI) have been working with some cloud providers (Microsoft Azure, Amazon AWS and Google Cloud) to create official Debian accounts in each of them, which will allow us to perform tests and publish Debian community images to their users. The team chose those developers as Delegates because they have no direct involvement with cloud providers (many people in the team provide consultancy or work for cloud providers), avoiding any bias in the decisions made by the team. The delegates are responsible for the policies, procedures, and services that are necessary for the production and maintenance of the official Debian images for use on cloud providers. Last October, the Debian Project Leader (DPL) officially announced the creation of the Debian Cloud Team and appointed some Debian Developers as Delegates: Lucas Filipozzi (lfilipoz), Steve McIntyre (93sam) and Tomasz Rybak (serpent). During the development-cycle time of this release the Debian Cloud team has made progress in many fronts: formalizing the team inside the project, improving our tooling, investing in QA, optimizing the generated images and increasing the number of supported architectures. The Debian project has started the freezing process to prepare to release Debian 10 (codename Buster) in the coming months. To make this easier, here’s a snippet I wrote in my ~/.bashrc to register my “builder.local” machine on a new project. You can repeat step 5 with the registration token of all your personal forks in the same GitLab instance. Register your runner sudo gitlab-runner register -non-interactive -url -executor docker -docker-image fedora:27 -registration-token **
Go to your gitlab project page, settings -> CI/CD -> expand “runners” 5.
Install & start the GitLab runner service sudo gitlab-runner install sudo gitlab-runner start 4. (Note: The Ubuntu 18.04 package doesn’t seem to work.) 3.
For personal forks there is only one (AFAIK) shared runner and you could be waiting for hours before it picks your job.īut did you know you can register your own PC, or a spare laptop collecting dust in a drawer, to get instant continuous integration (CI) going? It’s really easy to setup! 1. GNOME GitLab has AWS runners, but they are used only when pushing code into a GNOME upstream repository, not when you push into your personal fork.
0 kommentar(er)
