Hi,
if you don't know Koji [1], let me introduce it a little bit. It's a
distributed, clean-room, auditable build system used mainly for
production builds, mainly for RPMs, but also for other target platforms.
It's used by Fedora [2], Red Hat, Scientific Linux, NASA, etc. List of
some Koji instances is here [3].
The goal of the prepared Jenkins <> Koji integration plugin is to:
1) run regular CI in Jenkins
2) after several successful integration testsuite runs (unit tests)
trigger the production builds in Koji
3) stage the artifacts after successful completion (ideally on some
stage with API)
4) run smoke tests on the production bits from Koji in Jenkins
5a) if the smoke tests pass, promote the build to a candidate build
5b) if the smoke tests fail, repeat the process
Do you have any features you would like to see?
Are you using both Koji and Jenkins? If not, you can think of this as
automated release tool intended to run both on Jenkins and on some
clean-room environment - eg. Koji in this example.
Any other comments or opinions?
Best regards,
Vaclav Tunka
[1] https://fedoraproject.org/wiki/Koji
[2] http://koji.fedoraproject.org/koji/
[3] https://fedoraproject.org/wiki/Koji/RunsHere
--
Vaclav Tunka
Enterprise Application Platforms
JBoss by Red Hat
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
