Skip to content

Revert "Workaround test:backend-code not building"

Don't merge, until gitlab-org/gitlab-runner#30884 (closed) is fixed and deployed in our instance!

What does this MR do?

Reverts the workaround for #1590 (closed), switching to the "small" instance.

How confident are you it won't break things if deployed?

As long as the fix from Gitlab is deployed for us before this is merged, pretty confident.

Links to related issues

How to test

  • Rebuild this PR.

Checklist

  • added a test, or explain why one is not needed/possible...
    • Not needed, as it's a CI change.
  • 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.
Edited by Andre Dörscheln

Merge request reports