Running local, self hosted forgejo with a few runners.
Now my code is neatly checked with pre-commit and linters, build when new tags are pushed, renovate is scheduled every 24 hours to check for new releases of stuff etc.
The renovate image has been pulled by hand and the forgejo-runner will happily start the image. Both PAT and GITHUB secrets are configured as ‘action secrets’ within the renovate repository.
Besides the workflow, the repository contains renovate.json and config.js, so renovate has the correct configuration.
Absolutely!
Running local, self hosted forgejo with a few runners.
Now my code is neatly checked with pre-commit and linters, build when new tags are pushed, renovate is scheduled every 24 hours to check for new releases of stuff etc.
Just a few containers and a happy user :-)
do you use forgejo-runner or another ci/cd image?
I am not the OP but I use Woodpecker CI.
I like to keep things separated, in a KISS fashion. This makes changing either software easier.
Still testing and fiddling, but I’m using the forgejo-runner. Renovate is just another repository, with a workflow to get it started:
on: schedule: - cron: '5 2 * * *' - cron: '5 14 * * *' jobs: build: runs-on: docker container: image: renovate/renovate:37.140-full steps: - name: Checkout uses: actions/checkout@v3 - name: Run renovate env: PAT: ${{ secrets.PAT }} GITHUB_COM_TOKEN: ${{ secrets.GITHUB }} run: | echo "Running renovate" cd ${GITHUB_WORKSPACE} renovate --token ${PAT}The renovate image has been pulled by hand and the forgejo-runner will happily start the image. Both PAT and GITHUB secrets are configured as ‘action secrets’ within the renovate repository.
Besides the workflow, the repository contains renovate.json and config.js, so renovate has the correct configuration.