Discussion: set up a CI environment for Lacre? #71

Open
opened 2022-05-15 09:50:09 +02:00 by pfm · 3 comments
Collaborator

Idea: we can set up an environment to automatically perform a set of tests on Lacre code, to make sure that our changes don't break anything. This could be done quick-n-dirty way (Git's hooks running our hand-crafted scripts) or advanced/complete, using already available software (but potentially that would require more resources).

For available options, see DevOps section in Awesome Gitea.

The idea is to be notified immediately when our changes break functionality.

Idea: we can set up an environment to automatically perform a set of tests on Lacre code, to make sure that our changes don't break anything. This could be done quick-n-dirty way (Git's hooks running our hand-crafted scripts) or advanced/complete, using already available software (but potentially that would require more resources). For available options, see [DevOps section](https://gitea.com/gitea/awesome-gitea#user-content-devops) in *Awesome Gitea*. The idea is to be notified immediately when our changes break functionality.
pfm added the
IDEA
label 2022-05-15 09:50:09 +02:00
Author
Collaborator

The most popular solution is probably Jenkins, which has a Gitea plugin. Another option is Buildbot, which supports Gitea out of the box. Yet another option is to just set up Git hooks to run scripts and refuse to accept a commit if tests fail.

What are your opinions?

@muppeth do you already use any CI/CD tool?

The most popular solution is probably Jenkins, which has a Gitea plugin. Another option is Buildbot, which supports Gitea out of the box. Yet another option is to just set up Git hooks to run scripts and refuse to accept a commit if tests fail. What are your opinions? @muppeth do you already use any CI/CD tool?
pfm added the
To-Be-Reviewed
label 2024-01-07 19:48:38 +01:00
Author
Collaborator
Forgejo supports "Actions": * [Forgejo gets an integrated CI named Actions](https://forgejo.org/2023-02-27-forgejo-actions/); * [Forgejo Actions user guide](https://forgejo.org/docs/next/user/actions/).
Owner

Yes. Been thinking to look into that. We need to check what kind of impact it may have on server resources when run on our forgejo, and what's the abuse factor.

Yes. Been thinking to look into that. We need to check what kind of impact it may have on server resources when run on our forgejo, and what's the abuse factor.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Disroot/gpg-lacre#71
No description provided.