Use automated testing of updates #96

New Issue

Open

opened 2026-08-06 09:30:48 +00:00 by ineiti · 3 comments

ineiti commented 2026-08-06 09:30:48 +00:00

Owner

Copy Link

Copy Source

I would like to sign up coop-cloud/nextcloud to be tested with this:

https://docs.cooperative.computer/docs/d235e765-93db-4abd-a033-a72c94ae1eb2/

What do you think, @dannygroenewegen ?

I would like to sign up coop-cloud/nextcloud to be tested with this: https://docs.cooperative.computer/docs/d235e765-93db-4abd-a033-a72c94ae1eb2/ What do you think, @dannygroenewegen ?

ineiti referenced this issue 2026-08-08 09:25:45 +00:00

Updating to the latest nextcloud version #102

dannygroenewegen commented 2026-08-08 10:01:30 +00:00

Owner

Copy Link

Copy Source

I don't have time to really consider this at the moment. From what I understand, the !testme would run on a copy of this repo at Autonomic? Because a decision has to be made before integrating this at git.coopcloud.tech?

Up to you if you want to explore automated tests with the autonomic infra. But the title of this issue says 'automated updates': I'm not comfortable committing to automated updates for this recipe until I understand the test process and which parts would be updated automatically, and under which conditions.

I don't have time to really consider this at the moment. From what I understand, the `!testme` would run on a copy of this repo at Autonomic? Because a decision has to be made before integrating this at git.coopcloud.tech? Up to you if you want to explore automated tests with the autonomic infra. But the title of this issue says 'automated updates': I'm not comfortable committing to automated updates for this recipe until I understand the test process and which parts would be updated automatically, and under which conditions.

ineiti changed title from Use automated updates to Use automated testing of updates 2026-08-08 10:21:10 +00:00

ineiti commented 2026-08-08 10:21:44 +00:00

Author

Owner

Copy Link

Copy Source

Corrected the title to use automated TESTING of updates :) I'll contact them to know how that would work and what we'd need to change.

Corrected the title to `use automated TESTING of updates` :) I'll contact them to know how that would work and what we'd need to change.

moritz commented 2026-09-10 00:37:56 +00:00

Owner

Copy Link

Copy Source

That sounds very interesting. At the moment I am building a CI e2e testing pipeline for the kollicloud app integration:

1. Renovate found a new recipe update and creates a PR
2. Inside this PR a complete new kollicloud instance is deployed with our stable versions and updated to the new recipe versions
3. Some Playwright tests check if our integrations like SSO, Onlyoffice, Monitoring, SMTP ... are working
4. Then a complete new instance with the new recipe versions is deployed
5. The same Playwright tests are run agains this fresh deployement
6. If all tests are green and there is no major update the new versions are automerged

https://git.local-it.org/local-it/kolli-config/src/branch/main/ci

I think this could also be used to test the single recipies to automerge the renovate image updates. It would be nice to write tests especially for the modifications and non-defaults we put into the recipes.

That sounds very interesting. At the moment I am building a CI e2e testing pipeline for the kollicloud app integration: 1. Renovate found a new recipe update and creates a PR 2. Inside this PR a complete new kollicloud instance is deployed with our stable versions and updated to the new recipe versions 3. Some Playwright tests check if our integrations like SSO, Onlyoffice, Monitoring, SMTP ... are working 4. Then a complete new instance with the new recipe versions is deployed 5. The same Playwright tests are run agains this fresh deployement 6. If all tests are green and there is no major update the new versions are automerged https://git.local-it.org/local-it/kolli-config/src/branch/main/ci I think this could also be used to test the single recipies to automerge the renovate image updates. It would be nice to write tests especially for the modifications and non-defaults we put into the recipes.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

renovate/docker.elastic.co-elasticsearch-elasticsearch-9.x

semver_details

nextcloud-metrics

trusted-domains

update_33.0.8

renovate/pgautoupgrade-pgautoupgrade-18.x

pr-15.2.0+34.0.2-fpm

pr-14.1.0+33.0.7-fpm

pr-14.2.0+33-fpm

pr-15.1.0+34.0.2-fpm

pr-15.0.0+34.0.2-fpm

pr-14.0.1+33.0.7-fpm

feat/check-major-upgrade

pr-14.0.0+33-fpm

temp

fix/nginx-conf-config-name

pr-13.2.0+32-fpm

upload-limit

feature/imaginary

kc_stable

nextcloud-v28

add-theming-v28.0.5

add-theming

update-nginx-conf

split-bbb-onlyoffice-compos

split-onlyoffice-bbb-config

authentik_sso

healthchecks

occ_cmds

auto_app_install

embed_nextcloud_in_iframe

auto_configure_sso

add-postgres-db

14.1.1+33.0.8-fpm

14.1.0+33.0.7-fpm

14.0.1+33.0.7-fpm

14.0.0+33.0.7-fpm

13.2.0+32-fpm

13.1.5+32.0.13-fpm

13.1.4+32.0.13-fpm

13.1.3+32.0.13-fpm

13.1.2+32.0.13-fpm

13.1.1+32.0.12-fpm

13.1.0+32.0.11-fpm

13.0.1+32.0.3-fpm

13.0.0+32.0.3-fpm

12.1.0+31.0.6-fpm

12.0.1+31.0.6-fpm

12.0.0+31.0.6-fpm

11.4.0+30.0.6-fpm

11.4.0+30.0.10-fpm

11.3.0+30.0.6-fpm

11.2.0+30.0.6-fpm

11.1.0+30.0.6-fpm

11.0.1+30.0.4-fpm

11.0.0+30.0.4-fpm

10.0.0+30.0.4-fpm

9.2.0+29.0.8-fpm

6.0.11+28.0.10-fpm

6.0.10+28.0.10-fpm

6.0.9+28.0.10-fpm

9.1.2+29.0.5-fpm

6.0.8+28.0.5-fpm

6.0.7+28.0.5-fpm

9.1.0+29.0.5-fpm

9.0.0+29.0.5-fpm

6.0.6+28.0.5-fpm

8.0.1+29.0.3-fpm

8.0.0+29.0.1-fpm

7.0.3+29.0.1-fpm

6.0.5+28.0.5-fpm

7.0.2+29.0.1-fpm

7.0.1+29.0.1-fpm

7.0.0+29.0.0-fpm

6.0.4+28.0.5-fpm

6.0.3+28.0.5-fpm

6.0.2+28.0.5-fpm

5.0.3+27.0.1-fpm

6.0.1+28.0.2-fpm

6.0.0+28.0.1-fpm

5.2.0+27.1.5-fpm

5.1.1+27.1.5-fpm

5.1.0+27.1.3-fpm

5.0.2+27.0.1-fpm

5.0.1+27.0.1-fpm

5.0.0+27.0.0-fpm

4.0.7+26.0.2-fpm

4.0.6+26.0.2-fpm

4.0.5+26.0.2-fpm

4.0.4+26.0.2-fpm

4.0.3+26.0.2-fpm

4.0.2+26.0.2-fpm

4.0.1+26.0.1-fpm

4.0.0+26.0.1-fpm

3.3.2+25.0.6-fpm

3.3.1+25.0.5-fpm

3.3.0+25.0.5-fpm

3.2.0+25.0.4-fpm

3.1.2+25.0.4-fpm

3.1.1+25.0.1-fpm

3.1.0+25.0.1-fpm

3.0.1+25.0.1-fpm

3.0.0+25.0.1-fpm

2.1.4+24.0.6-fpm

2.1.3+24.0.5-fpm

2.1.2+24.0.3-fpm

2.1.1+24.0.2-fpm

2.1.0+24.0.0-fpm

2.0.0+23.0.4-fpm

1.0.0+23.0.1-fpm

Labels

Clear labels

bug

Something is not working

documentation

For issues that are calling out documentation gap

duplicate

This issue or pull request already exists

enhancement

New feature

help wanted

Need some help

invalid

Something is wrong

question

More information is needed

wontfix

This won't be fixed

No labels

Milestone

No items

No Milestone

Assignees

Clear assignees

3wordchant aadil (Aadil Ayub) abra-bot (Abra Bot) ammaratef45 amras (Sarma) BornDeleuze Brooke carla cas (Cassowary) coopcloud dannygroenewegen (Danny Groenewegen) decentral1se (d1) fauno (fauno) ineiti (Linus Gasser) javielico (Javielico) jjsfunhouse kawaiipunk (KawaiiPunk) knoflook moosemower moritz notplants oxaliq (sorrel) p4u1 renovate-bot (Comrade Renovate Bot) simon stevensting trav (Trav Fryer) yksflip

No Assignees

3 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/nextcloud#96