-----Original Message-----
From: buildsys-bounces(a)lists.fedoraproject.org [mailto:buildsys-
bounces(a)lists.fedoraproject.org] On Behalf Of Adam Miller
Sent: Thursday, May 14, 2015 09:38
To: Discussion of Fedora build system
Subject: Re: Quesitons about dev environments, CI, etc.
On Thu, May 14, 2015 at 8:08 AM, John Florian <john.florian(a)dart.biz>
wrote:
>> -----Original Message-----
>> From: buildsys-bounces(a)lists.fedoraproject.org [mailto:buildsys-
>> bounces(a)lists.fedoraproject.org] On Behalf Of Adam Miller
>> Sent: Wednesday, May 13, 2015 18:30
>> To: Discussion of Fedora build system
>> Subject: Quesitons about dev environments, CI, etc.
>>
>> Hello all,
>> I was recently pointed at kojak[0] to check it out as a way to
>> kick the tires on a fresh koji environment, test some things, and
>> attempt to start hacking on koji. I was curious however if this was at
>> all officially related with koji upstream?
>>
>> The "Tool Chain" section of the kojak README.md kind of hints at the
>> idea of a workflow for developers and/or CI environments. However,
>> that's all listed as a "future" item and leads me to some more
>> questions but they would be out of scope for this mailing list if the
>> project is disjoint from koji upstream.
>>
>> This basically rounds me back to the question of if this is officially
>> related?
>> - If yes, is there any specific roadmap or a place where someone
>> in the community can help work on this?
>> - If no, is there anything aiming to satisfy this use case that is
>> considered "official" within the koji project space?
>>
>> Thank you,
>> -AdamM
>>
>> [0] -
https://github.com/sbadakhc/kojak
>> --
>> buildsys mailing list
>> buildsys(a)lists.fedoraproject.org
>>
https://admin.fedoraproject.org/mailman/listinfo/buildsys
>
>
> First, I know nothing of kojak. You mentioned a CI workflow but it
wasn't clear to me if that's your goal or not. I've used JetBrain's
TeamCity quite a bit and it's a great CI environment but provides nothing
for building rpms directly. Koji does that very well, but I learned the
hard way a year or two ago that koji isn't CI ... at all. My rpm building
efforts under TC started having issues when I got to more complicated
builds so now I'm working towards integrating the two somehow. My current
vision is to have TC use VCS triggers which will then use tito to initiate
scratch builds in koji for development branches. I may eventually hack up
some specialized front-end for Koji to make it serve TC more cleanly, but
I need to experiment with tito more first because I really like how it
simplifies job injection.
>
> No idea if that's helpful or not, but it sounded like we might be on
similar paths.
>
I think we have different goals, I was hoping to start hacking on the
koji codebase itself and was curious if there's any CI workflow around
that and/or the concept of a "dev environment" providing an all-in-one
koji setup that can be iteratively deployed to for the sake
dev/testing. Kojak appears to aim to deliver that but I was just
curious if it was the official method? And if not, is there one?
Thanks,
-AdamM
Fair enough. I'm not tied in any way to TC it was just one of the pieces at my
disposal and that I was aware of with which I could see a solution, Frankensteinish as it
may be. An all-in-one setup would almost certainly be preferable so if nothing else,
I'll have to take a look at kojak myself since maybe that is my solution.
--
John Florian