containers / containers/udica

Cirrus CI shutdown

Open
#158 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
583
Forks
48
PR merge metrics
No merged PRs in 30d

Description

Cirrus CI will shut down June 1st, https://cirruslabs.org/

As such cirrus will no longer work, so far the cirrus setup used most of podman infra and its own internal GCP project to runt he VMs without other images. I requested the GCP project to be shut down.

I see you already use GH actions here so I suggest you check if you need to move any other tests that were only executed via cirrus.
The containers org also can use packit/tmt to run proper fedora VMs if that is something you liek to have.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the repository's Cirrus CI configuration and comparing its jobs with the existing GitHub Actions workflows. Identify tests that run only in Cirrus, then determine how they can be covered elsewhere and confirm that no required CI coverage is lost after Cirrus is removed.

Written by the indexing model from the issue text.

Assessment

Tech stack
gcp, github-actions, python
Domain
ci-cd, cloud, devops
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.