Move remaining build and release pipelines to Drone CI #270

New Issue

Closed

opened 2023-08-02 22:32:00 +02:00 by blacklight · 0 comments

blacklight commented

2023-08-02 22:32:00 +02:00

Owner

All the current build and release pipelines are currently managed by a single Platypush event hook that is triggered both on push and release.

The only exception is for the tests, which are currently running both on the Platypush hook and on the Drone CI instance.

The hook offers a lot of flexibility, but:

It doesn't offer a simple graphical overview of the build status, outside of the Platypush logs on the server.
It doesn't scale well - a single Platypush instance running on the same server as Gitea is in charge of everything, and it assumes that all the files already exist on the local machine.
The tests can be quite brittle, as they are executed on the same machine where the main instance itself is running and it assumes that all the files have already been correctly checked out.

We should therefore migrate the whole pipeline to Drone CI, and use webhooks when we want to interact with the Gitea server's Platypush instance if we need more granularity.

Checklist:

Migrate Matrix/IRC notifications.
Migrate docs rebuild.
Migrate Arch packages release automation.
Migrate pip package release automation.

All the current build and release pipelines are currently managed by a single Platypush event hook that is triggered both on push and release. The only exception is for the tests, which are currently running both on the Platypush hook and on the [Drone CI instance](https://ci-cd.platypush.tech/platypush/platypush). The hook offers a lot of flexibility, but: 1. It doesn't offer a simple graphical overview of the build status, outside of the Platypush logs on the server. 2. It doesn't scale well - a single Platypush instance running on the same server as Gitea is in charge of everything, and it assumes that all the files already exist on the local machine. 3. The tests can be quite brittle, as they are executed on the same machine where the main instance itself is running and it assumes that all the files have already been correctly checked out. We should therefore migrate the whole pipeline to Drone CI, and use webhooks when we want to interact with the Gitea server's Platypush instance if we need more granularity. Checklist: - [x] Migrate Matrix/IRC notifications. - [x] Migrate docs rebuild. - [x] Migrate Arch packages release automation. - [x] Migrate pip package release automation.