Discussion: set up a CI environment for Lacre? #71
Labels
No Label
ANSIBLE
BUG
CODE
DEVELOPMENT
DOCUMENTATION
FEEDBACK
FIX
HOWTOs
IDEA
INFRA
ISSUE
MAILSERVER
TESTS
To-Be-Reviewed
WEB
WEBSITE
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/gpg-lacre#71
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
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.
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?
Forgejo supports "Actions":
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.