Koschei - Continuous integration for Fedora packages

Michael Simacek msimacek at redhat.com
Sun Jun 29 11:19:43 UTC 2014


----- Original Message -----
> From: "Kevin Fenzi" <kevin at scrye.com>
> To: env-and-stacks at lists.fedoraproject.org
> Sent: Saturday, June 28, 2014 6:57:32 PM
> Subject: Re: Koschei - Continuous integration for Fedora packages
> 
> On Fri, 27 Jun 2014 16:37:56 -0400 (EDT)
> Michael Simacek <msimacek at redhat.com> wrote:
> 
> > Hello,
> > 
> > Recently I've been working on Koschei - a new continuous integration
> > tool for Fedora. It's main goal is to track dependency changes in
> > Rawhide and be able to (scratch) rebuild packages in Koji after their
> > dependencies change. It will use Hawkey library to resolve packages'
> > dependencies in order to match resolution happening during the Koji
> > build as closely as possible. That would also enable marking packages
> > with unresolved build dependencies as unbuildable without needing
> > actual rebuild in Koji. The packages will be scheduled based on their
> > current priority value, which will be increased with each
> > depenendency update by a value inversely proportional to the distance
> > between the package and the dependency in the dependency chain. The
> > priority will also slowly increase over time and will be reset back
> > when a new rebuild is scheduled.
> 
> Interesting. Is there any repo or further development information for
> this? Or is it still in the early planning stages?

It's in development phase, the source is available at:
https://github.com/msimacek/koschei
The core part - detecting dependency updates, submitting builds and collecting
the results are already implemented. Also the buildroot differences.
What still needs to be done is the web interface, other analysis and statistics
and taking Koji load into account - right now there's only a limit on number
of running builds.

> 
> > It will provide a web interface with:
> > - detailed reports about current state of packages
> > - their recent builds
> > - analysis of package failures - buildroot differences, parsing
> > failure reasons out of build logs
> > - statistics - build times, common failure reasons
> 
> Some (but by no means all) of this information is available in our
> packages application:
> 
> https://apps.fedoraproject.org/packages/midori
> 
> Would it make sense to add this on there? or do you see this as a
> different audience?

Well, by builds I meant scratch builds done by Koschei. The state is also WRT to
the scratch builds. But we can reuse some information from packages to get
a more complete view and see the builds in context.

> 
> > It will be limiting the number of rebuilds in order to not overload
> > Koji builders - by limiting maximum number of running builds and
> > monitoring Koji current load. Listening to Koji events will be done
> > over fedmsg bus.
> > 
> > If you have any questions or suggestions, please contact me.
> 
> I'd suggest talking with the releng and qa folks before diving in too
> deeply. You might get some more detailed plans or others to help
> you. ;)
> 
> kevin
> 
> _______________________________________________
> env-and-stacks mailing list
> env-and-stacks at lists.fedoraproject.org
> https://lists.fedoraproject.org/mailman/listinfo/env-and-stacks
> 


More information about the env-and-stacks mailing list