Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Renovate in Altinn Studio (Gitea) #5762

Open
6 tasks
Tracked by #126
altinnadmin opened this issue Feb 26, 2021 · 3 comments
Open
6 tasks
Tracked by #126

Renovate in Altinn Studio (Gitea) #5762

altinnadmin opened this issue Feb 26, 2021 · 3 comments
Labels
kind/analysis Used when an issue needs to be analysed before it becomes a user story. org/dsb Issues relevant for DSB org/krt Issues relevant for Finanstilsynet org/udir Issues relevant for Utdanningsdirektoratet quality/engineering Technical or architectural improvements. For example refactoring or upgrading. solution/studio/repos Issues related to the Altinn Studio Repos solution (Gitea).

Comments

@altinnadmin
Copy link
Member

altinnadmin commented Feb 26, 2021

Description

As more and more apps are developed in Altinn Studio, we need a scalable way to easily communicate when app dependencies should be updated.

Describe the solution you'd like

The ideal way to do this would be the same as for our code on GitHub, using Renovate.

  • Renovate identifies dependencies that should be updated for an app repo
  • Renovate creates a pull request for the app repo, inkluding links describing vulnerabilities
  • App developer merges the pull requests, testes and re-deploys the app

Lucky for us, Renovate supports Gitea, which is used in Altinn Studio Repos :)

https://about.gitea.com/resources/tutorials/use-gitea-and-renovate-bot-to-automatically-monitor-software-packages

Renovate screenshot

Describe alternatives you've considered

  • Dependabot, but it does not support Gitea.

Tasks

  • Set up server
  • Set up PAT for Renovate user
  • Set up configuration for Renovate
  • Update documentation
  • Push play :)
  • Run demo on Altinn kaffe
@altinnadmin altinnadmin added solution/studio/repos Issues related to the Altinn Studio Repos solution (Gitea). kind/analysis Used when an issue needs to be analysed before it becomes a user story. labels Feb 26, 2021
@altinnadmin altinnadmin added the quality/engineering Technical or architectural improvements. For example refactoring or upgrading. label Feb 26, 2021
@lvbachmann lvbachmann removed their assignment Mar 29, 2021
@lvbachmann lvbachmann added the QEB label Aug 27, 2021
@haakemon haakemon closed this as completed Sep 6, 2022
@altinnadmin altinnadmin reopened this Sep 6, 2022
@altinnadmin altinnadmin changed the title Dependabot in Altinn Studio Renovate in Altinn Studio Sep 6, 2022
@altinnadmin
Copy link
Member Author

Re-purposed this issue from Dependabot to Renovate.

@haakemon haakemon changed the title Renovate in Altinn Studio Renovate in Altinn Studio (Gitea) Sep 8, 2022
@FinnurO FinnurO added org/udir Issues relevant for Utdanningsdirektoratet org/krt Issues relevant for Finanstilsynet labels Sep 16, 2022
@mijohansen
Copy link
Contributor

This issue is connected to the demo from @bengtfredh today.

Check: https://blog.gitea.io/2022/12/feature-preview-gitea-actions/

@nkylstad
Copy link
Member

nkylstad commented Apr 5, 2024

As of v21 of Gitea (we are currently on 21.8), Gitea ships with actions enabled by default.
To get workflows running through Gitea actions:

  • The repo to run workflows in must have actions enabled through repo settings
  • A runner must be set up (either from repo or from org)
    • Using the docker image that Gitea provides seems to be the fastest way forward here, alternative is prebuilt binaries. Regardless of which method one uses, the runners should be running on a different machine than Gitea to avoid performance issues. I tested with setting up a runner on my own machine using the Docker image using these instructions, and it worked perfectly.
  • A workflow must be set up in the Gitea repo, under the .gitea/workflows folder.

We should look into how we can generalize this setup to make it available for everyone, and not just those who decide to set up their own runners.

Some relevant documentation:
https://docs.gitea.com/usage/actions/quickstart
https://docs.gitea.com/usage/actions/overview
https://docs.gitea.com/usage/actions/act-runner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/analysis Used when an issue needs to be analysed before it becomes a user story. org/dsb Issues relevant for DSB org/krt Issues relevant for Finanstilsynet org/udir Issues relevant for Utdanningsdirektoratet quality/engineering Technical or architectural improvements. For example refactoring or upgrading. solution/studio/repos Issues related to the Altinn Studio Repos solution (Gitea).
Projects
Status: No status
Development

No branches or pull requests

6 participants