Monitoring the general state of continuous integration tests #438

New Issue

3wordchant · 2023-03-28T05:16:38Z

3wordchant commented

2023-03-28 05:16:38 +00:00

Currently, some (most?) recipes have basic continuous integration tests, e.g. Wordpress:

Auto-deploys to swarm-test.autonomic.zone
Shows build status on the README page which also pulls through to the app catalogue entry
Also shows build status on the Drone homepage

And yet!

Nobody seems to be looking at the status badges
Or at the Drone dashboard
CI has been completely broken for $some_moderate_amount of time (Apparmor / Docker snafu on the CI server)

So, how to make this all more visible?

Currently, some (most?) recipes have basic continuous integration tests, e.g. Wordpress: - [Auto-deploys to swarm-test.autonomic.zone](https://git.coopcloud.tech/coop-cloud/wordpress/src/branch/master/.drone.yml#L4-L23) - Shows build status [on the README page](https://git.coopcloud.tech/coop-cloud/wordpress/#wordpress) which also pulls through to [the app catalogue entry](https://recipes.coopcloud.tech/wordpress) - Also shows build status [on the Drone homepage](https://build.coopcloud.tech/) And yet! - Nobody seems to be looking at the status badges - Or at the Drone dashboard - CI has been completely broken for $some_moderate_amount of time (Apparmor / Docker snafu on the CI server) So, how to make this all more visible?

3wordchant added the

enhancement

ci/cd

labels 2023-03-28 05:16:38 +00:00

decentral1se commented

2023-04-10 21:23:50 +00:00

Yeh, good to raise it. Some great has been put in! Thanks all 👏 Some thoughts...

I guess there is some avoidance of this due to the fact of not existing for so long (like the missing abra test suite) and also, it is a bit unreliable (i.e. what is it really testing?) and also it is bit complicated to grasp. Also, it kinda falls into the "whose responsibility is this?" hole.

There are so many apps and there are so many .drone.yml configs, so it's also kinda overwhelming. Maybe we only CI test apps that have some rating of 3+ or something? Or some way to thin it down to a maintained listing which can be watched over going forward.

I think we need to switch from stack-ssh-deploy to actually using abra? And some scenarios, instead of just deploy only (e.g. "can make new app from recipe", "can backup deployed app", etc.)? Again, I'm thinking of the YunoHost CI system.

Idk maybe we need to work back from the automation to how can we test things manually ourselves on our local workstations? Easier to grasp and for people to be involved in. This was what we ended up with the recipe versioning automation?

Yeh, good to raise it. Some great has been put in! Thanks all 👏 Some thoughts... I guess there is some avoidance of this due to the fact of not existing for so long (like the missing `abra` test suite) and also, it is a bit unreliable (i.e. what is it really testing?) and also it is bit complicated to grasp. Also, it kinda falls into the "whose responsibility is this?" hole. There are so many apps and there are so many `.drone.yml` configs, so it's also kinda overwhelming. Maybe we only CI test apps that have some rating of 3+ or something? Or some way to thin it down to a maintained listing which can be watched over going forward. I think we need to switch from `stack-ssh-deploy` to actually using `abra`? And some scenarios, instead of just deploy only (e.g. "can make new app from recipe", "can backup deployed app", etc.)? Again, I'm thinking of the YunoHost CI system. Idk maybe we need to work back from the automation to how can we test things manually ourselves on our local workstations? Easier to grasp and for people to be involved in. This was what we ended up with the recipe versioning automation?

decentral1se commented

2023-04-10 21:30:41 +00:00

Related: coop-cloud/organising#401

Related: https://git.coopcloud.tech/coop-cloud/organising/issues/401

decentral1se added this to the (deleted) project 2023-06-08 09:25:53 +00:00

decentral1se commented

2023-09-20 12:46:34 +00:00

Following on from coop-cloud/organising#438 (comment) 👉 coop-cloud/organising#491

Following on from https://git.coopcloud.tech/coop-cloud/organising/issues/438#issuecomment-16304 👉 https://git.coopcloud.tech/coop-cloud/organising/issues/491

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/organising#438