It's awesome Fedora Infra is starting to use Jenkins. At work I use it to keep our systems scripts code base in sync across our infrastructure after pulling fresh bits from our git repositories. We also use it to build RPMs and maintain key stores. To Robyn's point, I look forward to reading how Jenkins might complement the existing Fedora build infrastructure.

On Oct 8, 2012 11:38 AM, "Pierre-Yves Chibon" <pingou@pingoured.fr> wrote:
On Sun, 2012-10-07 at 06:59 -0700, Robyn Bergeron wrote:
>
> What are we "building"? Packages? Packages + test against multiple
> versions? Build package + unit-test/run against nightly?  Package +
> test against multiple+"nightly"/latest, if passes then automagically
> incorporate into new "nightly"?  Or am I TOTALLY off base and you're
> just thinking about how we build/test/redeploy our infrastructure
> apps?

In this case, we use Jenkins for running unit-tests of project for which
we are upstream (and which a) have unit-tests b) are interested in
having a Continuous Integration approach).
At the moment projects like python-kitchen, Bodhi, FedoraReview are in
Jenkins.

I remember thoughts of doing mass-rebuild using the clouds at some
point, but I don't remember from who.

> Yes, I realize that a bunch of those are like, totally jumping the gun
> and starting small is good, but curious if that is sort of the
> roadmap.
> Or if there is a roadmap or if this is just "checking things out to
> see what they might do for us."

Regarding Jenkins, I do not think there is a clear roadmap. We had a
need for an environment in which we could test python3 and the current
Jenkins instance was going to be hard to adapt for this and we thought
the cloud infra might be a nice solution to this.

However, I am convinced all developers here agree that we could improve
on unit-tests coverage for the project we maintain.
I guess that this will be something to work on when we port our current
(web-)app to newer framework.

> To that end - I think it would be super cool for others observing to
> know... what is the problem(s) we're trying to solve, or what is the
> gain we're hoping to see? And yes - "we heard this was kind of cool so
> we're just checking it out to see what it even does" is perfectly
> reasonable (and, ahem, awesome).  But we have all this new stuff going
> on - "we haz a cloud," autoqa is continuing to evolve, new archs like
> arm, etc... - and some of it could potentially solve things. So I'm
> wondering... is there is a basic "things we could solve/improve" list?

I am sure the QA guys could benefit from the fact that we have our own
cloud now.

>  Maybe this would be a cool topic for FUDCon if nothing else? :)

I don't doubt it would be :)

Pierre
_______________________________________________
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure