Workaround test:backend-code not building
Closes #1590 (closed)
What does this MR do?
Changes the instance type of the test:backend-code-stage to saas-linux-small-amd64. This circumvents an issue currently breaking execution of backend tests.
Tests are running slightly longer (11 vs 8 Minutes), but it's better than not having a working pipeline at all.
How confident are you it won't break things if deployed?
I don't think it will break, as i don't see any huge memory needs for these tests. Even though, someone with experience in this codebase should have a look. Also, i don't know why the feature flag FF_NETWORK_PER_BUILD, that's broken on medium-runners, works on test:backend-acceptance without changing the instance type.. kind of weird.
Links to related issues
How to test
- Trigger something that triggers a build.
Checklist
-
added a test, or explain why one is not needed/possible... - Not needed, as it's CI-related.
-
no unrelated changes -
asked someone for a code review -
set a "for:" label to indicate who will be affected by this change -
added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label) -
added an entry to CHANGELOG.md -
added a short text that can be used in the release notes -
Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/?page=bezirk&bid=734&sub=forum. Please change the MRs label to "state:Beta testing". - Consider writing a detailed description in German.
- Describe in a few sentences, what should be tested from a user perspective.
- Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
- Be aware, that also non technical people should understand.
Release notes text in German
Edited by Andre Dörscheln