feat: update examples/docker-compose/compose-forgejo-and-runner.yml with renovate #405
Labels
No labels
FreeBSD
Kind/Breaking
Kind/Bug
Kind/Chore
Kind/DependencyUpdate
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Windows
linux-powerpc64le
linux-riscv64
linux-s390x
run-end-to-end-tests
run-forgejo-tests
run-multi-platform-tests
No milestone
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo/runner#405
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Can you reproduce the bug on the Forgejo test instance?
No response
Description
I noticed the current "tests" for the runner use version
3.4.1, and not the latest versions,My thought process is that tests should be done on the latest code, not old supposedly depreciated code.
So I updated the tests to build a local image of the code, and then use that.
The Tests Fail
Forgejo Version
No response
Runner Version
No response
How are you running Forgejo?
forgejo/runnertestsHow are you running the Runner?
forgejo/runnertestsLogs
#404
See runner logs
Workflow file
#404
I thought renovate would take care of it but it does not appear to be the case. @viceice do you know why? Maybe this file must be explicitly explicitly marked as being a docker-compose file because renovate has no way to figure that on its own?
image: code.forgejo.org/forgejo/runner:6.3.1bug: Repository Tests Fail when using latest codeto feat: update examples/docker-compose/compose-forgejo-and-runner.yml with renovateit's because of this default preset
https://docs.renovatebot.com/presets-default/#ignoremodulesandtests