#4562 Koschei - continuous integration in Koji
Closed: Fixed None Opened 4 years ago by mizdebsk.

= About =

Koschei is a service for scratch-rebuilding RPM packages in Fedora
Koji instance when their build-dependencies change or after some time
elapse. You can find more information about Koschei at [http://fedoraproject.org/wiki/Koschei Fedora wiki page].

Continuous integration is part of [http://fedoraproject.org/wiki/Env_and_Stacks/Product_Requirements_Document Env and Stacks PRD], which was
approved by FESCo. Koschei is [http://meetbot.fedoraproject.org/fedora-meeting/2014-09-30/env-and-stacks.2014-09-30-13.03.html officially recommended] by Env and
Stacks working group.

= Status =

At the time of opening this ticket Koschei with all dependencies is
[http://admin.fedoraproject.org/pkgdb/package/koschei/ available] in official Fedora repositories. It is also being added
to EPEL 7 and can be expected to land there soon.

Koschei is implemeted with accordance to Fedora Infrastructure best
practices (implemented in Python, it uses PostgreSQL, SQLAlchemy and
Alembic). It provides integration with systemd.

Koschei has already been used in production for several months - first at private
system, then moved to Fedora cloud, where it can be currently [http://koschei.cloud.fedoraproject.org/ accessed].

= Requirements =

  • Fedora or RHEL 7 system with EPEL
  • at least 2 CPUs (4 preferred)
  • at least 2 GB of memory (4 GB preferred)
  • a few GB of persistent storage for database
  • preferably good network connection with Koji

= Project team =


Sorry for the delay answering you here. ;)

Do take a look at:

https://fedoraproject.org/wiki/Request_For_Resources
and
http://infrastructure.fedoraproject.org/infra/docs/requestforresources.txt

I can probibly sponsor you in this process.

I guess we are in the planning phase now. I will reply to your post on the infrastructure list with any questions I can think of and we can move on from there. ;)

koschei is now in production!

thanks everyone for all the hard work.

Login to comment on this ticket.

Metadata