Description
The openSUSE project wants to leverage AWS CodePipeline for Pull Requests on code.opensuse.org.
First use-case are the kiwi-descriptions to compose openSUSE release images (https://code.opensuse.org/project/kiwi-descriptions). To achieve this, a pagure CI plugin for AWS CodePipeline has to be written and merged upstream. Pagure is facing challenges with outdated dependencies that also impact the code.opensuse.org instance and need to be addressed.
The most challenging part is to tackle the technical debt and dependency issues pagure has. Fixing them is the pre-req to make the project a success and requires good Python skills.
An example of one hard nut to crack, related to Celery and SQLalchemy: https://pagure.io/pagure/pull-request/5508
Goals
- Resolve issues with outdated python dependencies to ensure pagure runs on Python 3.11 and current package versions. At least Fedora 40 python and python package versions. Fedora 41 would be even better. This will also satisfy openSUSE Tumbleweed and Leap 15.6 package versions used on code.opensuse.org
- Validate if https://bugzilla.opensuse.org/show_bug.cgi?id=1229570 is fixed for code.opensuse.org and that all required packages / backports landed in openSUSE:infrastructure:pagure
- Develop AWS CodePipeline pagure CI plugin and create an upstream pull request
- Backport Plugin into openSUSE pagure package on OBS till new upstream release
Resources
The pagure Channel on Matrix: https://matrix.to/#/#pagure:fedora.im
[WIP] Bump test containers to F40, bump pip version pinning to align with rpm versions, address some tech debts in dependencies (Open)
pygit2 1.15.0 (2024-05-18) - breaking changes affect pagure
fix unit tests, bump to F39, unpin python packages and replace deprecated code if necessary (Merged)
oSC 24 talk, Pagure CI integration with AWS CodePipeline
- Session: https://events.opensuse.org/conferences/oSC24/program/proposals/4587
- Slides: https://speakerdeck.com/wombelix/osc24-pagure-ci-integration-with-aws-codepipeline
- Recording: https://media.ccc.de/v/4587-pagure-ci-integration-with-aws-codepipeline
Refactoring: Make current Pagure CI hook / plugin system generic (Merged)
Running the unit-tests in container
- Readme section in https://pagure.io/pagure
Remove gitolite support (Merged)
Pagure Overview
- Ignore Gitolite related content https://docs.pagure.org/pagure/overview.html
Looking for hackers with the skills:
Nothing? Add some keywords!
This project is part of:
Hack Week 24
Activity
Comments
-
16 days ago by wombelix | Reply
Starting the Hack Week with my nemesis, the mysterious
Unable to find object
Exception I couldn't solve yet: https://pagure.io/pagure/pull-request/5508 -
16 days ago by wombelix | Reply
Day 1 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-1.html
I'm pretty happy with the progress, Goal 1 and 2 completed. I can't wait to get started with the AWS CodePipeline plugin tomorrow
-
14 days ago by wombelix | Reply
Day 2 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-2.html
-
14 days ago by wombelix | Reply
Day 3 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-3.html
-
13 days ago by wombelix | Reply
Day 4 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-4.html
-
12 days ago by wombelix | Reply
Day 5 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-5.html
Upstream Pull Request with the current status: https://pagure.io/pagure/pull-request/5511.
I finished around 2/3 of what was planned, I hope to get the rest done in the next week or two. It was still a very successful Hack Week for me and the project I worked on
Similar Projects
This project is one of its kind!