CI: run pytest and coverage tests inside ephemeral VM in the "builder" VM (nested) #103
No reviewers
Labels
No Label
Bug
Contributions welcome
Did not do
Duplicate
Feature
Module
Backups
Module
GraphQL
Priority
High
Priority
Low
Priority
Medium
Refactor
Severity
High
Severity
Low
Severity
Medium
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: SelfPrivacy/selfprivacy-rest-api#103
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "ci-vm-for-pytest"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Simply
nix flake check -L
is invoked (same as locally available).What to do with the redis port number? Is it used now?
It is currently defined in two places:
6389
as environment variable here:77f8856515/.drone.yml (L13)
6379
asredis
systemd service parameter here:77f8856515/flake.nix (L126)
Do we need to export coverage
xml
somewhere after the test has ended?We no longer test with a port.
Delete remaining port settings, we do not use them anymore
@houkime, deleted.
87516bfe9a
.87516bfe9a
to53ec774c90
WIP: CI: run pytest and coverage tests inside ephemeral VM in the "builder" VM (nested)to CI: run pytest and coverage tests inside ephemeral VM in the "builder" VM (nested)